doctor
Review the health of your incident.io agent estate — plugins, skills, connections — and say what to fix, without fixing anything itself. Use whenever anyone asks whether their incident.io setup is healthy, what's degraded, or what to improve, in any phrasing — one-off or as a recurring review. Every finding routes to the thing that fixes it.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 156
01 前言 Front Matter
- name
- doctor
- description
- Review the health of your incident.io agent estate — plugins, skills, connections — and say what to fix, without fixing anything itself. Use whenever anyone asks whether their incident.io setup is healthy, what's degraded, or what to improve, in any phrasing — one-off or as a recurring review. Every finding routes to the thing that fixes it.
- argument-hint
- <a plugin or area to focus on — or nothing, to be shown what can be reviewed from here>
02 资源文件 6
- 参考文档references/content-drift.md4.1 KB
- 参考文档references/extensions.md7.3 KB
- 参考文档references/orient.md5.4 KB
- 参考文档references/progress.md3.3 KB
- 参考文档references/report.md9.0 KB
- 参考文档references/telemetry.md2.3 KB
03 SKILL.md 正文
Doctor
A review, not a repair: doctor reads the estate, ranks what it finds, and hands each finding to the thing that fixes it. It never edits a plugin's tree (skills, README, docs — any file), never re-syncs, never changes a setting, and never writes into the estate — the report itself is handed over, not filed. All of this holds when it runs on a schedule. That's what makes it safe to run weekly and boring to read when everything is fine, which is the goal.
The shape of a run
- Orient — a fast pass, cheap reads only: where the session is, whether a plugin lives here and corresponds to one the account knows, what the account's own health rollup says, and whether this agent's own install is current. Ends in a compact situating block the user sees within seconds. → references/orient.md
- Offer — an interactive, unscoped invocation pauses on that block plus a short menu of the reviews that make sense from here, each with an honest cost signal, and waits for the pick. A scoped invocation skips the menu but still shows the block; a scheduled run, with nobody there to read it, skips both. The skip rules are in orient.md.
- Review — the chosen legs, below, with a progress stream reporting each step as it completes so the run is legible while it runs. → references/progress.md
- Report — headlines name the main finding and summarize the rest. An optional situating block adds context; short findings carry routes, and briefs carry the detail. Follow references/report.md.
The legs
- Extensions — plugins and their skills, checked end to end: sync state, how skills perform once loaded, the feedback issues worth acting on, feedback orphaned by renames, and convention drift against the authoring rules. → references/extensions.md
- Connections and telemetry — what this session can and cannot read about the rest of the estate, stated honestly. → references/telemetry.md
- Content drift — the copies that were right when written: runbooks restating what a skill owns, procedures naming levers that no longer exist, pointers to homes that don't hold the content, and skill-shaped knowledge with no skill to live in. → references/content-drift.md
Run all three for a whole-estate review. A named plugin gets the Extensions and Content drift legs; Connections and telemetry contributes only its orient snapshot unless the user asks for that leg. For any other scope, run the legs the user named.
Ground rules
- Propose-only, always. Every finding becomes a route: an improvement brief for
the
skill-authoringskill's improve job, a structural gap for theextensionsskill, a change in the plugin's repository, or a named dashboard page. Doctor stops at the hand-off — the report is the run's last act, and acting on a brief is a new job the user starts, never a continuation of this one. - Verify before alarming. A computed status is a hint, not a verdict: check an issue's anchor against the current tree, and apply the reading corrections in skill-authoring's improve reference before reporting an issue as real or resolved.
- An unreadable surface is reported, not guessed. Where this session has no way to read part of the estate, the report says so and names where the answer lives. Never pad a leg with speculation to look thorough.
- Healthy is a finding. "All plugins synced, no actionable issues" is a complete and useful report line, not a failure to find something.
- The run is visible while it runs. Review reports each step as it finishes, per references/progress.md, so a review that takes minutes is something the user can follow rather than wait out. Those lines are status; the report restates everything and is what gets filed.
What this skill is not for
Setting the estate up or growing it — that's extensions (which routes here for
reviews, as this skill routes there for gaps). Making the edits — that's
skill-authoring. And incident response: doctor reviews the machinery agents use, not
live 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`.