[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79HWSXWJMCVQKDP99P873RQ":3,"skill-same:01M79HWSXWJMCVQKDP99P873RQ":50},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":6,"ownerHtmlUrl":34,"ownerBlogUrl":35,"ownerDescription":6,"updatedAt":36,"install":37,"resources":49},"01M79HWSXWJMCVQKDP99P873RQ","instafy-skill-router",null,"Decide which Instafy skill(s) to apply for a user request (browsing vs previews vs secrets, etc).","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-skill-router\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: instafy-skill-router\ndescription: Decide which Instafy skill(s) to apply for a user request (browsing vs previews vs secrets, etc).\ncontext_kind: meta\ncontext_parent: instafy-persistent-contexts\ncontext_children: instafy-automations, instafy-browser-automation, instafy-byoc-ai-credentials, instafy-collaboration, instafy-conversation-history, instafy-diagnostics, instafy-frontend-previews, instafy-git-canonical-conflicts, instafy-git-canonical-sync, instafy-integration-onboarding, instafy-interactive-artifacts, instafy-learning-policy, instafy-location-sharing, instafy-research-team, instafy-runtime-flavors, instafy-secrets, instafy-skill-import-compat, instafy-space-review, instafy-web-research\nalways_include: true\nmax_children: 3\n---\n\n# Skill router (meta)\n\nNever prune: yes\n\nGoal: keep behavior consistent by selecting the right skill(s) based on the user’s request.\n\nTreat the selected skill set as the active branch of the persistent context tree for this turn.\n\n## How to use (strict)\n\n1. Skim the **Skills index** in the project memory snapshot (names + descriptions).\n2. Pick the smallest set of skills that apply.\n3. Follow those skill runbooks. Do not invent new workflows when a relevant skill exists.\n\nNotes:\n- Do not mention “skills” to the user unless they asked.\n- Prefer skill guidance over ad-hoc shell commands.\n- If two skills apply, you may combine them, but keep the execution mode clear (for example: “Tunnel preview mode” vs “Live browser assist mode”).\n- An outside lookup that is unavailable (exit 4, `status: \"unavailable\"`: a place search, a router, a store's site did\n  not answer) is not \"not found\": never retry it with another query or call the thing missing. Use what was found,\n  say plainly what could not be looked up, and offer to try again.\n\n## Routing rules (default)\n\nUse these mappings unless a project-specific skill overrides them.\n\n- **A site or server running in this space** (a dev server, a static file server, \"show me a preview\", localhost, 127.0.0.1, any port here)\n  - Use `instafy-frontend-previews`: show it to people with a private Studio preview card (`instafy preview open ... --serve-cmd \"\u003Ccommand>\" --start`, which also keeps it running after the turn) and check it yourself with `instafy preview check`.\n  - Not Instafy's browser: its safety policy blocks this space's own addresses (localhost, 127.0.0.1, 0.0.0.0, private addresses) and non-web ports.\n\n- **Anything a public web page would help with** (look something up, check or verify a public page, show a site's screens, guided clicks, sign-in)\n  - Use `instafy-browser-automation` and open the browser without asking in chat first; its site and action prompts still apply. Not for a site running in this space (above).\n  - Use the exposed Personal or Shared Browser tools. If neither is exposed, follow the skill's `request_browser` handoff so Studio can open or resume the appropriate browser.\n\n- **A fact from the web for an answer or a page** (prices, opening hours, timetables, addresses, places or products to compare, \"with sources\")\n  - Use `instafy-web-research`: which sources to read, how many, cross-checking, citing, and the link-only sites.\n  - Read public pages that need no JavaScript or sign-in with `instafy web read \u003Curl…> --json` (no browser card); its `provenance` is what to cite.\n  - Combine with `instafy-browser-automation` when the reads go through Instafy's browser (a page `instafy web read` reports as `needs_browser`, an aggregator, a page the person wants to see); one card may carry up to 6 related reads.\n\n- **Public page text \u002F element counts \u002F computed CSS \u002F screenshot verification**\n  - Use `instafy-browser-automation`.\n  - Prefer `instafy_local_browser.observe` when it is exposed; it is headless and read-only, not an interactive or authenticated session.\n\n- **A page to tap through: map, ranking, comparison or shopping table, dashboard, quiz, timeline, planner, tracker**\n  - Use `instafy-interactive-artifacts`: it picks the builder from the installed skills (a skill for that kind of\n    page, such as a map, `instafy-bound-sites` for values checked per click, a starter site otherwise) and shows the\n    result with `instafy preview open`.\n  - Many items to research live first (a long trip, several products): `instafy-research-team`.\n\n- **Near me \u002F around me \u002F my current location** (the user's own position; no place named)\n  - Use `instafy-location-sharing`.\n  - A named city, area, address or venue is not a location request: use it as given.\n  - Prefer an inline location action card over telling the user to search manually.\n  - Combine with `instafy-browser-automation` when a page would help after location is shared.\n\n- **Shareable preview URL \u002F mobile-friendly link \u002F “can you show me a demo link”**\n  - Use `instafy-frontend-previews` (tunnel preview mode).\n  - Ask for consent before creating a public URL. Check the site yourself with `instafy preview check`; Instafy's browser can open only its public tunnel URL, never the space's own address.\n\n- **Missing env vars \u002F API keys \u002F OAuth client setup \u002F dashboards**\n  - Use `instafy-integration-onboarding` for the step-by-step plan.\n  - Use `instafy-secrets` to request\u002Fstore secrets (never write secrets to files).\n  - When a provider's screens are involved, combine with `instafy-browser-automation` and open the browser to show them the way.\n\n- **Git canonical syncing \u002F conflicts**\n  - Use `instafy-git-canonical-sync` for normal sync.\n  - Use `instafy-git-canonical-conflicts` when sync hits conflicts.\n\n- **Runtime flavor\u002Fimage selection**\n  - Use `instafy-runtime-flavors`.\n\n- **Bring-your-own AI credentials**\n  - Use `instafy-byoc-ai-credentials`.\n\n- **Invite teammate \u002F add collaborator \u002F share this space by email \u002F change teammate access**\n  - Use `instafy-collaboration`.\n  - Direct the user to the interactive **Invite** UI or the Studio composer `\u002Finvite \u003Cemail> \u003Cviewer|builder>` command.\n  - For existing-member or pending-invite changes, direct the user to **Invite → Manage access**.\n  - Interpret “write access” as `builder`; project sharing only offers `viewer` and `builder`.\n  - Do not run CLI sharing commands from a runtime job. Scoped runtime\u002Ftool tokens intentionally cannot manage sharing.\n\n- **Earlier chat \u002F other conversation \u002F previous discussion \u002F “we talked about this before”**\n  - Use `instafy-conversation-history`.\n  - Prefer normal-language lookup over teaching special composer syntax.\n  - Search first with `instafy conversation search \"\u003Ckeywords>\"`, then inspect with `instafy conversation show \u003Cid> --transcript`.\n\n- **Getting started \u002F “I'm new here; what should I work on first?”**\n  - When no goal is stated and the person is not asking to inspect existing work, ask one short question about what they want to build or solve in this chat. Do not require a history review just to ask it, or claim the space is empty without evidence.\n  - If they already gave a goal, help with that goal directly.\n\n- **Review this space \u002F useful next actions from existing work \u002F “what should we pick up next?”**\n  - Use `instafy-space-review` for a bounded, on-demand review in the current chat.\n  - Read prior recommendations and accessible conversation evidence before proposing at most one useful next step. Respect delivered, accepted, dismissed and postponed topics; do not schedule reviews or execute the suggestion.\n\n- **Start recurring space reviews \u002F schedule check-ins \u002F start check-ins and review now**\n  - Use `instafy-automations` to list and create or update the `space_review` schedule. For an explicit immediate review too, trigger that schedule once after saving it; do not also review in the setup chat.\n\n- **Failed run \u002F runtime error \u002F diagnose \u002F investigate \u002F support report**\n  - Use `instafy-diagnostics`.\n  - Read signed-in-user diagnostics first; never scrape local logs or use raw\u002Foperator APIs.\n  - Keep diagnosis read-only unless the user explicitly asks to file a report, then preview and\n    obtain confirmation before submitting once.\n\n- **“Don't remind me again” \u002F “remind me tonight” \u002F “let's do this weekend” \u002F “check in less often” \u002F reminders \u002F schedules \u002F recurring tasks \u002F automation management**\n  - Use `instafy-automations`.\n  - For feedback on this chat's proactive suggestion, use `instafy recommendations current`, then `dismiss` or `remind`. Save the preference before acknowledging it.\n  - Changes to overall check-in frequency belong on the existing space review automation. Ordinary reminders use the normal automation commands.\n  - Interpret times in the user's known local timezone unless they explicitly say otherwise; ask when it is missing. A postponement schedules a reminder, not automatic execution of the task.\n\n## Ambiguous cases\n\n- If the person asks to \"open it in the browser\" for a site running in this space: say in one line that the browser's safety policy blocks the space's own addresses, point to the preview card (open one with `instafy-frontend-previews` if there is none), and offer a public link only after they agree to one.\n- If the user asks “use a browser” but they actually want a shareable link:\n  - Ask one short clarification: “Do you want a shareable public preview link, or a live browser walkthrough here?”\n- For current information (news, prices, releases, status pages):\n  - Read it with `instafy web read` or `instafy-browser-automation`, choosing and citing sources with `instafy-web-research`.\n  - Answer from memory only when no page can be read, and then say no live browsing was used.\n","# Skill router (meta)\n\nNever prune: yes\n\nGoal: keep behavior consistent by selecting the right skill(s) based on the user’s request.\n\nTreat the selected skill set as the active branch of the persistent context tree for this turn.\n\n## How to use (strict)\n\n1. Skim the **Skills index** in the project memory snapshot (names + descriptions).\n2. Pick the smallest set of skills that apply.\n3. Follow those skill runbooks. Do not invent new workflows when a relevant skill exists.\n\nNotes:\n- Do not mention “skills” to the user unless they asked.\n- Prefer skill guidance over ad-hoc shell commands.\n- If two skills apply, you may combine them, but keep the execution mode clear (for example: “Tunnel preview mode” vs “Live browser assist mode”).\n- An outside lookup that is unavailable (exit 4, `status: \"unavailable\"`: a place search, a router, a store's site did\n  not answer) is not \"not found\": never retry it with another query or call the thing missing. Use what was found,\n  say plainly what could not be looked up, and offer to try again.\n\n## Routing rules (default)\n\nUse these mappings unless a project-specific skill overrides them.\n\n- **A site or server running in this space** (a dev server, a static file server, \"show me a preview\", localhost, 127.0.0.1, any port here)\n  - Use `instafy-frontend-previews`: show it to people with a private Studio preview card (`instafy preview open ... --serve-cmd \"\u003Ccommand>\" --start`, which also keeps it running after the turn) and check it yourself with `instafy preview check`.\n  - Not Instafy's browser: its safety policy blocks this space's own addresses (localhost, 127.0.0.1, 0.0.0.0, private addresses) and non-web ports.\n\n- **Anything a public web page would help with** (look something up, check or verify a public page, show a site's screens, guided clicks, sign-in)\n  - Use `instafy-browser-automation` and open the browser without asking in chat first; its site and action prompts still apply. Not for a site running in this space (above).\n  - Use the exposed Personal or Shared Browser tools. If neither is exposed, follow the skill's `request_browser` handoff so Studio can open or resume the appropriate browser.\n\n- **A fact from the web for an answer or a page** (prices, opening hours, timetables, addresses, places or products to compare, \"with sources\")\n  - Use `instafy-web-research`: which sources to read, how many, cross-checking, citing, and the link-only sites.\n  - Read public pages that need no JavaScript or sign-in with `instafy web read \u003Curl…> --json` (no browser card); its `provenance` is what to cite.\n  - Combine with `instafy-browser-automation` when the reads go through Instafy's browser (a page `instafy web read` reports as `needs_browser`, an aggregator, a page the person wants to see); one card may carry up to 6 related reads.\n\n- **Public page text \u002F element counts \u002F computed CSS \u002F screenshot verification**\n  - Use `instafy-browser-automation`.\n  - Prefer `instafy_local_browser.observe` when it is exposed; it is headless and read-only, not an interactive or authenticated session.\n\n- **A page to tap through: map, ranking, comparison or shopping table, dashboard, quiz, timeline, planner, tracker**\n  - Use `instafy-interactive-artifacts`: it picks the builder from the installed skills (a skill for that kind of\n    page, such as a map, `instafy-bound-sites` for values checked per click, a starter site otherwise) and shows the\n    result with `instafy preview open`.\n  - Many items to research live first (a long trip, several products): `instafy-research-team`.\n\n- **Near me \u002F around me \u002F my current location** (the user's own position; no place named)\n  - Use `instafy-location-sharing`.\n  - A named city, area, address or venue is not a location request: use it as given.\n  - Prefer an inline location action card over telling the user to search manually.\n  - Combine with `instafy-browser-automation` when a page would help after location is shared.\n\n- **Shareable preview URL \u002F mobile-friendly link \u002F “can you show me a demo link”**\n  - Use `instafy-frontend-previews` (tunnel preview mode).\n  - Ask for consent before creating a public URL. Check the site yourself with `instafy preview check`; Instafy's browser can open only its public tunnel URL, never the space's own address.\n\n- **Missing env vars \u002F API keys \u002F OAuth client setup \u002F dashboards**\n  - Use `instafy-integration-onboarding` for the step-by-step plan.\n  - Use `instafy-secrets` to request\u002Fstore secrets (never write secrets to files).\n  - When a provider's screens are involved, combine with `instafy-browser-automation` and open the browser to show them the way.\n\n- **Git canonical syncing \u002F conflicts**\n  - Use `instafy-git-canonical-sync` for normal sync.\n  - Use `instafy-git-canonical-conflicts` when sync hits conflicts.\n\n- **Runtime flavor\u002Fimage selection**\n  - Use `instafy-runtime-flavors`.\n\n- **Bring-your-own AI credentials**\n  - Use `instafy-byoc-ai-credentials`.\n\n- **Invite teammate \u002F add collaborator \u002F share this space by email \u002F change teammate access**\n  - Use `instafy-collaboration`.\n  - Direct the user to the interactive **Invite** UI or the Studio composer `\u002Finvite \u003Cemail> \u003Cviewer|builder>` command.\n  - For existing-member or pending-invite changes, direct the user to **Invite → Manage access**.\n  - Interpret “write access” as `builder`; project sharing only offers `viewer` and `builder`.\n  - Do not run CLI sharing commands from a runtime job. Scoped runtime\u002Ftool tokens intentionally cannot manage sharing.\n\n- **Earlier chat \u002F other conversation \u002F previous discussion \u002F “we talked about this before”**\n  - Use `instafy-conversation-history`.\n  - Prefer normal-language lookup over teaching special composer syntax.\n  - Search first with `instafy conversation search \"\u003Ckeywords>\"`, then inspect with `instafy conversation show \u003Cid> --transcript`.\n\n- **Getting started \u002F “I'm new here; what should I work on first?”**\n  - When no goal is stated and the person is not asking to inspect existing work, ask one short question about what they want to build or solve in this chat. Do not require a history review just to ask it, or claim the space is empty without evidence.\n  - If they already gave a goal, help with that goal directly.\n\n- **Review this space \u002F useful next actions from existing work \u002F “what should we pick up next?”**\n  - Use `instafy-space-review` for a bounded, on-demand review in the current chat.\n  - Read prior recommendations and accessible conversation evidence before proposing at most one useful next step. Respect delivered, accepted, dismissed and postponed topics; do not schedule reviews or execute the suggestion.\n\n- **Start recurring space reviews \u002F schedule check-ins \u002F start check-ins and review now**\n  - Use `instafy-automations` to list and create or update the `space_review` schedule. For an explicit immediate review too, trigger that schedule once after saving it; do not also review in the setup chat.\n\n- **Failed run \u002F runtime error \u002F diagnose \u002F investigate \u002F support report**\n  - Use `instafy-diagnostics`.\n  - Read signed-in-user diagnostics first; never scrape local logs or use raw\u002Foperator APIs.\n  - Keep diagnosis read-only unless the user explicitly asks to file a report, then preview and\n    obtain confirmation before submitting once.\n\n- **“Don't remind me again” \u002F “remind me tonight” \u002F “let's do this weekend” \u002F “check in less often” \u002F reminders \u002F schedules \u002F recurring tasks \u002F automation management**\n  - Use `instafy-automations`.\n  - For feedback on this chat's proactive suggestion, use `instafy recommendations current`, then `dismiss` or `remind`. Save the preference before acknowledging it.\n  - Changes to overall check-in frequency belong on the existing space review automation. Ordinary reminders use the normal automation commands.\n  - Interpret times in the user's known local timezone unless they explicitly say otherwise; ask when it is missing. A postponement schedules a reminder, not automatic execution of the task.\n\n## Ambiguous cases\n\n- If the person asks to \"open it in the browser\" for a site running in this space: say in one line that the browser's safety policy blocks the space's own addresses, point to the preview card (open one with `instafy-frontend-previews` if there is none), and offer a public link only after they agree to one.\n- If the user asks “use a browser” but they actually want a shareable link:\n  - Ask one short clarification: “Do you want a shareable public preview link, or a live browser walkthrough here?”\n- For current information (news, prices, releases, status pages):\n  - Read it with `instafy web read` or `instafy-browser-automation`, choosing and citing sources with `instafy-web-research`.\n  - Answer from memory only when no page can be read, and then say no live browsing was used.\n",{"name":5,"description":7,"context_kind":24,"max_children":25,"always_include":26,"context_parent":27,"context_children":28},"meta",3,true,"instafy-persistent-contexts","instafy-automations, instafy-browser-automation, instafy-byoc-ai-credentials, instafy-collaboration, instafy-conversation-history, instafy-diagnostics, instafy-frontend-previews, instafy-git-canonical-conflicts, instafy-git-canonical-sync, instafy-integration-onboarding, instafy-interactive-artifacts, instafy-learning-policy, instafy-location-sharing, instafy-research-team, instafy-runtime-flavors, instafy-secrets, instafy-skill-import-compat, instafy-space-review, instafy-web-research","main","b256e0c9a2d28d4e2d20296b433415ef27c8d4e3","packages\u002Fruntime-agent\u002Fassets\u002Finstafy\u002F.agents\u002Fskills\u002Finstafy-skill-router",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":38,"prompt":48,"zipAvailable":26},[39,42,45],{"tool":40,"command":41},"npx","npx skills add instafy-dev\u002Finstafy --skill instafy-skill-router",{"tool":43,"command":44},"bunx","bunx skills add instafy-dev\u002Finstafy --skill instafy-skill-router",{"tool":46,"command":47},"pnpm","pnpm dlx skills add instafy-dev\u002Finstafy --skill instafy-skill-router","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Finstafy-dev\u002Finstafy\u002Fblob\u002Fmain\u002Fpackages\u002Fruntime-agent\u002Fassets\u002Finstafy\u002F.agents\u002Fskills\u002Finstafy-skill-router\u002FSKILL.md",[],[51,58,65,71,78,85],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"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":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"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":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]