AGENT SKILL

skill-authoring

Create and improve the skills in your own plugins — the ones incident.io's agents and your coding agents load. Use whenever you're writing, editing, or reviewing a skill in any way: creating one, improving one from usage feedback or a review brief, or asking what makes a good skill.

License 许可
MIT
最近更新
2026-11-13
Stars
★ 29
Forks
156

01 前言 Front Matter

name
skill-authoring
description
Create and improve the skills in your own plugins — the ones incident.io's agents and your coding agents load. Use whenever you're writing, editing, or reviewing a skill in any way: creating one, improving one from usage feedback or a review brief, or asking what makes a good skill.
argument-hint
<what the skill should do — or the skill to improve and why>

02 资源文件 6

03 SKILL.md 正文

Skill authoring

A skill is instructions your agents follow: a SKILL.md with a triggering description, plus references it loads on demand. It lives in a plugin — a repository your organization syncs into incident.io and can also install into coding agents. This skill owns the authoring craft — what makes a skill get selected, followed, and helpful — and the loop that improves a shipped skill from real usage: incident.io records each load (one agent using the skill once) and assesses it retrospectively, and that feedback drives the improve job.

The two jobs

  • Create — author a new skill into the user's plugin: pin it down with concrete trigger examples, check nothing owns the job already, draft to the format, register it, ship it. → references/create.md
  • Improve — edit an existing skill from evidence: read its usage feedback with improve.md's reading corrections applied, fix by theme without undoing credited strengths, verify the fix against the recorded issue where the session can, ship, confirm. → references/improve.md

Both jobs load the same two files before drafting: references/format.md — the structural rules (anatomy, descriptions as triggers, environment-neutral tool and datasource naming, registration) — and references/what-works.md — what the best-performing skills share, from incident.io's own estate and the assessment of real usage. Format answers "is this valid"; what-works answers "will this get followed". references/example.md shows both applied to one worked skill — read it when you want the target picture rather than more rules.

One further reference is conditional: references/triage-skills.md — read it when the skill should be reached for by incident.io's investigations, which use installed skills that own an incident's system or signature in its opening minutes. Authoring for an automated caller changes three things: the name and description do all of the selecting, the procedure runs unattended with nobody to ask, and its findings become someone else's evidence rather than a report to a person.

Where the skills live

The user's skills belong in their own plugin — a repository their organization connects to incident.io — never in this one. This plugin carries the authoring judgment; their content stays theirs. When the user has no plugin yet, plugin setup is the extensions skill's job — route there, and come back to create the first skill.

Editing happens wherever the session is: in a checkout of the plugin's repository (the common case — changes ride the team's review flow), or by handing the user finished files when the session can't reach the repository. Never write into a plugin the user didn't point you at.

What this skill is not for

Runbooks and architecture docs — those are content with their own formats, owned by the runbooks and architecture skills in this plugin; a skill is instructions for an agent, not knowledge for a person. And reviewing all your plugins at once ("are our skills healthy?") is the doctor skill's job — this skill works one skill at a time, from evidence about that skill.

04 同仓库更多 Skills

CognitionAI
CognitionAI/devin-marketplace

business-data

暂无简介

★ 29
CognitionAI
CognitionAI/devin-marketplace

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.

★ 29
CognitionAI
CognitionAI/devin-marketplace

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.

★ 29
CognitionAI
CognitionAI/devin-marketplace

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.

★ 29
CognitionAI
CognitionAI/devin-marketplace

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.

★ 29
CognitionAI
CognitionAI/devin-marketplace

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`.

★ 29