friction-triage
Skill5 starsChanged 33 days agoMITView on GitHub
Triage accumulated Munin friction and prepare or file consolidated Plane tickets routed to their owning repos. Use when the user explicitly asks to review friction signals or turn them into tickets.
In this repository18 other files it gives its agents.
- closeSkill
- cloudflare-private-static-siteSkill
- code-frictionSkill
- commitSkill
- debate-claudeSkill
- debateSkill
- delegateSkill
- eli5Skill
- email-triageSkill
- issuesSkill
- m5-delegateSkill
- magnus-security-reviewSkill
- mimir-searchSkill
- presentifySkill
- review-pr-codexSkill
- ship-itSkill
- ticket-fleetSkill
- user-test-memorySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read references/triage-details.md for the exact sweep-window and suppression rules, then filter the open events.
- Distinctive: line 16
If the user explicitly requests filing, use the same reference for ticket-body handling, board verification, and Munin updates.
- Very specific: line 18
Use /friction-triage report to stop after the proposed table without filing, changing board labels, or writing Munin state.
≈ “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
/friction-triage — Triage accumulated friction
Use this workflow to read the Munin friction corpus, group recurring root causes, separate local fixes from upstream problems, and produce a compact ticket proposal. Filing Plane tickets (including the Grimnir Roadmap board label) or writing Munin state requires explicit user direction; report mode is the default.
Workflow
- Read references/triage-details.md for the exact sweep-window and suppression rules, then filter the open events.
- Group repeated root causes and classify each cluster as locally actionable or upstream/covered.
- Route actionable clusters to the repository that owns the fix.
- Present a compact table before any publication.
- If the user explicitly requests filing, use the same reference for ticket-body handling, board verification, and Munin updates.
Use /friction-triage report to stop after the proposed table without filing, changing board labels, or writing Munin state.
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.