setup-wiki-backed-project-skills
Skill4 starsChanged 4 months agoMITView on GitHub
Set up a repository-local skill for creating project skills whose canonical procedures live in docs/wiki.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- build-incrementalSkill
- code-simplifySkill
- create-or-clone-repositorySkill
- design-firstSkill
- implementation-workflowSkill
- manage-git-worktreesSkill
- plan-driven-developmentSkill
- subagent-supervisionSkill
- task-briefSkill
- test-driven-debugSkill
- tidy-firstSkill
- write-personal-wikiSkill
- write-project-wikiSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the repository's AGENTS.md and documentation conventions.
- Distinctive: line 18
If repository instructions conflict with this convention or its adoption is unclear, explain the issue and stop without changing the …
- Distinctive: line 24
Check for an equivalent workflow or skill.
- Distinctive: line 31
Follow repository naming and skill placement conventions, adjusting relative links as needed.
- Distinctive: line 33
Add the workflow to the wiki index, creating the index if needed.
- Distinctive: line 39
Run the skill validator when available and git diff --check.
≈ “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
Set Up Wiki-backed Project Skills
Install the bundled wiki workflow and repository-local routing skill.
Applicability
Read the repository's AGENTS.md and documentation conventions.
Proceed when docs/wiki is already used as the project wiki or AGENTS.md
explicitly prescribes that convention. Create the necessary directories
if the convention is prescribed but they do not exist yet.
If repository instructions conflict with this convention or its adoption is unclear, explain the issue and stop without changing the documentation structure.
Install
- Check for an equivalent workflow or skill. Update existing equivalents instead of creating duplicates, preserving project-specific customizations.
- Install the bundled templates:
assets/wiki-backed-project-skills.md→docs/wiki/workflows/wiki-backed-project-skills.mdassets/create-wiki-backed-project-skill.md→.agents/skills/create-wiki-backed-project-skill/SKILL.md
- Follow repository naming and skill placement conventions, adjusting relative links as needed.
- Add the workflow to the wiki index, creating the index if needed.
Verify
- The repository skill's relative link resolves to the wiki workflow.
- The wiki contains the full procedure; the skill provides discovery and routing.
- Run the skill validator when available and
git diff --check.
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.