build-workspace-docs
Skill1.1k starsChanged 8 months agoMITView on GitHub
Use when regenerating README.md and WORK_AREAS.md in a managed library workspace. Always dry-run first to preview changes.
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 12
Keep workspace documentation in sync with the skills catalog after adding, removing, or curating skills.
- Very specific: line 16
Always use --dry-run before regenerating docs to preview what will change.
- Very specific: line 17
Only run from inside an initialized library workspace (a directory with .ai-agent-skills/config.json).
- Very specific: line 18
Never hand-edit the generated sections of README.md or WORK_AREAS.md.
- Very specific: line 19
Use --format json to capture structured results for automation pipelines.
- Very specific: line 45
After add, catalog, vendor, or curate commands that change the skills catalog.
- Distinctive: line 46
After bulk imports from a remote library.
- Distinctive: line 47
Before committing workspace changes to git.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
Build Workspace Docs
Goal
Keep workspace documentation in sync with the skills catalog after adding, removing, or curating skills.
Guardrails
- Always use
--dry-runbefore regenerating docs to preview what will change. - Only run from inside an initialized library workspace (a directory with
.ai-agent-skills/config.json). - Never hand-edit the generated sections of README.md or WORK_AREAS.md. The CLI will overwrite them.
- Use
--format jsonto capture structured results for automation pipelines.
Workflow
- Preview what would change.
npx ai-agent-skills build-docs --dry-run- Regenerate the docs.
npx ai-agent-skills build-docs- Verify the output.
npx ai-agent-skills build-docs --dry-run --format jsonThe JSON output includes currentlyInSync to tell you whether docs were already up to date.
When to Run
- After
add,catalog,vendor, orcuratecommands that change the skills catalog. - After bulk imports from a remote library.
- Before committing workspace changes to git.
Gotchas
- Running outside a workspace will fail with a clear error. Use
init-libraryto create one first. - The generated docs use HTML comment markers (
<!-- GENERATED:...:start/end -->) as boundaries. Do not remove these markers from the template sections.
Trending
More talk lately.thin dataabout the whole repository
Who's talking about MoizIbnYousaf/Ai-Agent-Skills
- ProSkillsMD/proskills“[Candidate] moizibnyousaf/ai-agent-skills/skills/backend-development - backend-development”GitHub · Oct 9, 2026
- ProSkillsMD/proskills“[Candidate] moizibnyousaf/ai-agent-skills/skills/audit-library-health - audit-library-health”GitHub · Oct 9, 2026
- ProSkillsMD/proskills“[Candidate] moizibnyousaf/ai-agent-skills/skills/ask-questions-if-underspecified - …”GitHub · Oct 9, 2026
- sudosubin/agents.nix“agent-skills.github.moizibnyousaf.ai-agent-skills: init at 4.3.2”GitHub · Sep 30, 2026
The biggest 4 of 4 mentions linking to the repository that our crawl found. Each line is their own headline.
Other versions2 projects use a version of this.
Word for word · 2
- skillcreatorai/Ai-Agent-Skills★ 1.1k100% same
- MoizIbnYousaf/ai-agent-skills★ 1.1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository17 other files it gives its agents.
- ask-questions-if-underspecifiedSkill
- audit-library-healthSkill
- backend-developmentSkill
- best-practicesSkill
- browse-and-evaluateSkill
- changelog-generatorSkill
- code-documentationSkill
- content-research-writerSkill
- curate-a-team-librarySkill
- database-designSkill
- install-from-remote-librarySkill
- llm-application-devSkill
- migrate-skills-between-librariesSkill
- review-a-skillSkill
- share-a-librarySkill
- update-installed-skillsSkill
- verification-agentSkill
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.

