00-init — Claude Code skill: what it does, how to install
00-init controls AIDD telemetry in projects: turns resource tracking on or off with consent, configures identity, or purges recorded metrics.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-telemetry@aidd-frameworkWhat 00-init does
This skill coordinates AIDD consumption measurements inside a workspace. It handles four specific routes: opting into project telemetry, showing or assigning a contributor name, turning metrics collection off while keeping past entries, and wiping local data.
Before executing any operation, the skill runs aidd telemetry on --help to probe the environment. If the aidd binary is missing or lacks the --anonymous option, it halts and reports that @ai-driven-dev/cli must be installed or updated.
All state modifications rely strictly on aidd telemetry rather than editing .aidd/config.json or git config files directly. The workflow never infers usernames from git logs or active sessions, requiring explicit input and approval before running mutating actions.
What it helps with
- enable AIDD resource tracking after explicit user consent
- assign or remove a contributor name on local measurements
- halt telemetry collection without deleting past records
- preview and remove all measurement logs from the machine
Example prompts for the agent
- Turn on AIDD measurement for this project
- Set my author name for AIDD telemetry
- Stop telemetry tracking and purge measured data
How to install 00-init
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-telemetry@aidd-frameworkThis installs the whole aidd-telemetry plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-init -a claude-code3Manually: put the files in place
~/.claude/skills/00-init/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/00-init/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-init -a codex2Manually: put the files in place
.agents/skills/00-init/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-init -a cursor2Manually: put the files in place
.cursor/skills/00-init/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-telemetry/skills/00-init2Manually: put the files in place
.github/skills/00-init/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-init -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-telemetry/skills/00-initManually: put the files in place
.devin/skills/00-init/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 00-init -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 00-init
How to install 00-init in Claude Code?
Run /plugin marketplace add ai-driven-dev/framework in Claude Code, then run /plugin install aidd-telemetry@aidd-framework.
What does the 00-init skill do?
It manages project telemetry state for AIDD, handling opt-in consent, author identity assignment, deactivation, and metric data cleanup.
What prerequisite is required to run 00-init?
The machine needs @ai-driven-dev/cli installed so that aidd telemetry on --help succeeds and contains the --anonymous flag.
Source text
SKILL.md · MIT
---
name: 00-init
description: Turn AIDD measurement on for a project after explicit consent, stop it, choose to be named on your own measurement, or delete what was measured. Use when the user wants to start or stop measuring what their work consumes, add or remove their name, or forget measured data. Not for answering what a period consumed.
argument-hint: opt in | my name | opt out | delete
---
# Init
```mermaid
flowchart TD
request([request]) --> probe{"aidd answers telemetry?"}
probe -->|"no"| absent([say it is missing, change nothing])
probe -->|"yes"| route{which case}
route -->|"start measuring"| start --> done([reported as it ran])
route -->|"name me, or stop naming me"| identity --> done
route -->|"stop measuring"| stop --> done
route -->|"delete what was measured"| forget
forget -->|"person confirms the preview"| done
forget -->|"person declines"| kept([nothing removed])
```
## Actions
Run the flow above. Read only the action file the case needs.
| Action | Does |
| --- | --- |
| start | ask for consent, then turn measurement on for this project |
| identity | set, show or remove the name on the person's own measurement |
| stop | turn measurement off for this project, keeping what was measured |
| forget | preview, then on confirmation delete everything measured on this machine |
## Transversal rules
- Probe first. Run `aidd telemetry on --help` before any action. When `aidd` is not found, the command exits non-zero, or its help does not list `--anonymous`, stop and say plainly that `aidd` is missing or too old to measure, name `@ai-driven-dev/cli` as what to install or update, and state that nothing was changed. Never go on, and never answer as if it had worked.
- Every change goes through `aidd telemetry`. Never edit git config, `.aidd/config.json` or any file by hand.
- Never run a command that changes anything before the person has said yes to what it does. A silence, a previous yes to another case, or a standing instruction is not a yes.
- Report what each command printed, including every warning, and never claim a result the output did not show.
- Never choose, derive or guess a name for the person: not from git, from the machine, nor from the session. Only the identifier the person types is used. `aidd telemetry on` run in a terminal offers the git name itself.
- When a command exits non-zero, show its message and stop. Do not retry with other flags.
© AI-Driven Dev · MIT · ai-driven-dev/framework