bro
Skill1 starsChanged 21 days agoMITView on GitHub
Plain-language restatement. Use on $bro anywhere in a message, \"plain english\", \"plain language\", \"dumb it down\", \"I don't understand\", or \"what does that mean\".
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
2
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 10
Keep every fact, number, caveat, link, path, and command.
- Distinctive: line 22
Do not redo the task, start a review, or change the standing style.
“Common” is measured: kept by at least 6 in 10 of the 17 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
Both uses follow these rules:
- Keep every fact, number, caveat, link, path, and command. Before sending, check each one against the original. Add no claim the original did not make.
- Full sentences for this one reply (an explicit request overrides
$caveman), then return to the standing style. - Everyday words instead of jargon. At most one term keeps a gloss; every other term gets replaced by a plain word or cut.
- Come in shorter than the original.
Explain (default)
Target: your previous reply, or the term or passage the user names. "Make that shorter" or "more to the point" about your own reply also lands here.
- Bottom line up front: open with what it means for the user in practice and what they need to do or decide. If nothing, say so.
- Then give the reason in a few sentences.
Do not redo the task, start a review, or change the standing style.
Plain pass on a deliverable
When the user aims $bro at a draft, file, or pasted text (email, forum post, page copy, doc): rewrite that text itself, not an explanation of it, under the $writing skill's rules at their plainest, with short sentences and one idea each, in the user's own voice. Deliver the rewritten text; do not ask first.
Other versions96 projects use a version of this.
Word for word · 3
- ryanportfolio/Corewise.Academy★ 1100% same
- ryanportfolio/savetokens★ 1100% same
- ryanportfolio/STK★ 1100% same
Edited · 1
- ryanportfolio/HarnessFirmware.com★ 096% same
Wrote their own version · 92
- backnotprop/pstack★ 2.7ksame name
- dmmulroy/skills★ 428same name
- luchasarie/bro-skill★ 385same name
- backnotprop/bro★ 166same name
- sammcj/agentic-coding★ 164same name
- jtaroreh/agystack★ 128same name
- uzairansaruzi/p3-stack★ 126same name
- dsebban/skills★ 71same name
- roerohan/skills★ 29same name
- ivanrvpereira/.agents★ 18same name
82 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.
Used alongsideProjects with it also use in-your-own-words, poteto-help and 2 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.
alexnthnzSkillin-your-own-words
Restate in your own words what you think the user's goals are and what problem they're trying to solve. Use for /keel:in-your-own-words.
Also in 9 projects that use this
ianclearySkillpoteto-help
Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.
Also in 9 projects that use this
Xia-AtaraxiaSkillmake-bot-ui
Builds a small web page whose buttons wake an agent over a webhook: a local server keeps the sender key server-side and POSTs JSON to a webhook-triggered routine, and the page is exposed on the existing Tailscale node. Use for \"make a bot UI\", \"a dashboard with buttons that trigger the agent\", \"wake the bot from a page\", handing a webhook sender key to the server without pasting it in chat, or putting that UI on the tailnet. Not for general frontend work - use principle-frontend; not for tailnet health or reachability - use tailscale.
Also in 17 projects that use this
jtarorehSkillpoteto-mode
poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.
Also in 5 projects that use this
In this repository85 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- addskillSkill
- adopt-repoSkill
- advocateSkill
- apply-firmwareSkill
- arenaSkill
- astra-reviewSkill
- babysit-ciSkill
- brainstormingSkill
- cache-loopSkill
- cavemanSkill
- claude-reviewSkill
- codex-reviewSkill
- dareSkill
- deep-planSkill
- design-prototypesSkill
- enhance-promptSkill
- external-reviewSkill
- fable-modeSkill
- forge-repo-ui-skillSkill
- handoff-auditSkill
- impartial-reviewSkill
- init-projectSkill
- labSkill
- long-horizonSkill
- optimize-contextSkill
- opus-fullreviewSkill
- perf-loopSkill
- recallSkill
- redesign-conceptsSkill
- refineSkill
- serversSkill
- session-hubSkill
- showpieceSkill
- sync-starterSkill
- whySkill
- wow-loopSkill
- wrapupSkill
- writing-plansSkill
- writingSkill
- addskillSkill
- adopt-repoSkill
- advocateSkill
- apply-firmwareSkill
- arenaSkill
- astra-fullreviewSkill
- astra-reviewSkill
- babysit-ciSkill
- brainstormingSkill
- broSkill
- cache-loopSkill
- cavemanSkill
- claude-reviewSkill
- codex-fullreviewSkill
- codex-image-genSkill
- codex-reviewSkill
- coordinateSkill
- dareSkill
- deep-planSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

