Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Bro?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/ryanportfolio-bro)
---
name: "bro"
description: "Plain-language restatement: 'plain english', 'dumb it down', 'I don't understand', 'what does that mean'."
---
# 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.
1. 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.
2. 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.