agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/agentic-loops/skills/bro/SKILL.md

bro

Skill5 starsChanged 20 days agoMITView on GitHub

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 simpler version of the last answer in Plain Language + Chicago Manual of Style, with diagrams where they help.

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 7

    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
  1. Distinctive:

    Explain again. Do not answer again: Never answer a new question.

    line 15
  2. Distinctive:

    Simpler, not necessarily shorter: If the idea needs space to be clear, use the space.

    line 16
  3. Distinctive:

    Use Plain Language + Chicago Manual of Style: Do not use em-dashes.

    line 18
  4. Distinctive:

    Add diagrams where they help: If the idea is a data flow or a control flow, add a diagram.

    line 19
  5. Distinctive:

    Same language: If your original message was not in English, write the simpler version in that language, with the same short, simple …

    line 20
  6. Distinctive:

    Flatten the structure: Remove headers and ceremony.

    line 21
  7. Distinctive:

    Edge case: if this conversation has no previous assistant message, say that there is nothing to simplify yet.

    line 22

“Common” is measured: kept by at least 6 in 10 of the 20 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/bro: say it simpler

The user typed /bro. Your last message was not clear to the user. It was too dense, had too much jargon, or was too formal.

Your task: explain YOUR most recent assistant message again in a much simpler way.

Rules

  1. Explain again. Do not answer again. Never answer a new question. Never add new information. Never use tools. Exception: you can read the diagram rules in rule 5. Only say again what you already said, in a different way.
  2. Simpler, not necessarily shorter. If the idea needs space to be clear, use the space. The goal is "impossible to misunderstand", not "fewer words". Remove preamble, hedging and consultant-speak. Keep the length that real clarity needs.
  3. Keep the facts exactly. Each path, command, filename, number, URL, name and decision stays EXACTLY the same. Make the explanation around the facts simpler. Never change the facts.
  4. Use Plain Language + Chicago Manual of Style. Do not use em-dashes.
  5. Add diagrams where they help. If the idea is a data flow or a control flow, add a diagram. Follow the diagram rules.
  6. Same language. If your original message was not in English, write the simpler version in that language, with the same short, simple sentences.
  7. Flatten the structure. Remove headers and ceremony. Change tables into plain sentences or a diagram. Keep a short list only if the original really had more than one part.
  8. Edge case: if this conversation has no previous assistant message, say that there is nothing to simplify yet.

Download now (ZIP)

  • Other versions96 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 4

    1. luchasarie/bro-skill★ 38514% same
    2. cassiorox/ClaudePRO★ 827% same
    3. snowfluke/engineering-skills★ 127% same
    4. tslateman/skills★ 123% same

    Wrote their own version · 92

    1. backnotprop/pstack★ 2.7ksame name
    2. dmmulroy/skills★ 428same name
    3. backnotprop/bro★ 166same name
    4. sammcj/agentic-coding★ 164same name
    5. jtaroreh/agystack★ 128same name
    6. uzairansaruzi/p3-stack★ 126same name
    7. dsebban/skills★ 71same name
    8. roerohan/skills★ 29same name
    9. ivanrvpereira/.agents★ 18same name
    10. Sapere-IA/sdd-onboarding-kit★ 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 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.
    • alexnthnzSkill

      in-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

    • ianclearySkill

      poteto-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-AtaraxiaSkill

      make-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

    • ryanportfolioSkill

      addskill

      Create, import, update, or install repository or personal skills; includes runtime ownership, resources, and discovery validation.

      Also in 5 projects that use this

    • ryanportfolioSkill

      astra-fullreview

      Full multi-agent Codex review on gpt-6-astra at medium reasoning. Same verified lifecycle as codex-fullreview. Use for /astra-fullreview or 'full Astra review with sub-reviewers'.

      Also in 5 projects that use this

    • jtarorehSkill

      poteto-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

    • +6 more from ryanportfolio
  • In this repository3 other files it gives its agents.

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.

Check your setup, free