/triage
Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a
$ npx -y skills add alirezarezvani/gaios --skill triage --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
/triage
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a
SKILL.md
triage.SKILL.mdname: triage
description: Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a full /structure brief or a /decide call. Trigger on "/triage", "triage this", "process my inbox", "sort these asks", "clear my backlog", "what do I do with all this".
Triage
Batch intake for the Chief of Staff: turn a chaotic pile into a sorted, owned, prioritized list — the front-door `/structure` does for *one* fuzzy input, `/triage` does for *many*.
When to run
- An inbox / backlog / message pile needs to become action.
- After a meeting, to process a batch of action items at once.
- Feeding `/daily` — fold the triaged items into today.
The output (always this shape)
## Triage — <date> (<N> items)
| # | Item (1 line) | Type | Owner | Next step | Priority | Route |
|---|---------------|------|-------|-----------|----------|-------|
| 1 | … | ask/FYI/decision/task | <who> | <action> | P1/P2/P3 | /structure · /decide · /draft · done |
**Needs your decision** — the short list only the user can resolve (with the framed choice).
**Delegated** — items routed to the team (with owner + next step).
**Drop / FYI** — no action needed (so they're off the list).
Process
1. **Split the batch into discrete items.** One row per real ask; merge duplicates. 2. **Classify each:** ask · FYI · decision · task. Be ruthless — most "FYIs" are drops. 3. **Assign owner + next step + priority.** Default owner to the right teammate (don't pool on the user). Priority by leverage/urgency. 4. **Route, don't solve inline:** mark complex items `/structure` (needs framing), `/decide` (needs a call), `/draft` (needs a reply). Simple ones get a one-line next step. 5. **Surface the decision shortlist.** Pull every `decision`-type item into "Needs your decision" with the choice framed for a fast yes/no. 6. **Offer next moves:** run `/structure` on the flagged items, `/draft` the replies (internal may send; external = draft), and/or feed the result into `/daily`.
Autonomy
**L2 — sorts and routes; the human decides and sends.** Triage never auto-replies.
Guardrails (from CLAUDE.md)
- **Eliminate first** (3Ms): if nobody would notice an item disappearing, drop it.
- No confidential data persisted to the repo; reference live sources.
- External replies are **drafts** in `references/voice.md` register; internal-to-team may send.
Read more
name: triage description: Use when the user dumps a batch of inputs at once — a pile of emails, a backlog of Slack/Teams messages, a list of asks, meeting action items, a notes brain-dump — and needs it sorted into action. Classifies each item, assigns owner + next step + priority, and flags which need a full /structure brief or a /decide call. Trigger on "/triage", "triage this", "process my inbox", "sort these asks", "clear my backlog", "what do I do with all this".
Triage
Batch intake for the Chief of Staff: turn a chaotic pile into a sorted, owned, prioritized list — the front-door `/structure` does for *one* fuzzy input, `/triage` does for *many*.
When to run
- An inbox / backlog / message pile needs to become action.
- After a meeting, to process a batch of action items at once.
- Feeding `/daily` — fold the triaged items into today.
The output (always this shape)
## Triage — <date> (<N> items) | # | Item (1 line) | Type | Owner | Next step | Priority | Route | |---|---------------|------|-------|-----------|----------|-------| | 1 | … | ask/FYI/decision/task | <who> | <action> | P1/P2/P3 | /structure · /decide · /draft · done | **Needs your decision** — the short list only the user can resolve (with the framed choice). **Delegated** — items routed to the team (with owner + next step). **Drop / FYI** — no action needed (so they're off the list).
Process
1. **Split the batch into discrete items.** One row per real ask; merge duplicates. 2. **Classify each:** ask · FYI · decision · task. Be ruthless — most "FYIs" are drops. 3. **Assign owner + next step + priority.** Default owner to the right teammate (don't pool on the user). Priority by leverage/urgency. 4. **Route, don't solve inline:** mark complex items `/structure` (needs framing), `/decide` (needs a call), `/draft` (needs a reply). Simple ones get a one-line next step. 5. **Surface the decision shortlist.** Pull every `decision`-type item into "Needs your decision" with the choice framed for a fast yes/no. 6. **Offer next moves:** run `/structure` on the flagged items, `/draft` the replies (internal may send; external = draft), and/or feed the result into `/daily`.
Autonomy
**L2 — sorts and routes; the human decides and sends.** Triage never auto-replies.
Guardrails (from CLAUDE.md)
- **Eliminate first** (3Ms): if nobody would notice an item disappearing, drop it.
- No confidential data persisted to the repo; reference live sources.
- External replies are **drafts** in `references/voice.md` register; internal-to-team may send.
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