agent-skill-manager
CLAUDE.md1 starsChanged 3 months agoMITView on GitHub
This repository uses AGENTS.md as the canonical project brief for all agents. Before making code or documentation changes: After non-trivial work that creates reusable knowledge, update the relevant wiki topic/source pages and append to docs/wiki/log.md. The wiki is a synthesis layer; verify current behavior against code and tests and keep accepted product decisions in AGENTS.md and the relevant planning file. Do not implement behavior that contradicts the decisions recorded in AGENTS.md without first updating the plan with the user.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- video/AGENTS.mdAGENTS.md
- skill-advisorSkill
The file
Show its rules and text
We split this CLAUDE.md into the rules it gives an agent
21 rules. About 0 are common, 20 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
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
- Distinctive: line 5
Before making code or documentation changes:
- Distinctive: line 8
Read docs/wiki/README.md and docs/wiki/index.md, then open the topic pages relevant to the task.
- Distinctive: line 9
If working on the MVP implementation, read planning/phase-1-mvp-tasks.md.
- Distinctive: line 10
If working on group or bulk toggle behavior, read planning/phase-2-group-bulk-toggle-tasks.md.
- Distinctive: line 11
If working on repository installation behavior or documentation, read planning/phase-3-repo-install-tasks.md.
- Distinctive: line 12
If working on repository update or uninstall behavior or documentation, read planning/phase-4-repo-update-uninstall-tasks.md.
- Distinctive: line 13
If working on local path install or uninstall behavior or documentation, read planning/phase-5-local-path-install-tasks.md.
- Distinctive: line 14
If working on the desktop app, read the relevant Phase 6-10 planning file.
- Distinctive: line 15
If working on publication or repository hygiene, read planning/phase-11-publication-readiness-tasks.md.
- Distinctive: line 16
If working on GitHub release artifacts, read planning/phase-12-github-release-tasks.md.
- Distinctive: line 17
If working on managed checkout diagnosis or repair, read planning/phase-21-checkout-repair-tasks.md.
- Distinctive: line 18
If working on reporting or installing skills added to a managed repository after install, read …
- Distinctive: line 19
If working on installing skills directly as OFF, read planning/phase-23-install-as-off-tasks.md.
- Distinctive: line 20
If working on optional TypeSafe recommendations or BYOK settings, read planning/phase-24-typesafe-advisor-tasks.md.
- Distinctive: line 21
If working on duplicate skill names inside one install source, read planning/phase-25-duplicate-skill-discovery-tasks.md.
- Very specific: line 22
If working on installing a skill under another name when another source owns its name (--as), read …
- Distinctive: line 23
If working on removing some recorded skills from a source, or on the update failure when a repository removed an installed skill, read …
- Distinctive: line 24
If working on the desktop advisor receipts view or on forgetting a blocked advisor receipt, read …
- Distinctive: line 25
Follow the task status rules in the relevant planning file before starting and after finishing work.
- Distinctive: line 27
After non-trivial work that creates reusable knowledge, update the relevant wiki topic/source pages and append to docs/wiki/log.md.
- Distinctive: line 29
Do not implement behavior that contradicts the decisions recorded in AGENTS.md without first updating the plan with the user.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
Claude Code Guidance
This repository uses AGENTS.md as the canonical project brief for all agents.
Before making code or documentation changes:
- Read AGENTS.md.
- Read docs/wiki/README.md and docs/wiki/index.md, then open the topic pages relevant to the task.
- If working on the MVP implementation, read planning/phase-1-mvp-tasks.md.
- If working on group or bulk toggle behavior, read planning/phase-2-group-bulk-toggle-tasks.md.
- If working on repository installation behavior or documentation, read planning/phase-3-repo-install-tasks.md.
- If working on repository update or uninstall behavior or documentation, read planning/phase-4-repo-update-uninstall-tasks.md.
- If working on local path install or uninstall behavior or documentation, read planning/phase-5-local-path-install-tasks.md.
- If working on the desktop app, read the relevant Phase 6-10 planning file.
- If working on publication or repository hygiene, read planning/phase-11-publication-readiness-tasks.md.
- If working on GitHub release artifacts, read planning/phase-12-github-release-tasks.md.
- If working on managed checkout diagnosis or repair, read planning/phase-21-checkout-repair-tasks.md.
- If working on reporting or installing skills added to a managed repository after install, read planning/phase-22-new-skill-discovery-tasks.md.
- If working on installing skills directly as OFF, read planning/phase-23-install-as-off-tasks.md.
- If working on optional TypeSafe recommendations or BYOK settings, read planning/phase-24-typesafe-advisor-tasks.md.
- If working on duplicate skill names inside one install source, read planning/phase-25-duplicate-skill-discovery-tasks.md.
- If working on installing a skill under another name when another source owns its name (
--as), read planning/phase-26-cross-source-skill-alias-tasks.md. - If working on removing some recorded skills from a source, or on the update failure when a repository removed an installed skill, read planning/phase-27-source-skill-removal-tasks.md.
- If working on the desktop advisor receipts view or on forgetting a blocked advisor receipt, read planning/phase-28-advisor-receipts-view-tasks.md.
- Follow the task status rules in the relevant planning file before starting and after finishing work.
After non-trivial work that creates reusable knowledge, update the relevant wiki topic/source pages and append to docs/wiki/log.md. The wiki is a synthesis layer; verify current behavior against code and tests and keep accepted product decisions in AGENTS.md and the relevant planning file.
Do not implement behavior that contradicts the decisions recorded in AGENTS.md without first updating the plan with the user.
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.

