Use when the user needs a written communication drafted in their voice — an email, a Slack/Teams message, a team update, an announcement, a reply to a thread, or a post. Produces a ready-to-review draft matching references/voice.md; never auto-sends external. Trigger on "/draft", "draft an email", "write a reply", "draft the update", "draft the announcement", "respond to this thread in my voice".
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Turn a brief (or a thread) into a ready-to-send-quality draft in the user's voice — fast, on-register, and honest.
/structure or /triage flags an item that needs a reply.**To / channel:** <who> · **Type:** email | slack | update | post · **Register:** internal | external
**Subject / opening line:** <if email>
<the draft — in the user's voice (references/voice.md)>
—
Send call: [internal → I can send in your voice] / [external → draft only, you send]
Open questions: <anything I assumed or couldn't verify>
/structure): audience, outcome, and the one thing they should do or know.references/voice.md; mirror the register (internal vs external split). Don't fake the voice on external content.context/, wiki/, /graph-query, the thread). Anything you can't confirm goes under "Open questions" — never assert it.L2 — drafts; you MAY send internal-to-team in the user's voice. External is always draft-only — the human sends.
No reviews yet. Tell others what you thought.
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.
Use when someone asks for an AIOS audit, asks to score their setup against the Four Cs, or says "is my AIOS working" / "audit my setup" / "find gaps in my AIOS". Produces a Four-Cs scoreboard with top-3 fixes ranked by leverage.
The English summary is being prepared. Showing the original description.
Use at the start of a working day (or when the user asks "what should I focus on today / give me my brief / daily standup"). Produces a one-screen daily brief — today's top 3, open loops that need a nudge, what's slipping, and a suggested focus order. Trigger on "/daily", "daily brief", "what should I focus on today", "morning brief", "standup".
The English summary is being prepared. Showing the original description.
Use when the user faces a real decision with stakes and wants it framed cleanly — options, ranked criteria, a recommendation, the falsifier, and reversibility — then logged to decisions/log.md. Trigger on "/decide", "help me decide", "should I X or Y", "frame this decision", "what's the call here", "log this decision".
The English summary is being prepared. Showing the original description.
Template skill for a leadership-transition / executive cockpit — when someone steps into or covers a leadership role and needs to not drop anything. Produces a handoff doc + decision-rights map, an "open loops" tracker, a team-comms cadence, and a recurring report/update drafter. Trigger on "/exec-cockpit", "handoff doc", "decision-rights map", "open loops tracker", "cover for <role>", "interim <role>". Customize the placeholders to your situation.
The English summary is being prepared. Showing the original description.
Use to run an autoresearch-style experiment loop — improve a measurable artifact by trying changes, measuring against one objective metric, keeping if better and reverting if not, on an isolated git branch with a logged trail. Trigger on "/experiment", "run an experiment loop", "autoresearch X", "tune/optimize X against a metric", "hill-climb X". Follows references/sops/experiment-loop.md. Enforces the autonomy gate (objective metric + reversible sandbox + no PHI/external) before any unsupervised looping.
The English summary is being prepared. Showing the original description.
Use when the user wants to build, refresh, or visualize the repo's knowledge graph — code structure plus the committed wiki/ — via graphify. Produces an interactive graph + a GRAPH_REPORT.md of God Nodes, surprising connections, and suggested questions. Trigger on "/graph", "build the knowledge graph", "graph the repo", "map the codebase", "refresh the graph", "visualize the second brain".
The English summary is being prepared. Showing the original description.