/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
$ npx -y skills add alirezarezvani/gaios --skill daily --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
/daily
Context preview
The summary Claude sees to decide when to auto-load this skill.
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
SKILL.md
daily.SKILL.mdname: daily
description: 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 brief", "what should I focus on today", "morning brief", "standup".
Daily Brief
The Cadence layer: turn scattered priorities, commitments, and calendar into one focused screen so the day starts pointed at leverage — not at the inbox.
When to run
- Start of day, or any time the user asks what to focus on now.
- After a `/triage` dump, to fold new items into the day.
The output (always this shape)
## Daily brief — <date>
**Today's 3** — the highest-leverage moves (tied to priorities). Each: action + why it matters.
1. … 2. … 3. …
**Open loops needing a nudge** — commitments owed by/to you, with next step.
- <loop> → <next step> (waiting on <who>)
**Slipping** — priorities/projects at risk, with the one action that unblocks.
**On the calendar** — meetings that need prep → offer `/prep`.
**Parked** — explicitly not today (so it's off the mind).
Process
1. **Gather (read, don't guess):** `context/priorities.md` (the 90-day outcomes), `decisions/log.md` (recent calls), `projects/` (active workstreams), and open commitments — from `tools/open_loops.py` if present, else from notes/projects. 2. **Pull live where connected:** if a calendar/task/CRM MCP is wired (`connections.md`), pull today's meetings and due items. If nothing is connected, work from files and say so. 3. **Rank to 3.** Map candidates to priorities; pick the 3 with the most leverage (find-the-constraint). Everything else is loops/parked. 4. **Flag slippage.** Compare priorities to recent activity; name what's at risk + the single unblocking action. 5. **Offer next moves:** `/prep` for each meeting, `/structure` for any fuzzy item, `/draft` for comms owed.
Autonomy
**L2 — drafts the brief; the human acts.** Never auto-sends anything it surfaces.
Guardrails (from CLAUDE.md)
- Pull confidential figures live; never persist them to the repo.
- Route owners to the team by default; don't pool everything on the user.
- Any external comm it proposes is a **draft**, in `references/voice.md` register.
Read more
name: daily description: 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 brief", "what should I focus on today", "morning brief", "standup".
Daily Brief
The Cadence layer: turn scattered priorities, commitments, and calendar into one focused screen so the day starts pointed at leverage — not at the inbox.
When to run
- Start of day, or any time the user asks what to focus on now.
- After a `/triage` dump, to fold new items into the day.
The output (always this shape)
## Daily brief — <date> **Today's 3** — the highest-leverage moves (tied to priorities). Each: action + why it matters. 1. … 2. … 3. … **Open loops needing a nudge** — commitments owed by/to you, with next step. - <loop> → <next step> (waiting on <who>) **Slipping** — priorities/projects at risk, with the one action that unblocks. **On the calendar** — meetings that need prep → offer `/prep`. **Parked** — explicitly not today (so it's off the mind).
Process
1. **Gather (read, don't guess):** `context/priorities.md` (the 90-day outcomes), `decisions/log.md` (recent calls), `projects/` (active workstreams), and open commitments — from `tools/open_loops.py` if present, else from notes/projects. 2. **Pull live where connected:** if a calendar/task/CRM MCP is wired (`connections.md`), pull today's meetings and due items. If nothing is connected, work from files and say so. 3. **Rank to 3.** Map candidates to priorities; pick the 3 with the most leverage (find-the-constraint). Everything else is loops/parked. 4. **Flag slippage.** Compare priorities to recent activity; name what's at risk + the single unblocking action. 5. **Offer next moves:** `/prep` for each meeting, `/structure` for any fuzzy item, `/draft` for comms owed.
Autonomy
**L2 — drafts the brief; the human acts.** Never auto-sends anything it surfaces.
Guardrails (from CLAUDE.md)
- Pull confidential figures live; never persist them to the repo.
- Route owners to the team by default; don't pool everything on the user.
- Any external comm it proposes is a **draft**, in `references/voice.md` register.
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 - /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 - /graph-query
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 what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with
Open skill