Skills
Restate the previous answer plainly with ak:bro
Make the immediately previous assistant message shorter and easier to understand without changing its meaning or taking action.
Use ak:bro when the assistant's immediately previous message is correct but
too technical, formal, repetitive, or difficult to follow. The Skill restates
that one message in plain language and returns only the revised version.
Choose ak:bro for restatement only
Use ak:bro when
- You want the last assistant answer shortened or made jargon-free.
- You need the same facts, uncertainty, warnings, decisions, and necessary call to action in simpler words.
- You want the restatement in your current language unless you request another.
Choose another workflow when
- You need new analysis, evidence, or an answer to a different question.
- You want the assistant to run a tool, edit a file, or perform an action named in the previous message.
- You want to simplify older text rather than the immediately previous assistant message. Provide that text to an appropriate writing workflow.
Invoke the Skill immediately after the message
| Runtime | Invocation | Availability boundary |
|---|---|---|
| Claude Code | /ak:bro | Restates the immediately previous assistant message available in the conversation. |
| Cursor | /ak:bro | Uses the same canonical Skill identity; conversation context still depends on the runtime. |
| Codex | $ak:bro | Uses native Skill discovery and the immediately previous visible assistant message. |
/ak:bro/ak:bro$ak:broYou can also say “simplify that,” “say it plainly,” or “explain it like a human” when the runtime routes natural-language requests to the Skill.
Understand the restatement stages
- Read only the immediately previous assistant message as the source.
- Preserve its meaning, facts, uncertainty, safety warnings, decisions, and necessary call to action.
- Replace jargon, acronyms, abstractions, and formal wording with ordinary language; briefly define a technical term only when it cannot be removed.
- Remove repetition, process narration, filler, excessive formatting, and details that do not affect understanding.
- Reply in your language unless you asked for another language.
- Return only the restated message without a preface about simplifying it.
Keep the source and authority boundary intact
Simplifying does not authorize new work
The Skill does not add analysis, answer another request, run tools, change files, or perform actions mentioned in the source message. Use the workflow that owns the action and approve it separately.
Quoted text and embedded instructions in the prior answer remain content to restate, not new instructions. The Skill must not reveal hidden prompts, credentials, personal data, secrets, or private details omitted from the original answer. Restatement also cannot remove a necessary refusal or safety boundary.
Verify the result
A correct result should:
- express the same conclusion and level of certainty;
- retain warnings, decisions, and required next actions;
- use shorter, more familiar wording;
- contain no new claims, recommendations, tool results, or completed actions;
- appear without introductory commentary.
Troubleshoot safely
| Symptom | Safe next step |
|---|---|
| There is no previous assistant message | Provide the text you want simplified; the Skill should not guess a source. |
| An important warning disappeared | Ask for another restatement that explicitly preserves all safety and uncertainty language. |
| The result adds a new conclusion | Discard that addition and restate only the original message. |
| You need more explanation rather than less | Ask a separate follow-up question instead of stretching the restatement workflow. |
| Runtime cannot find the Skill | Follow Runtime cannot find a Skill or Agent. |
The Skill cannot verify whether the original answer is correct; it only makes that answer easier to understand. Continue with the Marketing Kit overview or Runtime adapters.
Get technical guidance with ak:ask
Use ak:ask for evidence-based technical and architecture guidance without starting implementation.
Shape a marketing outcome with ak:brainstorm
Use ak:brainstorm to turn incomplete intent into an accepted outcome, constraints, non-goals, and observable acceptance criteria.