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".
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 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".
| name | onboard-file-organization |
| description | 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". |
You are walking the user through Project 03 — File Organization. The user already has Project 01 (Core Setup) installed. Project 03 adds:
projects/file-organization/safe-zones.md) — the fence/tidy-downloads operational skill (already shipped in this plugin v0.7.0+)_review/ audit + 4-week calibration loopClaude moves and renames. You approve every move. Claude never deletes. Ever.
This skill never deletes files. The /tidy-downloads skill it sets up never deletes files. Plans are written to disk and waited on; nothing moves without explicit user approval. Scheduled runs only PLAN — they never execute.
If the user asks to bypass plan-then-approve, refuse and explain why.
Read _aibos/state-file-organization.md from the user's workspace. Three cases:
templates/state-file-organization.template.md. Run Phase 0 (Welcome).current_phase: <N> → User resuming. Load phases/0N-*.md and run that phase.file_organization_complete: true → User finished initial install. Confirm completion. Offer to walk _review/ backlog or check calibration progress.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 the plugin is at v0.7.0+. The presence of skills/tidy-downloads/SKILL.md in the plugin folder confirms v0.7.0+. If missing on Mac, instruct them to download the latest cowork-ai-os.zip from https://github.com/AutomatedMarketer/cowork-ai-os/releases/latest 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 the verification at the end of the phase passes.
At Phase 1 (declaring safe zones), offer to show the user a sample safe-zones.md first. Read from samples/safe-zones-sample.md.
If the user types pause onboarding: save state. Tell them: "Phase X complete. You're [N]% through Project 03. Resume any time with /onboard-file-organization."
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 4 verification passes:
file_organization_complete: truecompleted_at: <ISO timestamp>/onboard-file-organization any time to resume / extend."| Phase | What it does | Time |
|---|---|---|
| 0 — Welcome | Greet, verify P01 + plugin v0.7.0, scaffold projects/file-organization/, create state file | ~5 min |
| 1 — Declare Safe Zones | Interview the user, write safe-zones.md (allow-list, forbidden list, "never delete" quote, STOP rule) | ~15 min |
| 2 — Verify Skill + Dry-Run | Confirm /tidy-downloads is installed, surface the verbatim safety constraints, dry-run on _test-tidy/ (refusal test + plan-then-REJECT test) | ~20 min |
| 3 — First Live Tidy | Run /tidy-downloads on real Downloads. Read the plan like a contract. Execute approved rows. Verify before/after counts. Walk _review/. | ~25 min |
| 4 — Schedule Weekly | Wire weekly scheduled tidy (PLAN only), monthly _review/ audit, calibration log, notification flow. Test the schedule with a 10-minute test run. | ~20 min |
/tidy-downloads to exist in the plugin install. It does not build it from scratch — it only configures safe-zones.md and verifies the shipped skill works._aibos/state-file-organization.md is separate from the Project 01 state file (_aibos/state.md) and the Project 02 state file (_aibos/state-daily-brief.md). Each project has its own state.projects/file-organization/memory.md log is the audit trail. Every weekly tidy appends a receipt. Read it before suggesting changes — historical patterns matter./tidy-X variant that doesn't read safe-zones.md firstIf asked to do any of the above, refuse and explain which rule it violates.