brooooo
Skill1 starsChanged 19 days agoMITView on GitHub
Invoke with /brooooo when the agent is going the wrong way, did something wrong, or gave a reply that did not land. The reader is frustrated. Stop, find where you drifted from what they asked, and get back on their track.
In this repository17 other files it gives its agents.
- did-we-break-itSkill
- finish-the-prSkill
- fix-it-properlySkill
- just-tell-meSkill
- lets-build-pyramidsSkill
- next-time-fasterSkill
- no-added-commentsSkill
- onmywatchSkill
- plan-the-big-oneSkill
- sharpenSkill
- show-meSkill
- statechartSkill
- talk-is-cheapSkill
- trust-issuesSkill
- trust-me-broSkill
- walk-me-throughSkill
- you-get-meSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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 16
Do not continue the current plan.
- Distinctive: line 44
Do X, their way. If you cannot tell what X is, ask one short question and wait.
- Distinctive: line 54
Do not comment on your last answer.
- Distinctive: line 55
Keep every fact they need, including anything they must decide or do.
- Distinctive: line 59
No apology paragraph, no "in other words" or "in plain terms", no explaining why you did it.
- Distinctive: line 60
Do not swing to the other extreme.
- Distinctive: line 62
If you have been told the same thing twice, say so in one line and follow it from now on.
≈ “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
brooooo
The reader just said "brooooo". That is frustration: "why are you doing this?" Something in your recent turns went against what they want.
What went wrong, in the reader's words: $ARGUMENTS. If that is empty, find it in step 2.
1. Stop
Do not continue the current plan. Do not finish the step you were on. Do not defend it.
2. Find the drift
Re-read the reader's own messages in this conversation, newest first, and the instructions they gave earlier. Then compare them with what you actually did.
Work out which case this is:
| Case | Sign |
| Wrong direction | You did the opposite of what they asked, or something they did not ask for: a different approach, extra scope, a guess instead of their choice. |
| Wrong result | You broke something, edited the wrong file, ignored an instruction, or claimed something you had not checked. |
| Did not land | Your reply was too long, too dense or too technical to use. |
3. Reply
For a wrong direction or a wrong result, your first sentence names your mistake, before any result or fix. This beats any "answer first" or brevity rule. Examples:
- "You asked for X. I was doing Y."
- "I said the test passes. I had not run it."
- "I deleted the wrong file."
Then:
Wrong direction:
- First line, before anything else: "You asked for X. I was doing Y." Quote or name their words. This beats any "answer first" style rule.
- Undo anything you changed on the wrong path. If undoing is risky or touches something shared, say what you would undo and ask first.
- Do X, their way. If you cannot tell what X is, ask one short question and wait.
Wrong result:
- First line, before anything else: what you did wrong. If you claimed something that was false or unchecked, name the claim: "I said X. That was wrong." or "…I had not checked it." This beats any "answer first" style rule: the admission comes before the fix.
- Fix it, or ask first if the fix is risky.
- Say what is true now and how to see it.
Did not land:
- Do not comment on your last answer. Start straight with the plain version. Say it again in plain words, shorter, starting with what it means for the reader.
- Keep every fact they need, including anything they must decide or do.
Rules
- No apology paragraph, no "in other words" or "in plain terms", no explaining why you did it. Start with the content itself.
- Do not swing to the other extreme. Fix the one thing that was off.
- What they said wins over your earlier plan, your own idea of better, and any skill you were following.
- If you have been told the same thing twice, say so in one line and follow it from now on.
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.