research-topic
Skill2 starsChanged 25 days agoMITView on GitHub
Use when you want a topic researched into verified notes. Splits the topic into narrow questions, fans out researcher agents in parallel, then runs /verify on each inbox file and /file on each verified file; lead-run, it does not write notes itself.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Ideya-AI/Ideyatheir own version, first seen Nov 15, 2026
- atomicinnovation/acceleratortheir own version, first seen Nov 14, 2026
- methylo/claude-skill-booktheir own version, first seen Nov 8, 2026
- dmzoneill/skillstheir own version, first seen Oct 24, 2026
- Pablomg02/pamaga-agent-toolkittheir own version, first seen Oct 11, 2026
- priyanshu-arya/LinkedIn_Automationtheir own version, first seen Sep 17, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- atomicinnovation/accelerator★ 35same name
- n24q02m/wet★ 24same name
- n24q02m/wet-mcp★ 24same name
- methylo/claude-skill-book★ 12same name
- dmzoneill/skills★ 2same name
- Ideya-AI/Ideya★ 1same name
- Pablomg02/pamaga-agent-toolkit★ 1same name
- priyanshu-arya/LinkedIn_Automation★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-reviewSkill
- ai-mesh-cleanSkill
- cad-buildSkill
- couponSkill
- curriculumSkill
- dfm-reviewSkill
- fileSkill
- gddSkill
- ip-checkSkill
- led-budgetSkill
- lesson-learnedSkill
- makerworld-publishSkill
- material-pickSkill
- mcp-new-toolSkill
- ortho-sheetSkill
- pi-power-budgetSkill
- preprint-checkSkill
- promo-planSkill
- qa-gateSkill
- render-criticSkill
- research-oneSkill
- retopoSkill
- safety-sheetSkill
- sculptSkill
- slicer-questionSkill
- style-bibleSkill
- tech-packSkill
- unit-costSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read CURRICULUM.md and the knowledge\ category indexes to pick the category the topic belongs to.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
Topic: $ARGUMENTS. This skill is the knowledge pipeline entry point: researcher, then fact-checker, then librarian, with on-disk hand-offs under research\.
When to use
You ask to research, learn or verify a topic, or an item from your research backlog is picked up. Not for a single quoted claim (use /verify "<claim>").
Steps
- Read
CURRICULUM.mdand theknowledge\category indexes to pick the category the topic belongs to. - Split the topic into 3 to 8 narrow questions, each answerable from one or two primary pages. Choose a
<topic-slug>. - Launch one
researchersubagent per question in the same message so they run in parallel (/research-onedoes one). Each gets: the question, the topic slug, the question slug, and the source priority reminder. Expect back a path underresearch\inbox\<topic-slug>\. - For each inbox file, run
/verify research\inbox\<topic-slug>\<q>.md. Pass only the path, never the researcher's output. - For each verified file, run
/file research\verified\<topic-slug>\<q>.md. - Reply: what was VERIFIED (with URLs), what was CONTRADICTED or UNVERIFIABLE, which notes changed (full paths), and the next topic. Mark questions NEEDS MAKER.
Common rationalizations
| Rationalization | Reality |
| "I already know the answer, skip the researcher." | Notes written from memory are where errors come from. Run the pipeline. |
| "Pass the researcher's reasoning to the fact-checker so it works faster." | Independence is the point. Path only. |
| "The fact-checker said PARTIAL; file it and move on." | PARTIAL is filed as the corrected value with the correction named. |
Red flags
- Fewer than 3 questions for a broad topic, or a question that needs opinion rather than a source.
- Running researchers one at a time.
- A note written by the lead instead of the librarian.
Verification
- Every question has an inbox file, a verified file, and a librarian result.
tools\check_note.pyPASS reported for every touched note.- Reply lists full paths and URLs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

