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 for a weekly operating review (Friday wrap or Monday plan) — review progress against the 90-day priorities, surface stalled open loops, and set next week's focus. This is the PERSONAL operating review; distinct from /audit (checks the kit's connections/freshness) and
$ npx -y skills add alirezarezvani/gaios --skill weekly --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/weeklyContext preview
The summary Claude sees to decide when to auto-load this skill.
Use for a weekly operating review (Friday wrap or Monday plan) — review progress against the 90-day priorities, surface stalled open loops, and set next week's focus. This is the PERSONAL operating review; distinct from /audit (checks the kit's connections/freshness) and
name: weekly description: Use for a weekly operating review (Friday wrap or Monday plan) — review progress against the 90-day priorities, surface stalled open loops, and set next week's focus. This is the PERSONAL operating review; distinct from /audit (checks the kit's connections/freshness) and /level-up (finds one automation to build). Trigger on "/weekly", "weekly review", "weekly planning", "how did this week go", "plan my week".
The Cadence layer at week resolution: close the loop on the week, surface what stalled, and aim the next week at the priorities that matter.
> Not to be confused with: **/audit** (is the *kit* healthy — connections, freshness) or > **/level-up** (build one new automation). This skill reviews *your week and priorities*.
## Weekly review — week of <date> **Moved** — progress on each 90-day priority this week (concrete, not vibes). **Stalled / at risk** — priorities or loops that didn't move + why + the unblock. **Closed loops** — commitments resolved this week. **Carrying forward** — open loops into next week, with owners. **Next week's focus** — 3–5 outcomes for the coming week, tied to priorities. **Surfaced for /level-up** — any task done manually 3+ times this week (candidate to automate).
1. **Read:** `context/priorities.md`, `decisions/log.md` (this week's entries), `projects/`, and open loops (`tools/open_loops.py` if present). 2. **Assess each priority:** moved / stalled / at-risk, with evidence (a shipped thing, a decision, a metric) — not assertion. 3. **Diagnose stalls:** for each, name the single blocker and the unblocking action/owner. 4. **Plan next week:** propose 3–5 outcomes mapped to the 90-day priorities; keep it realistic. 5. **Spot recurring manual work** → list it under "Surfaced for /level-up". 6. **Offer to log:** append a dated summary entry to `decisions/log.md` (allowed without approval).
**L2 — drafts the review and next-week plan; the human 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…
Use when the user faces a real decision with stakes and wants it framed cleanly — options, ranked criteria, a recommendation, the falsifier, and reversibility…
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…