validate-context
Skill253 starsChanged 10 months agoMITView on GitHub
Validate .context/ files for quality, staleness, and conformance to the Substrate methodology. Run after making changes to documentation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- albertomarturelo/siitheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- albertomarturelo/sii★ 19same 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-adrSkill
- generate-tool-configSkill
- new-domainSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 15
Broken links: Check that all markdown links to other .context/ files point to files that exist
- Very specific: line 16
Index sync: Verify CLAUDE.md and AGENTS.md reference all files that exist in .context/
- Distinctive: line 18
ADR completeness: Check all ADRs have Status, Context, Decision, and Consequences sections
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Validate the .context/ documentation for quality and conformance.
Checks to perform
- File size: Flag any
.context/file over 200 lines (context bloat risk) - Required sections: Each domain file should have Overview, Implementation Patterns, and Decision History sections
- Broken links: Check that all markdown links to other
.context/files point to files that exist - Index sync: Verify
CLAUDE.mdandAGENTS.mdreference all files that exist in.context/ - Stale content: Flag files that reference patterns or technologies not present in the codebase
- ADR completeness: Check all ADRs have Status, Context, Decision, and Consequences sections
Output format
Report findings as:
Passed
- List of checks that passed
Issues Found
- File: issue description
- Suggested fix
Recommendations
- Any improvements to documentation quality
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.

