maintainer
Skill1 starsChanged 3 months agoMITView on GitHub
Preserve availability, integrity, contributor clarity, and release discipline after a project ships. Use for release review, issue triage, dependency and link audits, incident records, changelogs, policy enforcement, and operational continuity work.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- udecode/platetheir own version, first seen Oct 17, 2026
- patriksimek/vm2their own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- udecode/plate★ 17ksame name
- patriksimek/vm2★ 4.1ksame name
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 repository5 other files it gives its agents.
- builderSkill
- growerSkill
- prototypeSkill
- sweeperSkill
- ux-ui-cx-market-intelligenceSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to keep a property trustworthy after it ships.
- Distinctive: line 18
Verify links, dependencies, structured data, publishing configuration, build output, and public error paths as applicable.
- Distinctive: line 28
Do not silently rewrite history, hide a failure, merge a sensitive change without independent review, disclose security reports, overstate …
≈ “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
Maintainer
Use this skill to keep a property trustworthy after it ships. Maintenance preserves the conditions under which readers, contributors, and operators can rely on what they see.
Intake
Record the affected property, change or incident record, current owner, risk level, user impact, validation plan, rollback or containment plan, and communication owner.
Workflow
- Triage by safety, security, availability, factual accuracy, accessibility, and user impact.
- Review proposed changes against the project charter, contribution policy, security policy, accessibility baseline, and public-claim evidence.
- Verify links, dependencies, structured data, publishing configuration, build output, and public error paths as applicable.
- Publish a concise changelog or incident record for material visible changes. Preserve a private record for sensitive details.
- Maintain a clear backlog and escalate unowned risk rather than allowing silent debt.
Deliverable
Provide a reviewed release note, triage outcome, validation evidence, changelog, and any incident or decision record needed. State operational condition, deferred changes, residual-risk owner, rollback owner, and next scheduled review.
Boundaries
Do not silently rewrite history, hide a failure, merge a sensitive change without independent review, disclose security reports, overstate availability or compliance, or use maintenance to erase evidence.
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.