keine-research
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/.
npx skills add majiayu000/claude-skill-registry --skill keine-research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Keine Research 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/`. ## When to use this skill 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. ## Report location 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. --- ## Workflow Work through each phase in order. Do not skip ahead. ### Phase 1 — Understand the question Before touching the KB, decompose the research question: - What is the user actually asking? Restate it precisely. - What sub-questions or facets need to be addressed for a complete answer? - What depth of coverage is expected? (If unclear, assume comprehensive.) Write these sub-questions down — they become the skeleton of the report. ##
- When to use this skill
- Report location
- Workflow
- Phase 1 — Understand the question
- Phase 2 — Mine the knowledge base
- Phase 3 — Web research
- Phase 4 — Write the report
- Phase 5 — Save and commit
- Phase 6 — Update topic map (if warranted)
- Quality bar
Survey topic maps ls docs/maps/ Survey available tags ls docs/tags/ Search for relevant keywords grep -ri "keyword" docs/ git add reports/<report>.md docs/ docs/tags/ git commit -m "docs(report): <topic>"
What does the keine-research skill do?
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/.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill keine-research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.