本文へ移動
cccskills
無料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.

egma-ai/egma
インストール方法を見る

含まれるファイル（1）

  • SKILL.md1.7 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

/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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Same language. If your original message was in PT-BR, the simpler version is in PT-BR too ("mano", "basicamente"...). English stays English.
  6. Flatten structure. Drop headers and ceremony. Tables become plain sentences. Keep a short list only if the original genuinely had multiple parts.
  7. Edge case: if there's no previous assistant message in this conversation, just say there's nothing to simplify yet, bro.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

ask-matt

無料

Ask which skill or flow fits your situation. A router over the skills in this repo.

日本語の概要は準備中です。原文の説明を表示しています。

egma-ai/egma1442026年9月30日 更新

code-review

無料

Review 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".

日本語の概要は準備中です。原文の説明を表示しています。

egma-ai/egma1442026年9月30日 更新

codebase-design

無料

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

日本語の概要は準備中です。原文の説明を表示しています。

egma-ai/egma1442026年9月30日 更新

coordinate-implementation

無料

Drive one ticketed effort through parallel implementation, independent review, serial integration, and one open pull request.

日本語の概要は準備中です。原文の説明を表示しています。

egma-ai/egma1442026年9月30日 更新

diagnosing-bugs

無料

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

日本語の概要は準備中です。原文の説明を表示しています。

egma-ai/egma1442026年9月30日 更新

domain-modeling

無料

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

日本語の概要は準備中です。原文の説明を表示しています。

egma-ai/egma1442026年9月30日 更新

egma-ai のスキルをすべて見る

このスキルの問題を報告する