Walks the user through expanding their morning brief with team comms and task sources. Trigger when the user says "/onboard-daily-brief", "set up my daily brief", "expand my brief", or "add Slack to my brief".
Pulls team-comms data from Slack, Discord, Teams, or Telegram for the morning brief. Use when the morning-brief skill invokes it to populate the Team comms section.
Recommends MCP connectors to add to Claude Cowork based on the user's business and empty tool buckets. Trigger when the user says "/browse-connectors", "what connectors do I need", "recommend MCPs", or "what should I plug into Cowork".
Recommends community plugins and skills for Claude Cowork based on the user's business and goals. Trigger when the user says "/browse-skills", "what skills should I install", "what plugins do I need", or "what else can Cowork do".
Finds the single highest-leverage next move for the user's Cowork AI OS setup. Trigger when the user says "/level-up", "what should I improve next", "what's the next step", "what is missing from my setup", or "where should I focus this week".
Generates a daily morning brief from the user's calendar, inbox, and priorities. Trigger when the user says "morning brief", "what is on today", "daily brief", or "/morning-brief".
Walks the user through setting up automated file organization with a safe plan-then-approve flow. Trigger when the user says "/onboard-file-organization", "organize my files", "set up file cleanup", or "tidy my downloads automatically".
| name | onboard-daily-brief |
| description | Walks the user through expanding their morning brief with team comms and task sources. Trigger when the user says "/onboard-daily-brief", "set up my daily brief", "expand my brief", or "add Slack to my brief". |
You are walking the user through Project 02 — Daily Brief expansion. The user already has Project 01 (Core Setup) installed with a working /morning-brief skill that already:
brief-preferences.mdabout-me/memory.mdProject 02 extends that — it doesn't rebuild it. It adds:
brief-source-comms)today.md markdown task source (no third-party task connector required)/tune-up daily-briefClaude drafts. You approve. You send.
This skill never sends an email. Never posts to any messaging platform (Slack, Discord, Telegram, Teams, or any other). Never creates calendar events. Never modifies tasks. Read-only on Gmail (existing P01 behavior continues), Calendar, and all messaging platforms. Write-only to outputs/daily-brief/, projects/daily-brief/, and Gmail Drafts.
If the user asks to bypass this rule, refuse.
Read _aibos/state-daily-brief.md from the user's workspace. Three cases:
templates/state-daily-brief.template.md. Run Phase 0 (Welcome).current_phase: <N> → User resuming. Load phases/0N-*.md and run that phase.daily_brief_complete: true → User finished. Confirm completion. Offer calibration check or weekly tune-up.Before Phase 0, confirm _aibos/state.md exists and shows install_complete: true. If not, STOP and tell the user to run /onboard first.
Confirm projects/daily-brief/brief-preferences.md already exists (P01 Phase 6 builds it). If missing, the user skipped P01 Phase 6 — send them back.
Confirm the morning-brief skill is at v0.6.0+ in their plugin install. The presence of skills/brief-source-comms/SKILL.md in their plugin folder confirms v0.6.0+. If missing on Mac, instruct them to download the latest cowork-ai-os.zip from the release page and re-upload via Settings → Customize → Browse plugins. On Windows, instruct them to run /plugin update cowork-ai-os.
Each phase script in phases/0N-*.md is the source of truth for that phase. Follow it exactly. Do not improvise. Do not skip questions. Do not advance until verification passes.
At Phase 1 (extending the prefs file), offer the sample additions as a filled-in example. Read from samples/sarahs-prefs-additions.md.
If user types pause onboarding: save state. Tell them: "Phase X complete. You're [N]% through. Resume with /onboard-daily-brief."
If user types continue onboarding or invokes the skill again: read state, jump to current_phase.
After verification passes for each phase:
current_phase: N+1, append timestamped log entrycontinue onboarding when ready."After Phase 6 verification passes:
daily_brief_complete: truecompleted_at: <ISO timestamp>/tune-up daily-brief after 7 days."The existing morning-brief skill (v0.6.0) reads projects/daily-brief/brief-preferences.md and conditionally adds sections based on what's there:
1. Read brief-preferences.md (existing P01 sections + any Q4-Q8 added by P02)
2. Pull Calendar (existing P01 logic)
3. Pull Inbox (existing P01 logic)
4. IF Q4 (Team comms rules) present for any platform
→ invoke brief-source-comms helper, append section
5. IF Q5 (Tasks rules) present AND projects/daily-brief/today.md exists
→ read today.md, surface Today section unchecked items
6. Quick Wins (existing P01 logic)
7. Drafts (existing P01 logic, refined by Q8 if present)
8. Save brief, log to about-me/memory.md (existing P01 behavior)
Each phase activates one of these conditional blocks by appending a new section to the existing brief-preferences.md. The student never edits morning-brief/SKILL.md directly. The team-comms helper skill ships with the plugin and supports whichever platform(s) the student has connected. Drafts get tighter just by Q8 being present.
| Phase | Title | Activates | Time | % at completion |
|---|---|---|---|---|
| 0 | Welcome + sample-first | Verify P01 + plugin v0.6.0 | 5 min | 0% |
| 1 | Extend Your Prefs (Q4–Q8) | — (configures only) | 25 min | 17% |
| 2 | Verify the Baseline | Existing brief reads new prefs | 15 min | 33% |
| 3 | Add Team Comms | brief-source-comms | 15 min | 50% |
| 4 | Add Tasks (today.md) | morning-brief Tasks section | 15 min | 67% |
| 5 | Tighten Draft Rules | Q8 sharper than P01 default | 15 min | 83% |
| 6 | Schedule + Calibrate | Cowork scheduled task | 25 min | 100% |
Total: ~115 min. Lesson docs add 10 min reading per concept, optional.
When walking the user through phases:
skills/morning-brief/SKILL.md appendix for the canonical anti-AI kill list. Don't duplicate.samples/sarahs-prefs-additions.md.about-me/business-brain.md. They edit from there.Never let a vague answer pass. The brief is only as sharp as its preferences.
Companion teaching curriculum lives in markdown-source/:
daily-brief-quick-start.md — outcome + roadmaplesson-01-*.md through lesson-06-*.md — concept + examplesdaily-brief-deck.md — concept slidesPhase scripts here = runtime walkthrough. Lesson docs = read-it-yourself companion. Same content, different surface.