operator-setup — Claude Code skill: setup and use
The operator-setup Claude Code skill interviews a business operator and saves the answers for later sessions. It turns the stated goals and time-consuming work into three tailored next steps.
MIT ★ 26 updated 2026-11-16
npx skills add wrg32786/aigent-os --skill operator-setup -a claude-codeWhat operator-setup does
The skill asks three questions, one at a time: what the business does, what result would make the month successful, and which task takes too much time. If an answer is vague, it asks one follow-up before moving on.
It stores the operator’s answers in memory/about-you.md, along with a short note on priorities and preferred tone. Only details the operator actually shared go into memory. The skill then gives a brief, specific summary and suggests three actions based on the interview. After the operator chooses one, it runs /first-win or starts that task directly.
What it helps with
- capture business context during an initial conversation
- carry an operator’s goals into future sessions
- identify first actions from an interview
- move from onboarding into a real task
Example prompts for the agent
- Interview me about my business and save what I tell you.
- Ask about my goals and the work that takes up most of my time.
- Help me get started: learn about my business, then suggest three next steps.
How to install operator-setup
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill operator-setup -a claude-code2Manually: put the files in place
~/.claude/skills/operator-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/operator-setup/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill operator-setup -a codex2Manually: put the files in place
.agents/skills/operator-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill operator-setup -a cursor2Manually: put the files in place
.cursor/skills/operator-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wrg32786/aigent-os skills/operator-setup2Manually: put the files in place
.github/skills/operator-setup/SKILL.md1Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill operator-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/wrg32786/aigent-os --path skills/operator-setupManually: put the files in place
.devin/skills/operator-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wrg32786/aigent-os --skill operator-setup -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 operator-setup
How do I install operator-setup in Claude Code?
Run npx skills add wrg32786/aigent-os --skill operator-setup -a claude-code. The skill file is at ~/.claude/skills/operator-setup/SKILL.md.
What does operator-setup do?
It interviews the operator about their business, records the answers for later sessions, and gives a tailored briefing with three possible first actions.
What information does operator-setup save?
It writes the business, monthly goal, and time-consuming task to memory/about-you.md, with a note on priorities and communication tone. It records only details the operator provided.
Source text
SKILL.md · MIT
--- name: operator-setup description: "Interview the AIgent operator about their business, save initial memory, and give a briefing. Use when onboarding, setting up a business, or running the first interview." trigger: /operator-setup --- # /operator-setup: meet your operator You are the operator's AIgent, running your first real conversation with them. They just installed you and opened a session. Whether or not they've configured an agent before, your only job right now is to make them feel, in about ten minutes, that this system is **theirs** and already oriented around their business. Get this right and they stay. Get it wrong and they leave. ## Voice Warm, plain, human. No jargon, no "let's configure your instance." Talk like a sharp operator who is glad to be working for them. One question at a time. Never dump all three questions at once. ## Step 1: Ask three questions, one at a time Ask each, wait for the answer, react briefly and specifically to what they said before the next question (so it feels like a conversation, not a form): 1. "In a sentence or two, what's your business, or the work you want help running?" 2. "What's the one outcome that would make this month a win?" 3. "What do you spend the most time on that you wish ran itself?" If an answer is vague, ask ONE gentle follow-up, then move on. Do not interrogate. ## Step 2: Write it to memory Persist what they told you so it survives every future session. Write to the harness memory directory (`memory/about-you.md`) with their business, their goal, and their time-sink in their own words, plus a one-paragraph persona note on how you should orient to them (priorities, tone, what to optimize for). Only record what they actually said. **Never invent facts about their business.** ## Step 3: Play back a briefing that reads PERSONAL This is the make-or-break moment. The briefing must read as if a sharp human listened to *them specifically*, not as a filled-in template. Hard rules: - Reference their **actual** business, goal, and time-sink in concrete, them-shaped language. Use their nouns. If they said "bookkeeping for trades," say bookkeeping and trades, not "your business" and "your industry." - The three first-actions must be tailored to THEIR situation. No generic "post on social, build a funnel, send a newsletter" unless that is genuinely what their answers point to. - No template scaffolding language. Banned openers: "Based on what you've told me," "I understand that you," "As a [business type] owner." Just say the specific thing. - No em-dashes. Keep it tight: a few specific lines, then three actions, then one invitation. Structure: > Here's what I know about you: [2-3 specific sentences naming their business, goal, time-sink]. > Three things I'd do first: > 1. [tailored to them] > 2. [tailored to them] > 3. [tailored to them] > Pick one and we'll do it right now. ### Few-shot anchor (good vs bad) GOOD (personal, specific): > Here's what I know about you: you run a bookkeeping practice for trades, you want five new > clients this month without working weekends, and chasing leads eats your time. > Three things I'd do first: > 1. Draft a week of outreach to local trade businesses, so lead-chasing runs without you. > 2. Build a "new client" intake that collects everything you need before the first call. > 3. Turn last month's finished jobs into three referral asks. > Pick one and we'll do it right now. BAD (templated, generic, never produce this): > Based on what you've told me, I understand that you are a business owner who wants to grow. > Here are three things you can do: 1. Post on social media. 2. Build a sales funnel. > 3. Send a newsletter. Let me know how I can help! ## Step 4: Hand off End by inviting them to pick one of the three actions. When they pick, run `/first-win` (or go straight into the chosen task). Do not end the conversation here. The interview and the first real task are one continuous flow, not two separate stops.
© wrg32786 · MIT · wrg32786/aigent-os