Agent skill

Bro

by luchasarie in luchasarie/bro-skill

Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'.

MITAuto-check passedWriting & Content

Install Bro

skills CLI
$ npx skills add luchasarie/bro-skill --skill bro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install luchasarie/bro-skill bro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bro
GitHub stars
381
Used in
1 other repo
Token cost
~421 tokens
SKILL.md length
226 words
Files
9
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'.

  • Works in 7 steps: Re-explain, don't re-answer. Never… → Simpler, not necessarily shorter. If the… → Facts survive verbatim. Every path,… → …
  • Tasks that involve Plain language and style rules
  • Runs Shell scripts from its folder

What it does

Bro is an agent skill from luchasarie/bro-skill. Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'. Use /bro to get a plain-language version of the last answer.

Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files (for example `README.md`, `examples/consultant-speak.md` and `examples/git-panic.md`).

It sits in Writing & Content, covering Plain language and style rules. The repository describes itself as: 🤙 /bro — re-explains the last answer in plain language, for when the reply made you go 'bro what'. One-file skill for Hermes, Claude Code, Codex, and opencode. The licence is MIT.

When your agent uses it

  • Tasks that involve Plain language and style rules

Example prompts

  • “bro what”
  • “/bro”

Requirements

  • A Bash shell

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Re-explain, don't re-answer. Never answer a new question, never add new information, never use tools. You are only re-expressing what you…
  2. Simpler, not necessarily shorter. If the idea needs space to be clear, take the space. The goal is "impossible to misunderstand", not…
  3. Facts survive verbatim. Every path, command, filename, number, URL, name, and decision stays EXACTLY as it was. Simplify the explanation…
  4. Light bro flavor. Casual and direct ("basically...", "the point is...", "ok so..."). A touch of personality is welcome — don't turn it…
  5. Same language. If your original message was in PT-BR, the simpler version is in PT-BR too ("mano", "basicamente"...). English stays English.
  6. Flatten structure. Drop headers and ceremony. Tables become plain sentences. Keep a short list only if the original genuinely had multiple…
  7. Edge case: if there's no previous assistant message in this conversation, just say there's nothing to simplify yet, bro.

What it can do on your machine

Read from SKILL.md and the folder at commit 3aa8c40. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Shell), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bro loads about 421 tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 226 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~43
When it runs · the whole SKILL.md, loaded when a task matches
~421

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from luchasarie/bro-skill at commit 3aa8c40, republished under its MIT licence (© luchasarie). 226 words, ~421 tokens.

Download SKILL.mdSave it as .claude/skills/bro/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
bro
description
Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'. Use /bro to get a plain-language version of the last answer.
license
MIT

/bro — say it simpler

The user just typed /bro. Your last message didn't land — it was too dense, too jargon-heavy, or too formal.

Your job: re-explain YOUR most recent assistant message in a much simpler way, like you're explaining it to a smart friend over a beer.

Rules

  1. Re-explain, don't re-answer. Never answer a new question, never add new information, never use tools. You are only re-expressing what you already said.
  2. Simpler, not necessarily shorter. If the idea needs space to be clear, take the space. The goal is "impossible to misunderstand", not "fewer words". Cut preamble, hedging, and consultant-speak — keep whatever length real clarity needs.
  3. Facts survive verbatim. Every path, command, filename, number, URL, name, and decision stays EXACTLY as it was. Simplify the explanation around the facts, never the facts themselves.
  4. Light bro flavor. Casual and direct ("basically...", "the point is...", "ok so..."). A touch of personality is welcome — don't turn it into a meme.
  5. Same language. If your original message was in PT-BR, the simpler version is in PT-BR too ("mano", "basicamente"...). English stays English.
  6. Flatten structure. Drop headers and ceremony. Tables become plain sentences. Keep a short list only if the original genuinely had multiple parts.
  7. Edge case: if there's no previous assistant message in this conversation, just say there's nothing to simplify yet, bro.

© luchasarie, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files in the repository root of luchasarie/bro-skill.

  • SKILL.md
  • LICENSE
  • README.md
  • examples/consultant-speak.md
  • examples/git-panic.md
  • examples/kubernetes.md
  • examples/pt-br.md
  • examples/software-architecture.md
  • install.sh

Open the folder on GitHubat commit 3aa8c40

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in luchasarie/bro-skill, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Bro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bro this skillluchasarie/bro-skill3811 repos~421Automated safety check: PassMIT
Asd Ste100danyuchn/asd-ste100-skill4.2k—~4.1kAutomated safety check: PassMIT
Simple Issue Descriptionevery-app/open-seo23k1 repos~1.2kAutomated safety check: PassMIT
Ponytail AuditDietrichGebert/ponytail159k—~1.4kAutomated safety check: PassMIT
Technical Writing Standardcursor/plugins10k10 repos~2.4kAutomated safety check: PassNone
Natural Japanese Business Writingcoji/natural-japanese1.9k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Asd Ste100

    danyuchn/asd-ste100-skill

    A skill your agent uses when English text must be parsed without a human to resolve ambiguity — tool descriptions, error messages, inter-agent instructions, system prompts, status reports — and…

    4.2k GitHub stars~4.1k tokensUpdated 5 days ago
    Writing & ContentAuto-check passed
  • Simple Issue Description

    every-app/open-seo

    Turn a rough bug report, feature request, support note, or pull request into a short, plain-language issue focused on the problem and desired behavior.

    23k GitHub starsUsed in 1 repo~1.2k tokens
    Writing & ContentAuto-check passed
  • Ponytail Audit

    DietrichGebert/ponytail

    Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split.

    159k GitHub stars~1.4k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Writing & ContentAuto-check passed
  • Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.

    1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
    Writing & ContentAuto-check passed
  • Pgjev

    realZachi/pg-jev

    Install, configure, query and explain pgjev (the jev PostgreSQL extension that filters, ranks and classifies rows with plain-language conditions via TypeSafe's Jev model).

    1.1k GitHub stars~2.9k tokensUpdated 3 days ago
    Writing & ContentAuto-check passed

Questions about Bro

What does Bro do?

Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'. Bro is an agent skill from luchasarie/bro-skill. Re-explain the previous assistant message in a much simpler way — for when the reply made you go 'bro what'.

When should I use Bro?

Bro fits situations like: tasks that involve Plain language and style rules.

How do I install Bro in Claude Code?

Run `npx skills add luchasarie/bro-skill --skill bro -a claude-code`. Or copy the skill folder (the luchasarie/bro-skill repository) into .claude/skills/bro in your project. Claude Code loads it when a task matches its description.

How do I install Bro in Codex?

Run `npx skills add luchasarie/bro-skill --skill bro -a codex`. Or copy the skill folder (the luchasarie/bro-skill repository) into .agents/skills/bro in your project. Codex loads it when a task matches its description.

Can I use Bro in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add luchasarie/bro-skill --skill bro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bro, .gemini/skills/bro, .github/skills/bro and .opencode/skills/bro in your project.

What does Bro need to run?

Going by SKILL.md and its folder, Bro needs a shell for the scripts in its folder. Our summary lists: A Bash shell.

Does Bro access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Bro safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bro use?

Bro is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bro use?

About 421 tokens (SKILL.md is roughly 1.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bro?

Skills that share tags, products or a category with Bro: Asd Ste100 (danyuchn/asd-ste100-skill, 4.2k stars), Simple Issue Description (every-app/open-seo, 23k stars), Ponytail Audit (DietrichGebert/ponytail, 159k stars) and Technical Writing Standard (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bro?

luchasarie (a GitHub user) maintains it in luchasarie/bro-skill, which has 381 GitHub stars. The repository was last updated on August 27, 2026.

Source: luchasarie/bro-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.