facts
Skill0 starsChanged 4 months agoMITView on GitHub
Document how a conceptual area of the codebase is implemented with parallel sub-agents. Usage: /facts {concept} [hint paths...]
6 other projects use a version of this.
Adopted by
Most recently taken up by
- persiyanov/skillstheir own version, first seen Nov 15, 2026
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tooltheir own version, first seen Nov 8, 2026
- ansvisor/ansvisortheir own version, first seen Nov 1, 2026
- av/harbortheir own version, first seen Oct 8, 2026
- denismrvoljak/claude-scholartheir own version, first seen Aug 16, 2026
- backnotprop/brotheir own version, first seen Jul 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- av/harbor★ 3.3ksame name
- ai-search-guru/getcito-worlds-first-open-source-aio-aeo-or-geo-tool★ 432same name
- ansvisor/ansvisor★ 241same name
- backnotprop/bro★ 182same name
- denismrvoljak/claude-scholar★ 1same name
- persiyanov/skills★ 1same 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 repository21 other files it gives its agents.
- add-to-claudeSkill
- add-to-rulesSkill
- audit-claudeSkill
- audit-rulesSkill
- autopilotSkill
- better-planSkill
- design-autoSkill
- designSkill
- execute-autoSkill
- executeSkill
- facts-extSkill
- questionsSkill
- research-autoSkill
- researchSkill
- review-autoSkill
- structure-autoSkill
- structureSkill
- wiki-captureSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 9 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Use the Agent tool with subagent_type: "fact-finder".
- Distinctive: line 28
After the root agent completes, seed both lists from its response:
- Distinctive: line 29
Add its COVERED items to covered
- Distinctive: line 30
Add its SUGGESTED items to queue
- Distinctive: line 37
If the filtered queue is empty, proceed to Phase 3.
- Distinctive: line 44
After all agents in this round complete, for each agent:
- Distinctive: line 46
Add its SUGGESTED items to queue (replacing the old queue)
- Distinctive: line 51
After the loop exits:
- Very specific: line 56
Use # {Concept} — Implementation Facts as the top heading
- Distinctive: line 60
No frontmatter, no timestamps, no filler
- Distinctive: line 61
Delete all fragment files
“Common” is measured: kept by at least 6 in 10 of the 4 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
Parse the user's input:
- First argument is the concept (e.g.,
authentication,offline-sync,navigation) - Any additional arguments are hint file paths the agent should start exploring from
Phase 1 — Root exploration
Spawn a fact-finder agent with:
concept: {concept}
sub_area: {concept}
hints: {any hint paths provided, or "none"}Use the Agent tool with subagent_type: "fact-finder".
Phase 2 — Recursive fan-out
Maintain two lists across rounds:
- covered — all topics explored so far (accumulated from every agent's COVERED section)
- queue — sub-areas to explore next
After the root agent completes, seed both lists from its response:
- Add its COVERED items to covered
- Add its SUGGESTED items to queue
Then loop:
- Filter the queue. For each proposed sub-area, evaluate:
- Relevance: Is this sub-area meaningfully related to the original concept
{concept}? Drop it if it has drifted to a tangential or generic topic. - Novelty: Has this topic (or something substantially overlapping) already been covered? Drop it if so.
- Relevance: Is this sub-area meaningfully related to the original concept
- If the filtered queue is empty, proceed to Phase 3.
- Spawn one
fact-finderagent per sub-area in the queue, all in parallel:concept: {concept} sub_area: {sub-area name} hints: {hints from the suggestion} - After all agents in this round complete, for each agent:
- Add its COVERED items to covered
- Add its SUGGESTED items to queue (replacing the old queue)
- Go back to step 1.
Phase 3 — Merge & clean up
After the loop exits:
- Glob
docs/{concept}/facts-*.mdto find all fragment files - Read every fragment
- Combine all fragments into
docs/{concept}/facts.md:- Use
# {Concept} — Implementation Factsas the top heading - Organize sections logically (root agent's broad content first, then deeper sub-area sections)
- Deduplicate facts that appear in multiple fragments
- Preserve all source file references
- No frontmatter, no timestamps, no filler
- Use
- Delete all fragment files
Tell the user the output is at docs/{concept}/facts.md.
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.

