find
Skill0 starsChanged 2 months agoMITView on GitHub
Search documentation with authority-aware ranking, so the canonical specification is returned before the tutorial that paraphrases it. Use for "where is X documented", "what do we say about Y", or finding the authoritative source for a behaviour.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Jamaalx/claude-chat-namertheir own version, first seen Nov 1, 2026
- replybr/plugadvpltheir own version, first seen Nov 1, 2026
- fakechris/obsidian_vault_pipelinetheir own version, first seen Oct 9, 2026
- bibryam/universal-skill-findertheir own version, first seen Sep 12, 2026
- tonydzi/second-brain-starter-kittheir own version, first seen Sep 8, 2026
- statzhero/zotero-fulltexttheir own version, first seen Apr 8, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- fakechris/obsidian_vault_pipeline★ 165same name
- tonydzi/second-brain-starter-kit★ 6same name
- bibryam/universal-skill-finder★ 5same name
- Jamaalx/claude-chat-namer★ 5same name
- replybr/plugadvpl★ 1same name
- statzhero/zotero-fulltext★ 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.
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 5 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 26
If a result is marked deprecated or superseded, follow its supersedes edge to the current document instead of using it.
“Common” is measured: kept by at least 6 in 10 of the 5 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
Find documentation
!docgov find "$ARGUMENTS" 2>&1 | head -c 10000
How to read this
Results are ordered by authority first, relevance second. That ordering is deliberate: an agent that reads the user guide before the canonical specification writes confidently wrong code.
[CONSTITUTION]/[CANONICAL]— authoritative. Start here. If something below contradicts these, the thing below is wrong.[REQUIREMENTS]/[DECISION]— why it was built this way. ADRs explain decisions you might otherwise reverse by accident.[CONTRACT]— machine-readable and authoritative over any prose about it.[AUDIENCE]— written for a reader, not for precision. Do not treat a guide as a spec.[HISTORICAL]— may be out of date on purpose. Checkstatusbefore believing it.
If a result is marked deprecated or superseded, follow its supersedes edge to the
current document instead of using it.
If nothing relevant comes back
That is a coverage gap, not a search failure. Run docgov health to see whether DocGov
already knows the document is missing, and offer to create it with /docgov:create.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.