Agent skill · operations · anthropics

start

Initialize the productivity system and open the dashboard. Use when setting up the plugin for the first time, bootstrapping working memory from your existing task list, or decoding the shorthand (nicknames, acronyms, project codenames) you use in your todos.

Why this skill is useful

Adds a comprehensive setup workflow for initializing a productivity system, including task decoding and memory bootstrapping that the AI wouldn't reliably generate on its own.

What it needs

About 3k tokens when loaded. Last updated 2026-08-07. 23,345 stars on the source repository.

What this skill does

Start Command If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Initialize the task and memory systems, then open the unified dashboard. Instructions 1. Check What Exists Check the working directory for: TASKS.md — task list CLAUDE.md — working memory memory/ — deep memory directory dashboard.html — the visual UI 2. Create What's Missing If TASKS.md doesn't exist: Create it with the standard template (see task-management skill). Place it in the current working directory. If dashboard.html doesn't exist: Copy it from ${CLAUDEPLUGINROOT}/skills/dashboard.html to the current working directory. If CLAUDE.md and memory/ don't exist: This is a fresh setup — after opening the dashboard, begin the memory bootstrap workflow (see below). Place these in the current working directory. 3. Open the Dashboard Do NOT use open or xdg-open — in Cowork, the agent runs in a VM and shell open commands won't reach the user's browser. Instead, tell the user: "Dashboard is ready at dashboard.html. Open it from your file browser to get started." 4. Orient the User If everything was already initialized: If memory hasn't been bootstrapped yet, continue to step 5. 5. Bootstrap Memory (First Run Only) Only do this if CLAUDE.md and memory/ don't exist yet. The best source of workplace language is the user's actual task list. Real tasks = real shorthand. Ask the user: Once you have access to the task list: For each task item, analyze it for potential shorthand: Names that might be nicknames Acronyms or abbreviations Project references or codenames Internal terms or jargon For each item, decode it interactively: Continue through each task, asking only about terms you haven't already decoded. 6. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills anthropics/start--0e653b

View the source on GitHub

Browse the @skills marketplace