audit
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…
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
$ npx -y skills add alirezarezvani/gaios --skill exec-cockpit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/exec-cockpitContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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.
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.
Clone it, run /setup, and it becomes yours in Claude Code or Codex — a second brain + Chief of Staff that holds your context, structures your work, drafts in your voice, and runs reliable workflows.
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…
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…
Use when the user faces a real decision with stakes and wants it framed cleanly — options, ranked criteria, a recommendation, the falsifier, and reversibility…
Use to run an autoresearch-style experiment loop — improve a measurable artifact by trying changes, measuring against one objective metric, keeping if better…
Use 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…
Use 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…