maintain-project-skills
Skill0 starsChanged 31 days agoUnlicenseView on GitHub
Installs, updates, or migrates project-local skills from their verified upstream source while preserving local ownership and pins. Use when asked to add, refresh, or migrate a project's local skills.
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
Keep project Agent Skills reproducible without turning generated payloads into hand-authored files.
- Distinctive: line 24
Do not copy the scheduled runtime into a consumer, install KGR globally, edit CLI-generated payloads or hashes by hand, or merge an …
≈ “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
Maintain project Agent Skills
Keep project Agent Skills reproducible without turning generated payloads into hand-authored files. This playbook maintains callers and exceptional migrations; the reusable workflow owns scheduled refresh mechanics.
Read
the project-skills maintenance runbook
when adding or changing a caller, migrating a deleted or renamed inventory
entry, declaring a skill's role in the generated AGENTS.md skills block, or
diagnosing a failed run. It holds the caller shape and permissions,
immutable-pinning rules, migration evidence requirements, role declarations,
and failure branches.
Do not copy the scheduled runtime into a consumer, install KGR globally, edit CLI-generated payloads or hashes by hand, or merge an automation PR. Use the consumer's validated project root and pinned skills CLI for every inventory mutation.
Completion
- The caller remains thin and pins an immutable reusable-workflow revision.
.agents/skillsandskills-lock.jsonchanged only through the pinned skills CLI or the workflow's opt-in deterministic hash normalization.- Inventory membership changes have source evidence and were reviewed as a migration.
- The caller's workflow validation passes, and any resulting PR remains draft for normal project review; nothing was merged automatically.
In this repository26 other files it gives its agents.
- address-feedbackSkill
- agent-behavior-auditSkill
- agent-writingSkill
- bleeding-edgeSkill
- codebase-auditSkill
- code-reviewSkill
- convex-conventionsSkill
- create-issueSkill
- create-prSkill
- create-releaseSkill
- deep-diveSkill
- deliverSkill
- delivery-waitSkill
- git-workflowSkill
- implementSkill
- milestone-rushSkill
- native-nostalgia-stackSkill
- project-structureSkill
- react-stackSkill
- roadmap-reviewSkill
- run-retroSkill
- software-engineering-excellenceSkill
- status-reportSkill
- test-against-specSkill
- typescript-stackSkill
- update-prSkill
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.