doc-garden
Skill0 starsChanged 4 months agoMITView on GitHub
Audit and refresh repository documentation when asked to garden docs, find stale or broken knowledge-base references, check local links or anchors, review verified-date freshness, identify references to deleted paths, or prepare a documentation cleanup report or patch. Use for read-only scheduled documentation health checks and explicitly authorized fix-up changes or pull requests.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/templates.mdcCursor rule
- llms.txtllms.txt
- doc-gardenSkill
- releaseSkill
- verify-liveSkill
- doc-gardenSkill
- releaseSkill
- verify-liveSkill
- releaseSkill
- verify-liveSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 16
Read that file for the full skill before starting.
≈ “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.
Files
Document Garden
Canonical source: .agents/skills/doc-garden/SKILL.md
Read that file for the full skill before starting. This stub only registers the skill with the harness — edit the canonical file, then run bash scripts/harness/sync.
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.