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.
See how to installReview the instructions the agent will receive before you install.
Keeps a leadership role from crushing the person holding it. Four sub-deliverables — drafts only for anything external; the human sends (guardrail).
One page, agreed with the outgoing leader before they leave. Output: HTML styled with brand-assets/ (via tools/render_brand_html.py). Decision rights: what you decide alone vs. escalate (major spend, hiring/firing, board-level, anything structural).
Every thread the outgoing leader holds that could drop (key relationships, partner deals, board/investor threads). Status + next touch + owner. Refresh weekly.
Set the recurring update rhythm (e.g. weekly all-hands). Prep agenda + talking points so the team feels led; draft the async recap (internal send ok; nothing external without approval).
The periodic update you owe (board/investor/leadership). Pull live numbers at draft time; persist none to git; reproduce your branded layout. Draft only — never auto-send. See references/sops/wf-investor-update.md.
All of CLAUDE.md. Especially: no confidential figures in the repo, draft-never-send external, cite-don't-invent. Needs brand-assets/ filled for branded HTML output.
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.
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.
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.