vault-search
Skill6 starsChanged 3 months agoNo licenceView on GitHub
Query the knowledge-iop vault as a habit before drafting anything. Before you write a new problem-brief, design-brief, inquiry, decision, discussion, scope, or arc, first check whether a relevant artifact already exists so you can supersede, relate to, or frame from it — rather than orphan your work. Use this whenever the user says things like "what do we know about X", "is there already a brief on Y", "show me the design for Z", "find related artifacts", "what's the status of...", or before any phase skill (frame-problem, propose-design, record-decision, ...). The underlying programmatic tools are vault_search, vault_edges, and vault_check_transition — this skill teaches when to reach for each.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- c-ibarra/ObsidianKnowledgeCuratortheir own version, first seen Oct 9, 2026
- AGMO-Inc/agmo-everywheretheir own version, first seen Mar 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- AGMO-Inc/agmo-everywhere★ 4same name
- c-ibarra/ObsidianKnowledgeCurator★ 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 repository26 other files it gives its agents.
- document-featureSkill
- recommend-skillsSkill
- seed-skill-templateSkill
- architecture-diagramSkill
- catchupSkill
- dataflow-diagramSkill
- engineering-journalSkill
- format-layout-diagramSkill
- review-exchangeSkill
- review-guideSkill
- rust-source-layoutSkill
- sharable-artifactSkill
- sweep-commentsSkill
- technical-proseSkill
- close-arcSkill
- define-scopeSkill
- discussSkill
- frame-problemSkill
- open-arcSkill
- open-inquirySkill
- plan-featureSkill
- propose-designSkill
- reconcile-vaultSkill
- record-decisionSkill
- submit-explorationSkill
- synthesizeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.