extensions
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.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 156
01 前言 Front Matter
- name
- extensions
- description
- 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.
02 资源文件 4
- 参考文档references/choosing-a-mechanism.md4.5 KB
- 参考文档references/estate.md11.0 KB
- 参考文档references/extensions-product.md7.6 KB
- 参考文档references/scaffold.md6.3 KB
03 SKILL.md 正文
Extensions
Before anything else, check the model this session runs on. These workflows need Opus/Sol level or higher; smaller models follow them unreliably. If this session is below that level, tell the user and recommend switching model before continuing.
Extensions are how an organization gives incident.io's agents its own tools and instructions. There are two kinds: plugins — directories of skills synced from the organization's repositories, which agents load and follow — and connectors — MCP servers whose tools agents can call. references/extensions-product.md explains how the system works; read it before answering questions about it or changing anything.
This skill is the entrypoint. It teaches the system, reads the current state of an estate, and picks the right mechanism for a problem — and it routes every specialised job to the skill that owns it rather than doing it here.
Whatever the task, the first two moves are the same: read the estate, and hear what the user needs. Nothing else — no drafting, no probing of any connected system — starts before both.
Route by the task
- Understand the system — what plugins, skills, and connectors are, how agents use them, what's possible → references/extensions-product.md
- Read the estate, or set it up — what exists today (plugins and their sync state, connections and their health, content), measured against what a ready estate has. One walk serves every starting point, from scratch to a readiness pre-check. → references/estate.md
- Choose the right mechanism — the user describes a problem ("I want these steps run at the start of an investigation", "I want something that diagnoses this error code") and it needs mapping to the feature that solves it: a skill, a runbook, an architecture doc, a connector, or a combination. This picks the mechanism, not a detailed plan of what to build — drafting the content is the owning skill's job. → references/choosing-a-mechanism.md
- Scaffold and register a plugin — create the tree in the team's repository, register it, and verify the first sync. → references/scaffold.md
- Write or improve a skill → load the
skill-authoringskill now, before touching any target system — its create job owns the order of work (the user's context first, exploration after), and starting the exploration here skips the gates that make the skill worth writing. - Write or answer from architecture docs → the
architectureskill - Review the estate's health ("is our setup healthy? what's degraded?") → the
doctorskill
Ground rules
-
Ground before proposing. Grounding means two things, and target-system exploration is neither: the incident.io estate (references/estate.md — what's registered, connected, and already written;
extension_plugin_listis the first call), and the user's intent — what they actually need, in their words. Probing the system a skill will cover is part of authoring, owned byskill-authoring, and comes after the user has confirmed what the skill is for. However inviting a connected tool surface is, exploring it before that conversation is guessing with tools. -
Confirm before creating. Every artefact — a directory, a registration, a doc — is proposed with what it will contain, and created only on a yes.
-
Requirements are few; the rest is guidance. The hard requirements are what the platform needs to function:
- a repository the connected source-control integration can read
- a registered plugin
Everything else (architecture docs, runbooks, more skills) is a recommendation: explain why it produces better results, then respect the user's choice. A narrow use case gets a narrow setup, not the full walk's ambitions.
-
Speak the user's language, not this skill's. The user hasn't read this file — never cite "the ground rules", a reference filename, or "the estate walk" at them. Say what you're doing plainly ("I'm checking your configuration before we get started") and end a read-only pass with an offer of what you can help with next.
-
Connections are created in the dashboard, never here. Connecting a tool to incident.io is an authentication flow. Where a gap is found, link the user to the dashboard's Extensions page and continue with what exists.
-
Specialised work goes to the skill that owns it. This skill owns the estate-level picture and the routing; the routes above name the owners.
What this skill is not for
Incident response — this skill configures the machinery agents use, it doesn't investigate incidents.
04 同仓库更多 Skills
business-data
暂无简介
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.
workflow
Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
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.
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.
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`.