Update to vidIQ

{
  "description": "Set up, verify, or troubleshoot vidIQ MCP and pick a first workflow. Use when asked to connect vidIQ or a YouTube channel, 'is vidIQ connected', 'which channel is linked', 'check my credits', or when vidIQ tools are missing, a call returns 401, 403, or verification errors, credits run out, or a thumbnail, watch, or script job is stuck. Not for creator research.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 441
    },
    {
      "relative_path": "references/job-recovery.md",
      "size_in_bytes": 976
    },
    {
      "relative_path": "references/live-surface-notes.md",
      "size_in_bytes": 2014
    },
    {
      "relative_path": "references/troubleshooting.md",
      "size_in_bytes": 2207
    }
  ],
  "name": "vidiq-get-started",
  "skill_md_contents": "---\nname: vidiq-get-started\ndescription: Set up, verify, or troubleshoot vidIQ MCP and pick a first workflow. Use when asked to connect vidIQ or a YouTube channel, 'is vidIQ connected', 'which channel is linked', 'check my credits', or when vidIQ tools are missing, a call returns 401, 403, or verification errors, credits run out, or a thumbnail, watch, or script job is stuck. Not for creator research.\n---\n\n# vidIQ Get Started\n\nRead [Live surface notes](references/live-surface-notes.md) first, even when using only supplied evidence.\n\nHelp the creator connect, diagnose a problem, or choose a workflow. Run only the relevant branch:\n\n- Connection, channel, or balance checks: use the relevant steps below.\n- Errors or charge questions: read [Troubleshooting](references/troubleshooting.md).\n- Existing or interrupted jobs: read [Job recovery](references/job-recovery.md). To list active\n  jobs, use `vidiq_jobs_list` with `status: \"inprogress\"`.\n- No YouTube channel connected, or a write tool asks for verification: use steps 3 and 6 below.\n- Saved research: `vidiq_bookmarks_list` returns the creator's saved videos, channels, and\n  keywords when they ask what they bookmarked.\n- Capabilities: summarize the outcomes supported by the exposed tools.\n\n## Connect and verify\n\n1. Inspect whether vidIQ tools are visible. Visibility confirms that the client loaded the\n   server; successful account-state calls establish authorization.\n2. If tools are missing, check installation, enablement, and client reload requirements.\n   Use the client's native MCP authentication action when available; otherwise follow its\n   connection flow and the [official setup guide](https://support.vidiq.com/en/articles/15082430-vidiq-mcp).\n   Wait for browser authorization, then re-check. Never request credentials in chat.\n3. Call `vidiq_user_channels` once and report the returned authorized IDs.\n   Account labels are optional and useful only for diagnosis.\n   An empty or unexpected list can indicate the wrong account; suggest reconnecting with the\n   intended account without claiming token expiry. When no channel is connected, or another\n   tool reports that no YouTube channel is connected, call `vidiq_connect_youtube_channel`, show\n   its widget, wait for the creator to finish, then retry the original request. The connection\n   and authorization tools are free and are not exposed by the Claude.ai directory connector.\n4. Resolve the intended channel only before channel-specific work. If several IDs are returned,\n   use the user's explicit selection; do not pick the first or largest. Enrich titles with\n   `vidiq_get_channels_by_ids` only when needed. A channel outside the authorized\n   set can receive public research, but not private analytics.\n5. Use `vidiq_balance` to explain returned renewable and\n   add-on credits, preserving `unlimited` and `null`.\n6. Before a write workflow (video details or thumbnail) or when a tool returns\n   `status: verification_required`, call `vidiq_authorize_with_youtube`, show its widget, and wait\n   for the creator to use it. Do not repeat the write until they confirm verification is complete.\n\n## Choose the next step\n\nAfter setup, use the creator's stated decision. If it is unclear, ask one compact question and offer:\n\n- **Package an existing idea or video:** `vidiq-packaging-studio`.\n- **Discover an idea:** `vidiq-video-ideas`; feed its concept cards into packaging for an\n  end-to-end request.\n- **Review performance:** `vidiq-channel-audit`, or `vidiq-new-upload-review` for a recent upload.\n- **Change something on YouTube:** `vidiq-video-metadata` for a video's details or thumbnail.\n\nHonor a more specific request with its matching skill; ask what vidIQ can do and the answer is\nthe routing table in the agent guide. Supplied-context analysis or text drafting\nmay need no MCP calls. Do not run research merely to demonstrate the connection.\nOnboarding alone does not authorize later generation or state changes.\n\n## Report\n\nReport the requested check's result, any issue, and the next action. For setup, include connection\nand authorization state, relevant channels and credits, and one recommended workflow. For job\nrecovery, report the actual job state and result or pending ID.\n"
}