Use this skill only when the user explicitly requests deep research or a detailed report on a topic — phrases like "research X", "give me a detailed report on X", "deep dive into X", "I want a thorough analysis of X", or "write me a research report on X". Do NOT trigger for casual questions, quick lookups, or requests to add/edit entries. This is a heavyweight, multi-step workflow that mines the knowledge base, fills gaps with web research, creates new KB entries along the way, and produces a long-form, citation-rich research report saved to reports/.
This skill produces a long-form research report grounded in the knowledge base and supplemented by
web research. The output is saved as a Markdown file in reports/.
Only trigger when the user explicitly asks for research, a deep dive, or a detailed report. This is
not a lookup skill — it is a slow, thorough process. If the user asks a quick question, answer it
directly. If they want to add something to the KB, use keine-update-entries instead.
All reports go in reports/<yyyy-mm-dd-slug>.md. This directory is separate from entries
(docs/) and maps (docs/maps/). Reports are synthesis documents — they cite KB entries and web
sources but are not themselves knowledge entries.
Work through each phase in order. Do not skip ahead.
Before touching the KB, decompose the research question:
Write these sub-questions down — they become the skeleton of the report.
Use the KB's structure to orient yourself quickly:
# Survey topic maps
ls docs/maps/
# Survey available tags
ls docs/tags/
# Search for relevant keywords
grep -ri "keyword" docs/
Read all relevant map files first — they give the fastest orientation to a topic area and link to the most relevant entries.
Then read the specific entries linked from those maps and tags. For each entry, note:
Be honest about gaps. Local knowledge is almost always incomplete for a substantive research question.
For each gap or unanswered sub-question identified in Phase 2, search the web. Be systematic: search each facet deliberately rather than doing a single broad search.
For each significant web finding:
keine-update-entries skill. This ensures future agents can find it.Do not create entries for every result — only for knowledge worth keeping. A good rule: if a future agent researching a related question would benefit from finding this entry, create it.
After creating new entries, run tag maintenance scripts/maintain_tags.py
Write a detailed, long-form report. Inline citations ([1], [2], ...) should appear throughout
the body wherever a claim is grounded in a specific source. Numbered references are listed at the
end.
Aim for depth over brevity — this is not a summary. Each section should explain, not just list.
---