{"id":31064,"plugin_id":"plugin_asdk_app_6ac466ba11f4819191ee609ea667f124","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-10T06:12:56.161Z","digest":"c1d62e944b9a67e16e7c71f910dbb6f4e89d35b8305c0b0b09aad936e74a1a6f","against":null,"payload":{"description":"Run right after Pika is installed or when the user chooses Set up for Pika — checks the Pika MCP server is connected and signed in, opens the app gallery and suggests a first creation.","included_files":[],"name":"onboarding","skill_md_contents":"---\nname: onboarding\ndescription: Run right after Pika is installed or when the user chooses Set up for Pika — checks the Pika MCP server is connected and signed in, opens the app gallery and suggests a first creation.\n---\n\n# Set up Pika\n\nPika works only through the tools of the Pika MCP server this plugin installs (`pika`, or `pika-staging` for the staging plugin): one tool per creation app (`create_video`, `headshot`, `product_ad`, …) plus `browse_apps`, `ask_for_media`, `get_job`, `get_account` and the rest. Never stand in for them with built-in image, video or audio generation.\n\n1. If there are no Pika tools in your tool list, Pika isn't connected or signed in. Tell the user how to sign in, then stop:\n   - Codex CLI: run `codex mcp login pika` (`codex mcp login pika-staging` for staging; `codex mcp list` shows the server's name and whether it's logged in).\n   - Codex or ChatGPT app: sign in to Pika from the plugin's settings, then start a new chat.\n   - Claude Code: run `/mcp` and sign in to Pika.\n2. Call `get_account` with `{}`.\n   - If it fails with a sign-in error (`SIGN_IN_REQUIRED` or \"Sign in to Pika to continue\"), the user isn't signed in yet. Most apps show their own sign-in prompt for it (a sign-in sheet in ChatGPT and Codex, a Connect card in Claude); ask the user to finish signing in there, then call `get_account` again. Where no prompt appears, use the steps in step 1.\n   - If it returns the account, tell the user their credit balance in one line. If its summary says \"No approval mode chosen yet\", call `show_settings` with `{}` and follow its `next`. When it opens the settings panel, end your turn: the panel saves the pick itself and posts it in the chat (or the user tells you when they're done), so don't call `set_preferences` for it, and another Pika view opened in the same turn would replace the panel. When it lists the modes as text instead, show them one line each and save the user's reply with `set_preferences` (autopilot also needs `auto_approve_credits`).\n3. Once an approval mode is saved, call `browse_apps` with `{}` to open the gallery.\n4. Offer three starters, one line each:\n   - Turn a product photo into a video ad (`product_ad`).\n   - Make a studio headshot from a selfie (`headshot`).\n   - Animate a photo into a short clip (`create_video`).\n5. If the user installed Pika in the middle of a task, skip the starters and continue that task with the `pika-create` playbook.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}