agentleFS
Sign inStart free
drafaeldrafael/coding-harness/skills/bro/SKILL.md

bro

Skill1 starsChanged 6 months agoMITView on GitHub

Restate the assistant's last message in plain, concise human language without jargon. Manual invocation only; use when the user explicitly invokes bro or asks for that restatement. Do not turn it into a new explanation or investigation.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 24 edited versions we read keep these.

  • 3

    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:

    Run only after an explicit request.

    line 12
  2. Distinctive:

    Keep identifiers, commands, links, or paths when the user needs them to act.

    line 16
  3. Distinctive:

    Do not add claims, forced slang, a patronizing tone, or a summary that loses the point.

    line 17

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

Restate your last substantive message as one person talking to another. Use plain words, short sentences, and less jargon.

Run only after an explicit request. Rewrite the message; do not investigate, use tools, change files, or take the next step in the task.

  • Preserve its meaning, facts, uncertainty, warnings, and any decision waiting on the user.
  • Explain an unavoidable technical term briefly rather than replacing it with something inaccurate.
  • Keep identifiers, commands, links, or paths when the user needs them to act; otherwise leave out distracting detail.
  • Do not add claims, forced slang, a patronizing tone, or a summary that loses the point.

Return only the restatement, without a preamble or a change report. If no earlier substantive assistant message is available, say so briefly instead of inventing one.

Download now (ZIP)

  • Other versions100 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 100

    1. backnotprop/pstack★ 3.3ksame name
    2. dmmulroy/skills★ 428same name
    3. luchasarie/bro-skill★ 385same name
    4. backnotprop/bro★ 166same 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★ 19same name
    10. Sapere-IA/sdd-onboarding-kit★ 19same name

    90 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 poteto-help, addskill 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.
    • 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 14 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

    • 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 20 projects that use this

    • +8 more from ryanportfolio
  • In this repository31 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