Update to AdAgnt

{
  "name": "adagnt-setup",
  "description": "First-run onboarding for AdAgnt. Connects the MCP server, walks the user through OAuth for each ad platform, verifies every connection, and seeds a STRATEGY.md so all later work is context-aware. Use in a fresh workspace or whenever connections need re-checking.",
  "included_files": [],
  "skill_md_contents": "---\nname: adagnt-setup\ndescription: First-run onboarding for AdAgnt. Connects the MCP server, walks the user through OAuth for each ad platform, verifies every connection, and seeds a STRATEGY.md so all later work is context-aware. Use in a fresh workspace or whenever connections need re-checking.\n---\n\n# AdAgnt Setup\n\nBring a new workspace from zero to fully connected. Work through the phases in order and do not skip verification — every later skill assumes the checks below have passed.\n\n## Phase 1 — Confirm the MCP connection\n\n1. Check whether AdAgnt tools (for example `get_connections_status`) are available in this session.\n2. If they are not, the server is not registered yet. Point the user at the connector configs in `plugins/` for their client:\n   - Claude Code: `plugins/claude-code/.mcp.json`\n   - Cursor: `plugins/cursor/mcp.json`\n   - Codex: `plugins/codex/config.toml`\n   - ChatGPT: `plugins/chatgpt/README.md`\n   The default local endpoint is `http://localhost:8734/mcp`.\n3. Once tools appear, call `get_usage_status` to confirm the account is active and to learn the plan's tool-call quota. Tell the user what plan they are on and how much headroom they have.\n\n## Phase 2 — Connect ad platforms\n\n1. Call `get_connections_status` (no arguments) to see which of Google Ads, Meta Ads, LinkedIn Ads, and TikTok Ads are already linked.\n2. Ask the user which platforms they actually advertise on. Do not push them to connect platforms they do not use.\n3. For each missing platform, direct the user to the AdAgnt dashboard to complete OAuth in their browser. Never ask for passwords, tokens, or API keys in chat — authorization happens only through the platform's own consent screen.\n4. After each authorization, re-run `get_connections_status` until the platform shows as connected.\n\n## Phase 3 — Verify accounts\n\n1. Call `list_connected_accounts` for each connected platform (pass the `platform` argument) and show the user the accounts found.\n2. If more than one account exists per platform, ask which is primary and call `switch_primary_account` accordingly.\n3. Sanity-check read access with one cheap read per platform: `list_campaigns` (Google), `list_meta_campaigns`, `list_linkedin_campaigns`, `list_tiktok_campaigns`. Empty results are fine; errors are not — surface any error verbatim and stop until resolved.\n\n## Phase 4 — Seed the strategy document\n\n1. Look for `STRATEGY.md` in the workspace root. If it exists, read it and confirm with the user that it is current.\n2. If it does not exist, gather context before writing it:\n   - Call `infer_business_profile` (Google) to have the server derive vertical, audience, and goals from account history, when a Google account is connected.\n   - Call `get_business_profile` to read anything already saved server-side.\n   - Ask the user for whatever is still missing: what they sell, who buys it, main competitors, target CPA or ROAS, monthly budget, brand voice.\n3. Create `STRATEGY.md` with the six sections defined by the `adagnt-strategy` skill: Business Profile, Target Audience, Competitive Landscape, Campaign Strategy, Brand Voice, Performance History. Leave `Performance History` as an empty log with a dated \"workspace initialized\" entry.\n4. Mirror the durable facts server-side with `save_business_profile` (vertical, size, audience, geography, goal, seasonality) so tools that read the profile behave consistently.\n\n## Done criteria\n\n- MCP tools respond and quota is known.\n- Every platform the user advertises on shows connected in `get_connections_status`.\n- `list_connected_accounts` returns the expected accounts and a primary is chosen.\n- `STRATEGY.md` exists with all six sections filled in (Performance History may be just the init entry).\n\nReport a short summary: platforms connected, accounts selected, plan/quota, and the path to `STRATEGY.md`.\n"
}