[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWNXCD9JVB6G9JZBJJZDS7":3,"skill-same:01M7BWNXCD9JVB6G9JZBJJZDS7":65},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BWNXCD9JVB6G9JZBJJZDS7","extensions",null,"Understand the extensions so that you can help a user configure and manage their incident.io agent estate. Use this when you're asked a question about incident.io  plugins, skills, connectors or MCPs (\"I want to setup an incident plugin\", \"How do I  add a triage skill?\"), or when you need to understand the user's existing configuration before editing a plugin or skill.","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-io\u002Fskills\u002Fextensions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: extensions\ndescription: >\n  Understand the extensions so that you can help a user configure and manage\n  their incident.io agent estate. Use this when you're asked a question about incident.io \n  plugins, skills, connectors or MCPs (\"I want to setup an incident plugin\", \"How do I \n  add a triage skill?\"), or when you need to understand the user's existing configuration\n  before editing a plugin or skill.\n---\n\n# Extensions\n\nBefore anything else, check the model this session runs on. These workflows need\nOpus\u002FSol level or higher; smaller models follow them unreliably. If this session is\nbelow that level, tell the user and recommend switching model before continuing.\n\nExtensions are how an organization gives incident.io's agents its own tools and\ninstructions. There are two kinds: **plugins** — directories of skills synced from the\norganization's repositories, which agents load and follow — and **connectors** — MCP\nservers whose tools agents can call.\n[references\u002Fextensions-product.md](references\u002Fextensions-product.md) explains how the\nsystem works; read it before answering questions about it or changing anything.\n\nThis skill is the entrypoint. It teaches the system, reads the current state of an\nestate, and picks the right mechanism for a problem — and it routes every specialised\njob to the skill that owns it rather than doing it here.\n\nWhatever the task, the first two moves are the same: read the estate, and hear what\nthe user needs. Nothing else — no drafting, no probing of any connected system —\nstarts before both.\n\n## Route by the task\n\n- **Understand the system** — what plugins, skills, and connectors are, how agents use\n  them, what's possible →\n  [references\u002Fextensions-product.md](references\u002Fextensions-product.md)\n- **Read the estate, or set it up** — what exists today (plugins and their sync state,\n  connections and their health, content), measured against what a ready estate has.\n  One walk serves every starting point, from scratch to a readiness pre-check.\n  → [references\u002Festate.md](references\u002Festate.md)\n- **Choose the right mechanism** — the user describes a problem (\"I want these steps\n  run at the start of an investigation\", \"I want something that diagnoses this error\n  code\") and it needs mapping to the feature that solves it: a skill, a runbook, an\n  architecture doc, a connector, or a combination. This picks the mechanism, not a\n  detailed plan of what to build — drafting the content is the owning skill's job.\n  → [references\u002Fchoosing-a-mechanism.md](references\u002Fchoosing-a-mechanism.md)\n- **Scaffold and register a plugin** — create the tree in the team's repository,\n  register it, and verify the first sync.\n  → [references\u002Fscaffold.md](references\u002Fscaffold.md)\n- **Write or improve a skill** → load the `skill-authoring` skill *now*, before\n  touching any target system — its create job owns the order of work (the user's\n  context first, exploration after), and starting the exploration here skips the\n  gates that make the skill worth writing.\n- **Write or answer from architecture docs** → the `architecture` skill\n- **Review the estate's health** (\"is our setup healthy? what's degraded?\") → the\n  `doctor` skill\n\n## Ground rules\n\n- **Ground before proposing.** Grounding means two things, and target-system\n  exploration is neither: the incident.io estate\n  ([references\u002Festate.md](references\u002Festate.md) — what's registered, connected, and\n  already written; `extension_plugin_list` is the first call), and the user's intent —\n  what they actually need, in their words. Probing the system a skill will cover is\n  part of *authoring*, owned by `skill-authoring`, and comes after the user has\n  confirmed what the skill is for. However inviting a connected tool surface is,\n  exploring it before that conversation is guessing with tools.\n- **Confirm before creating.** Every artefact — a directory, a registration, a doc —\n  is proposed with what it will contain, and created only on a yes.\n- **Requirements are few; the rest is guidance.** The hard requirements are what the\n  platform needs to function:\n  - a repository the connected source-control integration can read\n  - a registered plugin\n\n  Everything else (architecture docs, runbooks, more skills) is a recommendation:\n  explain why it produces better results, then respect the user's choice. A narrow\n  use case gets a narrow setup, not the full walk's ambitions.\n- **Speak the user's language, not this skill's.** The user hasn't read this file —\n  never cite \"the ground rules\", a reference filename, or \"the estate walk\" at them.\n  Say what you're doing plainly (\"I'm checking your configuration before we get\n  started\") and end a read-only pass with an offer of what you can help with next.\n- **Connections are created in the dashboard, never here.** Connecting a tool to\n  incident.io is an authentication flow. Where a gap is found, link the user to the\n  dashboard's Extensions page and continue with what exists.\n- **Specialised work goes to the skill that owns it.** This skill owns the\n  estate-level picture and the routing; the routes above name the owners.\n\n## What this skill is not for\n\nIncident response — this skill configures the machinery agents use, it doesn't\ninvestigate incidents.\n","# Extensions\n\nBefore anything else, check the model this session runs on. These workflows need\nOpus\u002FSol level or higher; smaller models follow them unreliably. If this session is\nbelow that level, tell the user and recommend switching model before continuing.\n\nExtensions are how an organization gives incident.io's agents its own tools and\ninstructions. There are two kinds: **plugins** — directories of skills synced from the\norganization's repositories, which agents load and follow — and **connectors** — MCP\nservers whose tools agents can call.\n[references\u002Fextensions-product.md](references\u002Fextensions-product.md) explains how the\nsystem works; read it before answering questions about it or changing anything.\n\nThis skill is the entrypoint. It teaches the system, reads the current state of an\nestate, and picks the right mechanism for a problem — and it routes every specialised\njob to the skill that owns it rather than doing it here.\n\nWhatever the task, the first two moves are the same: read the estate, and hear what\nthe user needs. Nothing else — no drafting, no probing of any connected system —\nstarts before both.\n\n## Route by the task\n\n- **Understand the system** — what plugins, skills, and connectors are, how agents use\n  them, what's possible →\n  [references\u002Fextensions-product.md](references\u002Fextensions-product.md)\n- **Read the estate, or set it up** — what exists today (plugins and their sync state,\n  connections and their health, content), measured against what a ready estate has.\n  One walk serves every starting point, from scratch to a readiness pre-check.\n  → [references\u002Festate.md](references\u002Festate.md)\n- **Choose the right mechanism** — the user describes a problem (\"I want these steps\n  run at the start of an investigation\", \"I want something that diagnoses this error\n  code\") and it needs mapping to the feature that solves it: a skill, a runbook, an\n  architecture doc, a connector, or a combination. This picks the mechanism, not a\n  detailed plan of what to build — drafting the content is the owning skill's job.\n  → [references\u002Fchoosing-a-mechanism.md](references\u002Fchoosing-a-mechanism.md)\n- **Scaffold and register a plugin** — create the tree in the team's repository,\n  register it, and verify the first sync.\n  → [references\u002Fscaffold.md](references\u002Fscaffold.md)\n- **Write or improve a skill** → load the `skill-authoring` skill *now*, before\n  touching any target system — its create job owns the order of work (the user's\n  context first, exploration after), and starting the exploration here skips the\n  gates that make the skill worth writing.\n- **Write or answer from architecture docs** → the `architecture` skill\n- **Review the estate's health** (\"is our setup healthy? what's degraded?\") → the\n  `doctor` skill\n\n## Ground rules\n\n- **Ground before proposing.** Grounding means two things, and target-system\n  exploration is neither: the incident.io estate\n  ([references\u002Festate.md](references\u002Festate.md) — what's registered, connected, and\n  already written; `extension_plugin_list` is the first call), and the user's intent —\n  what they actually need, in their words. Probing the system a skill will cover is\n  part of *authoring*, owned by `skill-authoring`, and comes after the user has\n  confirmed what the skill is for. However inviting a connected tool surface is,\n  exploring it before that conversation is guessing with tools.\n- **Confirm before creating.** Every artefact — a directory, a registration, a doc —\n  is proposed with what it will contain, and created only on a yes.\n- **Requirements are few; the rest is guidance.** The hard requirements are what the\n  platform needs to function:\n  - a repository the connected source-control integration can read\n  - a registered plugin\n\n  Everything else (architecture docs, runbooks, more skills) is a recommendation:\n  explain why it produces better results, then respect the user's choice. A narrow\n  use case gets a narrow setup, not the full walk's ambitions.\n- **Speak the user's language, not this skill's.** The user hasn't read this file —\n  never cite \"the ground rules\", a reference filename, or \"the estate walk\" at them.\n  Say what you're doing plainly (\"I'm checking your configuration before we get\n  started\") and end a read-only pass with an offer of what you can help with next.\n- **Connections are created in the dashboard, never here.** Connecting a tool to\n  incident.io is an authentication flow. Where a gap is found, link the user to the\n  dashboard's Extensions page and continue with what exists.\n- **Specialised work goes to the skill that owns it.** This skill owns the\n  estate-level picture and the routing; the routes above name the owners.\n\n## What this skill is not for\n\nIncident response — this skill configures the machinery agents use, it doesn't\ninvestigate incidents.\n",{"name":5,"description":7},"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fincident-io\u002Fskills\u002Fextensions",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill extensions",{"tool":39,"command":40},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill extensions",{"tool":42,"command":43},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill extensions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-io\u002Fskills\u002Fextensions\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fchoosing-a-mechanism.md","REFERENCE","参考文档",4651,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-io\u002Fskills\u002Fextensions\u002Freferences\u002Fchoosing-a-mechanism.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Festate.md",11299,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-io\u002Fskills\u002Fextensions\u002Freferences\u002Festate.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fextensions-product.md",7808,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-io\u002Fskills\u002Fextensions\u002Freferences\u002Fextensions-product.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fscaffold.md",6491,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fincident-io\u002Fskills\u002Fextensions\u002Freferences\u002Fscaffold.md",[66,72,79,85,92,99],{"skillNo":67,"name":68,"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":69,"categories":70,"keywords":71,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","workflow","Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of \"workflow\", \"durable functions\", \"resumable\", \"workflow sdk\", \"queue\", \"event\", \"push\", \"subscribe\", or step-based orchestration.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":80,"name":74,"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},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\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},"01M7BYASGMK935J33E21N5WTW0","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","vercel-storage","Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","vercel-services","Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]