/setup
First-run guided setup for a fresh gAIOS clone. Interviews the user (identity, role, priorities, voice, connections, team, pain, guardrails) and fills the templates — CLAUDE.md, context/, references/voice.md, connections.md — then introduces the WAT / wiki / workflows /
$ npx -y skills add alirezarezvani/gaios --skill setup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/setup
Context preview
The summary Claude sees to decide when to auto-load this skill.
First-run guided setup for a fresh gAIOS clone. Interviews the user (identity, role, priorities, voice, connections, team, pain, guardrails) and fills the templates — CLAUDE.md, context/, references/voice.md, connections.md — then introduces the WAT / wiki / workflows /
SKILL.md
setup.SKILL.mdname: setup
description: First-run guided setup for a fresh gAIOS clone. Interviews the user (identity, role, priorities, voice, connections, team, pain, guardrails) and fills the templates — CLAUDE.md, context/, references/voice.md, connections.md — then introduces the WAT / wiki / workflows / experiments features. Trigger on "/setup", "set me up", "get started", "onboard me", or a fresh clone where CLAUDE.md still has {{placeholders}}.Setup — make this AIOS yours
A guided interview that turns the blueprint into a personalized AIOS. Read `aios-intake.md` first; if it's filled, confirm and scaffold; if not, run the interview conversationally, **one question at a time, with a recommended answer** so the user can confirm/correct.
Interview (capture each answer into `aios-intake.md` as you go)
1. **Who are you** — role, company, what you own. (→ `context/about-me.md`, `CLAUDE.md` header) 2. **Voice samples** — ask the user to **paste 1–2 real, unedited** things they've written. *Refuse typed-fresh prose* (it contaminates the sample). (→ `references/voice.md`) 3. **90-day priorities** — dated, concrete. Push back on vague. (→ `context/priorities.md`) 4. **Business** — what it sells, to whom, the model. (→ `context/about-business.md`, Knowledge base) 5. **The stack** — where revenue/customers/comms/docs/tasks live. (→ `connections.md`) 6. **The team** — roster + who can absorb delegated work. (→ `context/about-team.md`) 7. **The constraint / pain** — what eats the week; what to hand off first. 8. **Guardrails** — the hard rules + sensitive-data line + any compliance regime (GDPR/HIPAA/SOC2/...); what may be sent/acted-on vs only drafted. (→ `CLAUDE.md` Guardrails)
Scaffold (after the interview)
Fill every `{{placeholder}}` in `CLAUDE.md` (name, persona, knowledge base, voice summary, connections, **guardrails — customize rule #1 and #8 to the domain**). Write `context/*`, `references/voice.md`, and the `connections.md` rows. Back up any existing versions to `archives/` first.
Introduce the engine (one screen)
Point the user at: `/structure` (frame fuzzy asks) · `/triage` · `/daily` · `/weekly` (Cadence) · `/wiki` (second brain: `raw/` → `wiki/`) · `/graph` · `/graph-query` · `/graph-ingest` (knowledge graph) · `/workflow` (dynamic workflows) · `/experiment` (autoresearch loop) · `/audit` + `/level-up` (weekly). Then suggest the first prompt: *"what should I focus on this week?"*
Optional: knowledge graph (graphify)
Offer to set up the knowledge graph so the user can *see* and query their code + second brain: run `python tools/graphify_setup.py install` (installs graphify and wires the Claude Code & Codex skills). Then `/graph` builds it. Skippable and additive — graphs **code + the committed `wiki/` only**, never `raw/`.
Rules
- Voice paste cannot be skipped or typed fresh.
- One-shot scaffold after the interview; the user iterates by editing `aios-intake.md` and re-running.
- Customize the Guardrails block to the user's domain — don't ship the generic defaults unchanged for a regulated business.
Read more
name: setup
description: First-run guided setup for a fresh gAIOS clone. Interviews the user (identity, role, priorities, voice, connections, team, pain, guardrails) and fills the templates — CLAUDE.md, context/, references/voice.md, connections.md — then introduces the WAT / wiki / workflows / experiments features. Trigger on "/setup", "set me up", "get started", "onboard me", or a fresh clone where CLAUDE.md still has {{placeholders}}.Setup — make this AIOS yours
A guided interview that turns the blueprint into a personalized AIOS. Read `aios-intake.md` first; if it's filled, confirm and scaffold; if not, run the interview conversationally, **one question at a time, with a recommended answer** so the user can confirm/correct.
Interview (capture each answer into `aios-intake.md` as you go)
1. **Who are you** — role, company, what you own. (→ `context/about-me.md`, `CLAUDE.md` header) 2. **Voice samples** — ask the user to **paste 1–2 real, unedited** things they've written. *Refuse typed-fresh prose* (it contaminates the sample). (→ `references/voice.md`) 3. **90-day priorities** — dated, concrete. Push back on vague. (→ `context/priorities.md`) 4. **Business** — what it sells, to whom, the model. (→ `context/about-business.md`, Knowledge base) 5. **The stack** — where revenue/customers/comms/docs/tasks live. (→ `connections.md`) 6. **The team** — roster + who can absorb delegated work. (→ `context/about-team.md`) 7. **The constraint / pain** — what eats the week; what to hand off first. 8. **Guardrails** — the hard rules + sensitive-data line + any compliance regime (GDPR/HIPAA/SOC2/...); what may be sent/acted-on vs only drafted. (→ `CLAUDE.md` Guardrails)
Scaffold (after the interview)
Fill every `{{placeholder}}` in `CLAUDE.md` (name, persona, knowledge base, voice summary, connections, **guardrails — customize rule #1 and #8 to the domain**). Write `context/*`, `references/voice.md`, and the `connections.md` rows. Back up any existing versions to `archives/` first.
Introduce the engine (one screen)
Point the user at: `/structure` (frame fuzzy asks) · `/triage` · `/daily` · `/weekly` (Cadence) · `/wiki` (second brain: `raw/` → `wiki/`) · `/graph` · `/graph-query` · `/graph-ingest` (knowledge graph) · `/workflow` (dynamic workflows) · `/experiment` (autoresearch loop) · `/audit` + `/level-up` (weekly). Then suggest the first prompt: *"what should I focus on this week?"*
Optional: knowledge graph (graphify)
Offer to set up the knowledge graph so the user can *see* and query their code + second brain: run `python tools/graphify_setup.py install` (installs graphify and wires the Claude Code & Codex skills). Then `/graph` builds it. Skippable and additive — graphs **code + the committed `wiki/` only**, never `raw/`.
Rules
- Voice paste cannot be skipped or typed fresh.
- One-shot scaffold after the interview; the user iterates by editing `aios-intake.md` and re-running.
- Customize the Guardrails block to the user's domain — don't ship the generic defaults unchanged for a regulated business.
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.
Other skills on gaios.
- /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 AIOS". Produces a Four-Cs scoreboard with top-3 fixes ranked by leverage.
Open skill - /daily
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
Open skill - /decide
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",
Open skill - /exec-cockpit
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
Open skill - /experiment
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",
Open skill - /graph-ingest
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 brain. Fetches the source into the git-ignored capture inbox, admits it to the committed wiki through the admission policy,
Open skill