friction
Skill2 starsChanged 19 days agoMITView on GitHub
Scans past build-issue-loop workflow runs for agent friction (skill or tool hunting under ~/.claude, denied or erroring tool calls, repeated failing commands, forbidden actions, self-reported friction, token and tool-call outliers) and reports the patterns seen in two or more runs, each with the deterministic check that would stop it or the prompt line it points to. Use when the user runs /dream-team:friction or asks what keeps going wrong across build-issue runs.
- Commits and pushes
6 other projects use a version of this.
Adopted by
Most recently taken up by
- mira-pi/rsi-skillstheir own version, first seen Nov 1, 2026
- manusco/resonancetheir own version, first seen Oct 22, 2026
- gabo963/claude-skillstheir own version, first seen Oct 15, 2026
- ananmouaz/frictiontheir own version, first seen Oct 13, 2026
- udaysharmadev/Skillstheir own version, first seen Sep 17, 2026
- jorekai/skillstheir own version, first seen Sep 7, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- manusco/resonance★ 38same name
- udaysharmadev/Skills★ 13same name
- mira-pi/rsi-skills★ 2same name
- ananmouaz/friction★ 0same name
- gabo963/claude-skills★ 0same name
- jorekai/skills★ 0same 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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-teamSkill
- assemble-metaSkill
- brainstormSkill
- build-issueSkill
- cut-milestonesSkill
- milestone-closeSkill
- qa-reviewSkill
- review-benchSkill
- scope-commitSkill
- scope-issueSkill
- scope-mrSkill
- scope-specSkill
- setup-dream-teamSkill
- ship-itSkill
- triage-issueSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
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 46
Read the evidence before blaming a prompt or naming a check.
- Distinctive: line 52
No check and no prompt line behind it → list it as ordinary and offer nothing for it.
- Very specific: line 58
No check, a prompt line → <target> is <file>:<line>.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
friction
1. Scan
- Run
python3 <this skill's base directory>/friction.py. - User asks for run times → add
--time; print its table and stop. - The script scans every workflow run not yet in the cache and appends its hits there.
- It prints each pattern + role seen in 2 or more runs; one-off hits stay in the cache only.
- Output is only the
scanned … new runsline → report no repeated friction and stop.
2. Trace each pattern
Pattern names the script prints:
claude-dir: Read/Glob/Grep, or a Bashfind/ls/cat, under~/.claude.tool-error: a tool call denied or erroring, other than a plain non-zero exit.repeat-failure: the same failing Bash command run twice or more by one agent.forbidden:ssh,git push, agh/glabwrite, or an edit, a Bash tree edit (sed/perl -i,git checkout/restore/stash,teeor a redirect to a path outside/tmp/and/dev/) or a commit by a read-only role.self-report: an entry from the agent'sfrictionoutput field.tokens-outlier,tools-outlier: over 2x the role's median over earlier runs.
For each printed pattern:
- Find the prompt that role runs in
<base directory>/../../workflows/build-issue-loop.js:impl→implPrompt,gate→verifyPrompt,build-fix→buildFixPrompt,simplify→simplifyPrompt,simplify-fix→simplifyFixPrompt,review:domain→domainPrompt,review:external→externalPrompt, otherreview:→lensPrompt,re-review:→reReviewPrompt,fixdiff:→fixDiffPrompt,fix→fixPromptornitFixPrompt. - Name the prompt or skill line the evidence points to: the instruction the agent could not follow, or the tool it lacked.
- Read the evidence before blaming a prompt or naming a check; a hook bounce working as designed or a long run on a hard issue has neither behind it.
- A permission rule, hook or gate command could stop the pattern → name that check and what it stops.
- The pattern needs judgement → name no check.
- The only check is a new hook and no written rule forbids what the agent did → name no check.
- No check and no prompt line behind it → list it as ordinary and offer nothing for it.
3. Report
- One bullet per pattern:
- **<pattern> | <role>:** <n> runs; <evidence>; <target>. - A named check →
<target>ischeck: <check>. - No check, a prompt line →
<target>is<file>:<line>. - Ordinary →
<target>isordinary. - Offer to file one dream-team issue per pattern with a check or a prompt line, for its
<target>, written withscope-issue. - File nothing without the user's yes.
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.

