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…
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",
$ npx -y skills add alirezarezvani/gaios --skill decide --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/decideContext preview
The summary Claude sees to decide when to auto-load this skill.
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",
name: decide 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".
Turn a fork in the road into a clear, logged decision — reasoning visible, and the way you'd know you were wrong stated up front.
## Decision — <the question> · <date> **Context** — why this is on the table now (2–3 lines). **Options** — each with its main upside + main cost/risk (include "do nothing"). **Criteria** — what actually matters here, ranked. **Recommendation** — the call + the why, in one paragraph. **Falsifier** — what we'd later see that would prove this was the wrong call (Verification Gate). **Reversibility** — one-way or two-way door? (two-way → decide fast and move). **Owner / next step** — who does what, by when.
1. **Frame the real question.** Strip to the actual choice (`/structure` if fuzzy). Name what is *not* being decided. 2. **Lay out options honestly** — including "do nothing." Each gets a real upside and a real cost. No strawmen. 3. **Make criteria explicit and ranked** — most decisions go wrong because the criteria were never named. 4. **Recommend.** Take a position with the reasoning. State the **falsifier** and the **reversibility** (two-way doors don't deserve one-way-door deliberation). 5. **Verify the inputs (Verification Gate).** Any fact or number the decision rests on → trace to source; flag unknowns as risks, don't paper over them. 6. **Log it.** On the user's confirmation, append the brief to `decisions/log.md` (dated) — the standing record (per "How you work with me").
**L1–L2** — frames and recommends; the human makes the call. Logs it once the user confirms.
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…
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…
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…