exec-cockpit
$
npx mdskill add alirezarezvani/gaios/exec-cockpitPrevents leadership gaps by automating handoff and reporting.
- Solves sudden role changes where critical context is lost.
- Depends on HTML rendering tools, brand assets, and live data APIs.
- Decides scope based on user intent like 'handoff doc' or 'cover for'.
- Delivers structured docs, trackers, cadences, and draft reports.
SKILL.md
.github/skills/exec-cockpitView on GitHub ↗
--- name: exec-cockpit 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. --- # Exec cockpit (template) Keeps a leadership role from crushing the person holding it. Four sub-deliverables — **drafts only for anything external; the human sends** (guardrail). ## 1. Handoff doc + decision-rights map *(do first)* 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). ## 2. "Open loops" tracker Every thread the outgoing leader holds that could drop (key relationships, partner deals, board/investor threads). Status + next touch + owner. Refresh weekly. ## 3. Team-comms cadence 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). ## 4. Recurring report drafter 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`. ## Guardrails 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.
More from alirezarezvani/gaios
- draftUse 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".
- graphUse 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".
- graph-ingestUse when the user brings an external source worth keeping — a URL, a paper, a tweet/thread, a blog post, a docs page — and wants it pulled into the second brain. Fetches the source into the git-ignored capture inbox, admits it to the committed wiki through the admission policy, then refreshes the knowledge graph so it joins the rest of your thinking. Trigger on "/graph-ingest", "ingest this url", "add this paper to my knowledge", "add this tweet/page to my knowledge", "capture this source".
- graph-queryUse when the user asks a question about how things in the codebase or wiki relate — what connects two things, how something works end to end, what depends on what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with source-location citations. Trigger on "/graph-query", "ask the graph", "what connects X to Y", "trace how X works", "explain <concept> from the graph", "shortest path between".
- level-upUse weekly to find and ship one new automation. Walks the 3Ms interview — Mindset (find the candidate) → Method (scope one) → Machine (build it). Trigger on "let's level up", "what should I automate next", "find me leverage this week", or as a Friday ritual. One run = one shipped artifact.
- prepUse when the user has a meeting, call, 1:1, a person to meet, or a decision coming up and needs to walk in prepared. Assembles a one-page brief from context/, wiki/, connections, open loops, and the knowledge graph — who · what · goal · history · open loops · the ask · risks. Trigger on "/prep", "prep me for", "brief me on <person/meeting>", "what do I need to know before", "get me ready for".
- structureUse when the user brings any fuzzy, half-formed, or interrupt-driven input — an order from a boss, a forwarded email thread, a ticket, a chat message, a "can you look into X", a raw idea — and it needs framing before work starts. Turns the input into a structured brief (Context · Desired outcome · Goal · Owner · Next step · Decision needed). This is the AIOS's front door; run most things through it first. Trigger on "/structure", "frame this", "what's the actual ask here", "structure this", or any vague task that lacks a defined outcome.