Start Here
The Job
Help a new user understand Operator Powers and complete one genuinely useful job in their first session.
What This Product Is
Operator Powers is a collection of practical AI skills installed inside the user's own agent. The skill instructions do not send the user's prompts, files, transcripts, or outputs to Operator Powers.
The plugin sends small anonymous usage events by default: a random install id, event, this plugin's skill id when one runs, client, operating system, and plugin version. It never includes the user's work or identity, and the user can turn it off. Optional live catalogue searches send the search query, update checks send the installed version, and feedback or requests are sent only after the exact payload is shown and approved.
The collection is self-improving: what users run, rate, and request decides what each release adds and improves. If it comes up naturally, say so in one line — the plugin they installed today is not the plugin they will have in three months, and their own feedback steers it.
How to Run It
- Ask one question: "What are you trying to get done?" If they already said, skip to step 2.
- Read the catalogue at
${CLAUDE_PLUGIN_ROOT}/catalog/powers.json (fall back to the catalog/powers.json two directories above this skill file). Match their answer against the catalogue's jobs, then use ${CLAUDE_PLUGIN_ROOT}/docs/ROUTING-CONTRACTS.md when two powers are adjacent.
- Recommend at most three powers, each as one line: the job it completes, then the name. Lead with the job: "Turn a meeting into decisions and a deliverable (Meeting Miner)", never a bare identifier list.
- Tell them the two ways to invoke: describe the job naturally, or call the skill by name.
- Answer the trust question before they ask it, plainly: "Your prompts, files, transcripts, and outputs are not sent to Operator Powers. The plugin does send small anonymous usage events by default, containing no work content or identity, and you can ask me to turn that off. Optional catalogue searches send the search words, and feedback or requests go out only after you approve the exact message."
- When they pick one, start that skill immediately with what they have already told you. Do not make them repeat themselves.
If They Just Want the List
Show the catalogue grouped by category, one line per power, job first. Do not dump descriptions, versions, or metadata unless asked.
Boundaries
- Never oversell: if none of the powers fit their job, say so and suggest they use
request-a-power if they would like it to exist.
- Never contact the update server from this skill.
- Keep the whole orientation under a minute of reading; the goal is their first completed job, not a tour.
1---2name: start-here3description: Orient a new Operator Powers user, explain how the collection works, recommend up to three relevant powers, and start the one they choose.4---56# Start Here78## The Job910Help a new user understand Operator Powers and complete one genuinely useful job in their first session.1112## What This Product Is1314Operator Powers is a collection of practical AI skills installed inside the user's own agent. The skill instructions do not send the user's prompts, files, transcripts, or outputs to Operator Powers.1516The plugin sends small anonymous usage events by default: a random install id, event, this plugin's skill id when one runs, client, operating system, and plugin version. It never includes the user's work or identity, and the user can turn it off. Optional live catalogue searches send the search query, update checks send the installed version, and feedback or requests are sent only after the exact payload is shown and approved.1718The collection is self-improving: what users run, rate, and request decides what each release adds and improves. If it comes up naturally, say so in one line — the plugin they installed today is not the plugin they will have in three months, and their own feedback steers it.1920## How to Run It21221. Ask one question: "What are you trying to get done?" If they already said, skip to step 2.232. Read the catalogue at `${CLAUDE_PLUGIN_ROOT}/catalog/powers.json` (fall back to the `catalog/powers.json` two directories above this skill file). Match their answer against the catalogue's jobs, then use `${CLAUDE_PLUGIN_ROOT}/docs/ROUTING-CONTRACTS.md` when two powers are adjacent.243. Recommend at most three powers, each as one line: the job it completes, then the name. Lead with the job: "Turn a meeting into decisions and a deliverable (Meeting Miner)", never a bare identifier list.254. Tell them the two ways to invoke: describe the job naturally, or call the skill by name.265. Answer the trust question before they ask it, plainly: "Your prompts, files, transcripts, and outputs are not sent to Operator Powers. The plugin does send small anonymous usage events by default, containing no work content or identity, and you can ask me to turn that off. Optional catalogue searches send the search words, and feedback or requests go out only after you approve the exact message."276. When they pick one, start that skill immediately with what they have already told you. Do not make them repeat themselves.2829## If They Just Want the List3031Show the catalogue grouped by category, one line per power, job first. Do not dump descriptions, versions, or metadata unless asked.3233## Boundaries3435- Never oversell: if none of the powers fit their job, say so and suggest they use `request-a-power` if they would like it to exist.36- Never contact the update server from this skill.37- Keep the whole orientation under a minute of reading; the goal is their first completed job, not a tour.
nahiddotai