Use when the user says an explanation was unclear, too technical, or full of jargon, or asks for plain language.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Bro
When invoked without an argument after a reply, restate that reply with the [writing contract](../../shared/writing.md).
Keep every relevant fact.
Otherwise, read the writing contract again and apply it to all later natural-language text.
Do not change code style.
Assume the reader has little project context.
Explain what happens, why it matters, and how the real workflow behaves.
Use simple, concrete words without removing necessary technical detail.
The line at the top of this page pins the label git:20260919.a9f7da5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_jtfc7cuoshp4hf3w
GET https://markdownregistry.com/api/v1/resolve?ref=reidemeister94/development-skills/bro
GET https://markdownregistry.com/api/v1/blob/6aae1b68554a833eea7cc43bc2283245c81c8d6790465540a0280a3f0d07d050
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
reidemeister94/development-skills · skills/ai-agent-bench/SKILL.md · Compare Claude Code and Codex on the same code task, with isolated worktrees, common checks, time, and cost.
reidemeister94/development-skills · skills/align-docs/SKILL.md · Align stale repository docs and task records; use --clean for a full documentation cleanup.
reidemeister94/development-skills · skills/best-practices/SKILL.md · Research current practices or compare approaches using primary evidence and the user's constraints.
reidemeister94/development-skills · skills/brainstorming/SKILL.md · Use when the user wants to brainstorm, choose an approach, design something, or clarify an ambiguous or consequential…
reidemeister94/development-skills · skills/changelog/SKILL.md · Add CHANGELOG.md entries, derive them from commits, or cut a Keep a Changelog and SemVer release.
reidemeister94/development-skills · skills/eval-regression/SKILL.md · Check skill routing or behavior, investigate a regression, or compare plugin changes with a base commit.
reidemeister94/development-skills · skills/evolve-loop/SKILL.md · Autonomous /goal loop that rethinks a project's design and adds features and improvements that can change its behavior…
nightly-labs/openbot · marketplace/production-catalog/bundles/pstack/skills/bro/SKILL.md · Restate the last message in plain human language, with no jargon.
michael-denyer/pstack-claude · plugins/pstack/skills/bro/SKILL.md · Restate the last message in plain human language, with no jargon. Use for /bro or when asked to say it plainly.
davepoon/buildwithclaude · plugins/all-skills/skills/bro/SKILL.md · Re-explain the previous assistant message, or any text typed after the command, in a much simpler way. For when a reply…
ericrisco/rsc-harness · skills/bro/SKILL.md · Use whenever the user asks to make an answer or draft sound human, natural, plain-spoken or less AI-written — including…
