ask-matt
FreeAsk which skill or flow fits your situation. A router over the skills in this repo.
The English summary is being prepared. Showing the original description.
egma-ai/egma145Updated Sep 30, 2026
FreePublished on GitHub
bro
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.
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md1.7 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
/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
- 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.
- 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.
- 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.
- 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.
- Same language. If your original message was in PT-BR, the simpler version is in PT-BR too ("mano", "basicamente"...). English stays English.
- Flatten structure. Drop headers and ceremony. Tables become plain sentences. Keep a short list only if the original genuinely had multiple parts.
- Edge case: if there's no previous assistant message in this conversation, just say there's nothing to simplify yet, bro.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
code-review
FreeReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
The English summary is being prepared. Showing the original description.
egma-ai/egma145Updated Sep 30, 2026
codebase-design
FreeShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
The English summary is being prepared. Showing the original description.
egma-ai/egma145Updated Sep 30, 2026
Drive one ticketed effort through parallel implementation, independent review, serial integration, and one open pull request.
The English summary is being prepared. Showing the original description.
egma-ai/egma145Updated Sep 30, 2026
diagnosing-bugs
FreeDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
The English summary is being prepared. Showing the original description.
egma-ai/egma145Updated Sep 30, 2026
domain-modeling
FreeBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
The English summary is being prepared. Showing the original description.
egma-ai/egma145Updated Sep 30, 2026