[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79HVKSMB6C9CX75XESTQFVS":3,"skill-same:01M79HVKSMB6C9CX75XESTQFVS":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M79HVKSMB6C9CX75XESTQFVS","instafy-integration-onboarding",null,"Action-card policy for integration setup and guided onboarding in Instafy's browser.","instafy-dev\u002Finstafy","instafy-dev","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F233032513?v=4","01M79HSF94X6QYAFACH32J9DDE","Instafy","01M79HSF9TRDTDD5NKM9QSTGFW",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Fassets\u002Finstafy\u002F.agents\u002Fskills\u002Finstafy-integration-onboarding\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: instafy-integration-onboarding\ndescription: Action-card policy for integration setup and guided onboarding in Instafy's browser.\nrouting_keywords: token, api key, secret, connection, portal, dashboard, developer, walk me through, set up, integration, connect, github, repo, import, unauthorized, permission denied, 401, 403\n---\n\n# Integration onboarding (action-card contract)\n\nGoal: make provider workflows (GitHub, Slack, WhatsApp, etc.) proactively guide setup instead of failing silently.\n\n## Capability preflight\n\nBefore claiming success on provider work:\n- Identify the provider and requested capability (examples: repo clone, issues read, Slack post, WhatsApp send).\n- If auth\u002Fscope is missing or uncertain, return an onboarding action first.\n- Do not ask users to paste tokens in chat.\n\n## Automation strategy (API-first)\n\nIf the user asks for repeated\u002Fautomated actions against a third-party service:\n- Prefer official API\u002Fintegration flows first (more reliable and auditable).\n- Use browser automation for repeated or scheduled work only when no viable API exists. Opening the browser to look, verify or show the person the way is always fine.\n- If both are possible, explain the API option first and ask which path the user wants.\n\nFor high-risk domains (finance, payments, account\u002Fsecurity settings):\n- Require explicit confirmation before executing impactful actions.\n- Summarize the exact action before execution (target account, amount\u002Fchange, and expected outcome).\n\n## Required action types\n\nUse these actions in the JSON response:\n\n- `request_integration`\n  - `provider`: provider id (for example `github`, `slack`, `whatsapp`)\n  - optional `description`, `requiredScopes`, `capabilities`, `authMethods`, `suggestedSecretNames`, `suggestedSecrets`, `agentHandles`\n- `request_secret`\n  - `name`: env var (for example `GITHUB_TOKEN`)\n  - optional `valueLabel`, `description`, `whereToGet`, `sensitive`, `skill`, `agentHandles`; a skill setup says how to fill each\n- `request_browser`\n  - `task`: the user's browsing request, written as their own message\n  - optional `browserLocation`: `auto` unless the user named this device or the Workspace\n\nUse `request_integration` for account connection\u002Fscope onboarding.\nUse `request_secret` for project runtime tokens\u002Fwebhooks.\nUse `request_browser` to open Instafy's browser when no browser tools are on this turn.\n\n### Keep cards small\n\n- Treat action-card `description` fields as one-line hints (not documentation).\n- Put detailed setup steps (where to find tokens, what to click, how to verify) in the `summary` text.\n- Keep `requiredScopes`\u002F`capabilities` short; only include items you are confident are needed.\n- In `summary`, include a short numbered checklist for where to obtain credentials. If you don’t know the exact provider UI path, include a precise search phrase the user can copy and ask exactly one clarifying question.\n\n## Scope model\n\nKeep these scopes distinct:\n- User credential scope: user-owned identity\u002Fsession used to connect providers.\n- Project integration scope: per-project provider connection state + scopes\u002Fcapabilities.\n- Project secret scope: per-project runtime env vars for agent execution.\n\nDo not collapse OAuth credentials into project secrets by default.\n\n## Failure recovery rule\n\nIf commands or APIs fail with auth\u002Fpermission errors (401\u002F403\u002Funauthorized\u002Fpermission denied\u002Fmissing token):\n- Return the most relevant onboarding action(s) in the same response.\n- Ask the user to confirm when done, then retry.\n\n## GitHub repo onboarding\n\nTreat requests like these as direct repo-onboarding intents:\n- \"continue working on my project https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\"\n- \"import this repo\"\n- \"open this GitHub project\"\n\nDefault behavior:\n1. Treat the current space as the target workspace.\n2. Continue with repo import instead of sending the user through a separate onboarding script.\n3. Keep follow-up questions to a minimum. Only ask about branch or subfolder when the repo is clearly large\u002Fambiguous or the user asked for a specific slice.\n\nFor private or access-restricted repos:\n- If auth is missing or uncertain, emit `request_integration` for `github`.\n- Include only the scopes\u002Fcapabilities you are confident are needed for the next step (for repo import this is usually `repo` \u002F `repo.read`).\n- After connection completes, provide exactly one retry phrase that resumes the same repo request.\n\nAvoid product bloat:\n- Do not invent a bespoke multi-step onboarding checklist when the user already gave the repo intent in chat.\n- Prefer one direct retry phrase over multiple variants.\n- Use the dedicated onboarding UI only as a shortcut surface; the real contract is that the chat intent should work.\n- Do not silently redirect the user into a different space just because the same repo might exist elsewhere. Spaces are isolation boundaries.\n\n## Follow-up UX\n\nAfter onboarding completes, suggest one concrete retry prompt so the user can continue immediately.\n- Provide exactly one retry phrase. Don’t add an alternate “then reply …” phrase.\n\n## Showing the way in Instafy's browser\n\nWhen provider setup needs dashboard\u002Flogin interaction:\n- When setup involves the provider's own screens, open Instafy's browser without asking, once per setup. With browser tools on this turn, go there now. Without them, emit one `request_browser` action after any `request_secret` cards; write its `task` as the user's own request, and say in one sentence where it goes.\n- Open only an address a skill declares or the user gave you, and walk the screens the declaration names, in order. Never guess a provider address. When a skill declares more than one (such as live and demo) and the user has not chosen, open it only after they have.\n- Guide step-by-step and pause for user-only actions (login, MFA, consent) with `request_human_input` on their fields, so the user completes them on the page and chooses Let Octo continue. Never type a password, a one-time code or another credential, and never ask for one in chat.\n- Stop on the screen that lists a secret value (an API secret, token or key), such as the list whose row opens it. In Instafy's browser, never open a screen that shows the value and never ask the user to open one: others watching that browser can see it, it often cannot be copied out, and it reaches you with the next look at the page. Tell the user to open that same page in a tab of their own browser, open the value there and copy it into its `request_secret` card.\n- If the user closes or pauses the browser, give manual steps and do not open it again for this setup unless they ask.\n","# Integration onboarding (action-card contract)\n\nGoal: make provider workflows (GitHub, Slack, WhatsApp, etc.) proactively guide setup instead of failing silently.\n\n## Capability preflight\n\nBefore claiming success on provider work:\n- Identify the provider and requested capability (examples: repo clone, issues read, Slack post, WhatsApp send).\n- If auth\u002Fscope is missing or uncertain, return an onboarding action first.\n- Do not ask users to paste tokens in chat.\n\n## Automation strategy (API-first)\n\nIf the user asks for repeated\u002Fautomated actions against a third-party service:\n- Prefer official API\u002Fintegration flows first (more reliable and auditable).\n- Use browser automation for repeated or scheduled work only when no viable API exists. Opening the browser to look, verify or show the person the way is always fine.\n- If both are possible, explain the API option first and ask which path the user wants.\n\nFor high-risk domains (finance, payments, account\u002Fsecurity settings):\n- Require explicit confirmation before executing impactful actions.\n- Summarize the exact action before execution (target account, amount\u002Fchange, and expected outcome).\n\n## Required action types\n\nUse these actions in the JSON response:\n\n- `request_integration`\n  - `provider`: provider id (for example `github`, `slack`, `whatsapp`)\n  - optional `description`, `requiredScopes`, `capabilities`, `authMethods`, `suggestedSecretNames`, `suggestedSecrets`, `agentHandles`\n- `request_secret`\n  - `name`: env var (for example `GITHUB_TOKEN`)\n  - optional `valueLabel`, `description`, `whereToGet`, `sensitive`, `skill`, `agentHandles`; a skill setup says how to fill each\n- `request_browser`\n  - `task`: the user's browsing request, written as their own message\n  - optional `browserLocation`: `auto` unless the user named this device or the Workspace\n\nUse `request_integration` for account connection\u002Fscope onboarding.\nUse `request_secret` for project runtime tokens\u002Fwebhooks.\nUse `request_browser` to open Instafy's browser when no browser tools are on this turn.\n\n### Keep cards small\n\n- Treat action-card `description` fields as one-line hints (not documentation).\n- Put detailed setup steps (where to find tokens, what to click, how to verify) in the `summary` text.\n- Keep `requiredScopes`\u002F`capabilities` short; only include items you are confident are needed.\n- In `summary`, include a short numbered checklist for where to obtain credentials. If you don’t know the exact provider UI path, include a precise search phrase the user can copy and ask exactly one clarifying question.\n\n## Scope model\n\nKeep these scopes distinct:\n- User credential scope: user-owned identity\u002Fsession used to connect providers.\n- Project integration scope: per-project provider connection state + scopes\u002Fcapabilities.\n- Project secret scope: per-project runtime env vars for agent execution.\n\nDo not collapse OAuth credentials into project secrets by default.\n\n## Failure recovery rule\n\nIf commands or APIs fail with auth\u002Fpermission errors (401\u002F403\u002Funauthorized\u002Fpermission denied\u002Fmissing token):\n- Return the most relevant onboarding action(s) in the same response.\n- Ask the user to confirm when done, then retry.\n\n## GitHub repo onboarding\n\nTreat requests like these as direct repo-onboarding intents:\n- \"continue working on my project https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\"\n- \"import this repo\"\n- \"open this GitHub project\"\n\nDefault behavior:\n1. Treat the current space as the target workspace.\n2. Continue with repo import instead of sending the user through a separate onboarding script.\n3. Keep follow-up questions to a minimum. Only ask about branch or subfolder when the repo is clearly large\u002Fambiguous or the user asked for a specific slice.\n\nFor private or access-restricted repos:\n- If auth is missing or uncertain, emit `request_integration` for `github`.\n- Include only the scopes\u002Fcapabilities you are confident are needed for the next step (for repo import this is usually `repo` \u002F `repo.read`).\n- After connection completes, provide exactly one retry phrase that resumes the same repo request.\n\nAvoid product bloat:\n- Do not invent a bespoke multi-step onboarding checklist when the user already gave the repo intent in chat.\n- Prefer one direct retry phrase over multiple variants.\n- Use the dedicated onboarding UI only as a shortcut surface; the real contract is that the chat intent should work.\n- Do not silently redirect the user into a different space just because the same repo might exist elsewhere. Spaces are isolation boundaries.\n\n## Follow-up UX\n\nAfter onboarding completes, suggest one concrete retry prompt so the user can continue immediately.\n- Provide exactly one retry phrase. Don’t add an alternate “then reply …” phrase.\n\n## Showing the way in Instafy's browser\n\nWhen provider setup needs dashboard\u002Flogin interaction:\n- When setup involves the provider's own screens, open Instafy's browser without asking, once per setup. With browser tools on this turn, go there now. Without them, emit one `request_browser` action after any `request_secret` cards; write its `task` as the user's own request, and say in one sentence where it goes.\n- Open only an address a skill declares or the user gave you, and walk the screens the declaration names, in order. Never guess a provider address. When a skill declares more than one (such as live and demo) and the user has not chosen, open it only after they have.\n- Guide step-by-step and pause for user-only actions (login, MFA, consent) with `request_human_input` on their fields, so the user completes them on the page and chooses Let Octo continue. Never type a password, a one-time code or another credential, and never ask for one in chat.\n- Stop on the screen that lists a secret value (an API secret, token or key), such as the list whose row opens it. In Instafy's browser, never open a screen that shows the value and never ask the user to open one: others watching that browser can see it, it often cannot be copied out, and it reaches you with the next look at the page. Tell the user to open that same page in a tab of their own browser, open the value there and copy it into its `request_secret` card.\n- If the user closes or pauses the browser, give manual steps and do not open it again for this setup unless they ask.\n",{"name":5,"description":7,"routing_keywords":24},"token, api key, secret, connection, portal, dashboard, developer, walk me through, set up, integration, connect, github, repo, import, unauthorized, permission denied, 401, 403","main","b256e0c9a2d28d4e2d20296b433415ef27c8d4e3","packages\u002Fruntime-agent\u002Fassets\u002Finstafy\u002F.agents\u002Fskills\u002Finstafy-integration-onboarding",1,"https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy","https:\u002F\u002Fgithub.com\u002Finstafy-dev","instafy.dev","2026-11-15 00:42:15",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add instafy-dev\u002Finstafy --skill instafy-integration-onboarding",{"tool":39,"command":40},"bunx","bunx skills add instafy-dev\u002Finstafy --skill instafy-integration-onboarding",{"tool":42,"command":43},"pnpm","pnpm dlx skills add instafy-dev\u002Finstafy --skill instafy-integration-onboarding","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Fassets\u002Finstafy\u002F.agents\u002Fskills\u002Finstafy-integration-onboarding\u002FSKILL.md",true,[],[48,55,62,68,75,82],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7BE6WNHSHP6CW4X5JDGCJ1X","workspace","Work with an Instafy space — find and read its conversations and message history, inspect the person's agents and their context notes, and read run diagnostics. Use when the person mentions an Instafy space, a conversation, an agent such as @octo, a run or plan group id, or asks what was decided or tried earlier in the workspace.","https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fclaude-plugin\u002Finstafy\u002Fskills\u002Fworkspace\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M79HXANKJNWV4DQ1ZFN2T09W","gamma-renamed","Third fixture skill whose frontmatter name differs from its folder.","https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Ftests\u002Ffixtures\u002Fskills-pack\u002F.agents\u002Fskills\u002Fgamma\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M79HX9TD4129V5G2N1PE2AVP","beta","https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Ftests\u002Ffixtures\u002Fskills-pack\u002F.agents\u002Fskills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M79HX8CW8M8GATDJBXA6DJ4J","alpha","First fixture skill.","https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Ftests\u002Ffixtures\u002Fskills-pack\u002F.agents\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79HX3KZ9NY6GKVM0EDZ2JJK","instafy-web-research","Research and cite web facts, cross-check sources and respect site restrictions.","https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Fassets\u002Finstafy\u002F.agents\u002Fskills\u002Finstafy-web-research\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79HWZGBPY8H0E21FGCTRX79","instafy-space-review","Review accessible recent chats and start at most one useful private Octo conversation with grounded context and a natural next step. Use for an opted-in space review automation or “review this space”; it never carries out the suggested work.","https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Fassets\u002Finstafy\u002F.agents\u002Fskills\u002Finstafy-space-review\u002FSKILL.md",[],[]]