maintainer-brief
Skill0 starsChanged 5 months agoMITView on GitHub
Prepare source-backed maintainer briefs from issue, PR, release, or research context without hiding evidence gaps.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- capture-fixture-verificationSkill
- pr-draft-summarySkill
- release-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 when preparing context for an issue response, pull request review, release decision, or follow-up investigation.
- Distinctive: line 21
Keep source links visible.
- Distinctive: line 23
Do not smooth over missing evidence.
- Distinctive: line 24
Prefer Markdown artifacts that can be reviewed outside chat.
≈ “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 Brief
Use this skill when preparing context for an issue response, pull request review, release decision, or follow-up investigation.
Output Shape
- Summary
- Sources reviewed
- Evidence found
- Evidence gaps
- Maintainer decision points
- Follow-up tasks
Rules
- Keep source links visible.
- Separate verified evidence from inference.
- Do not smooth over missing evidence.
- Prefer Markdown artifacts that can be reviewed outside chat.
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.