agentleFS
ryanportfolioryanportfolio/Harness-Firmware/.agents/skills/bro/SKILL.md

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

    Keep every fact, number, caveat, link, path, and command.

    line 10
  2. Distinctive:

    Do not redo the task, start a review, or change the standing style.

    line 22

“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.

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

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.

Download now (ZIP)

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.