Extensions Review
作者 incident-io443f47164eda無授權條款2 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新
Review what your extensions did over a period: the skill loads that made a real difference, told through the incident or conversation each one happened in, and the incidents no skill or runbook covered. Use whenever anyone wants a review, digest, or pulse of extension or skill usage over a window — "how did our skills do this week", "post yesterday's extensions review to our channel" — one-off or on a schedule. Whether the estate is healthy (sync state, funnels, issues to fix) is the doctor skill, not this one.
僅公開檔案列表。將技能安裝到工作區後即可檢視檔案內容。
| 路徑 | 大小 | 類型 |
|---|---|---|
| references/gaps.md | 5.3 KB | text/markdown |
| references/report.md | 6.2 KB | text/markdown |
| references/usage.md | 8.3 KB | text/markdown |
| SKILL.md | 4.4 KB | text/markdown |
來源與署名
來源：incident-io/skills位於plugins/incident-io/skills/extensions-review提交443f471
授權條款： 無授權條款
內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。
更多來自 incident-io/skills 的技能
Skill Authoring
incident-io
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.
Extensions
incident-io
Understand the extensions so that you can help a user configure and manage their incident.io agent estate. Use whenever you're working with incident.io plugins, skills, connectors or MCPs in any way ("I want to set up an incident plugin"), when someone new wants to give incident.io's agents their own knowledge and doesn't yet know the pieces, or when you need to understand the user's existing configuration before editing a plugin or skill.
Doctor
incident-io
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.
Architecture
incident-io
Answer questions about how the organisation builds, deploys, and runs its software — what a system is, where it runs, what it depends on, and the real names of things (cloud projects, clusters, namespaces, hostnames, buckets) — from architecture docs wherever they live. Use when asked "how does X run", "what is Y", "where does Z live", or when grounding a component before debugging it.