bro
Skill19 starsChanged 38 days agoMITView on GitHub
Re-explain something concisely in plain language. Use when the developer says there is too much text, does not understand a message, a spec item (REQ-003, A1, Q2, T1), a file, a term or a concept, and wants it simply.
109 other projects use a version of this.
Adopted by
Most recently taken up by
- marmot-protocol/mdktheir own version, first seen Nov 9, 2026
- Yeachan-Heo/oh-my-claude-sisyphustheir own version, first seen Nov 8, 2026
- caidanw/skillstheir own version, first seen Nov 8, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 8, 2026
- endqwerty/endstacktheir own version, first seen Nov 8, 2026
- tristanphvn/keeltheir own version, first seen Nov 8, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
- ryanportfolioSkill
apply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions109 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 109
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- backnotprop/pstack★ 3.8ksame name
- dmmulroy/skills★ 428same name
- luchasarie/bro-skill★ 385same name
- backnotprop/bro★ 176same name
- jtaroreh/agystack★ 128same name
- uzairansaruzi/p3-stack★ 126same name
- dsebban/skills★ 71same name
- marmot-protocol/mdk★ 69same name
99 more not listed
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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- closingSkill
- context-auditSkill
- decision-logSkill
- dependency-freshnessSkill
- documentation-updateSkill
- failure-learningSkill
- git-disciplineSkill
- goblin-modeSkill
- project-mapSkill
- run-and-verifySkill
- spec-from-screenshotSkill
- ui-qaSkill
- sdd-updateSkill
- sdd-workflowSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 27 edited versions we read keep these.
6
Distinctive
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 42
Add no new claims: every statement must come from the source.
- Distinctive: line 43
If the source is ambiguous or contradicts itself, say so in one line instead of guessing what it meant.
- Distinctive: line 44
Do not repeat or quote the original text back.
- Distinctive: line 45
Do not change any file, task state or memory.
- Distinctive: line 46
Do not pad: no preamble, no recap of what was asked, no headings beyond the contract.
- Distinctive: line 47
If the developer asks to go deeper, answer only the part they named, with the same plain style.
“Common” is measured: kept by at least 6 in 10 of the 27 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
Bro — say it simply
Purpose
The developer got too much text, or text they do not follow. Re-explain it short and plain. This skill only explains: it never decides, implements or edits.
What to explain
- No argument: your previous message in this conversation.
- Pasted text: that text.
- A file path: that file (or the part the developer points at).
- A spec ID (
REQ-003,A1,Q2,T1,TASK-001…): find it underspecs/(andtasks.jsonfor task IDs). If it matches more than one spec, ask which feature, or use the active task's spec and say so. If not found, say so and stop. - A term or concept: explain it as it applies to this project; read the project map or
AGENTS.mdonly if the meaning is project-specific.
Output contract
Reply in the developer's language. At most ~150 words in total.
**TL;DR:** <one line>
<Plain-words explanation: short sentences, no jargon — or define each
term the first time. One everyday analogy only if it really helps.>
**What this means for you:** <the practical consequence, 1–2 lines>
**What you need to decide:** <only if there is a pending decision: the
choice, the options, the recommended one>
Want me to go deeper on any part?Drop "What you need to decide" when nothing is pending. Keep the last line as a single short offer.
Rules
- Add no new claims: every statement must come from the source. No new facts, risks, recommendations or numbers.
- If the source is ambiguous or contradicts itself, say so in one line instead of guessing what it meant.
- Do not repeat or quote the original text back; rephrase it.
- Do not change any file, task state or memory. Read only.
- Do not pad: no preamble, no recap of what was asked, no headings beyond the contract.
- If the developer asks to go deeper, answer only the part they named, with the same plain style.
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.