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.
添加到 SourceWeft 工作区
- 在控制台中打开该技能，并将它添加到工作区。
- 为需要使用它的对话启用该技能。
该技能仅含说明：不附带任何可执行的脚本。
添加到 SourceWeft系统会先要求你登录，然后直接带你回到这个技能。
让你的智能体来安装
把这段提示词粘贴到 Claude Code、Codex、Cursor 或其他能运行命令的智能体中，也可以粘贴到 SourceWeft 对话里。智能体会阅读这个技能的安装说明，向你展示它的来源、许可证和脚本情况，在你同意后用 SourceWeft CLI 安装。
阅读 https://sourceweft.com/skills/gh-incident-io-skills-extensions-review/install.md 中的说明，按说明安装这个技能。安装前先告诉我它的来源、许可证以及是否附带脚本，等我确认。修改我电脑上的其他任何内容之前也要先问我。用命令行自行安装
适用于 Claude Code、Codex、Cursor 及其他本地智能体。SourceWeft CLI 会从源代码仓库中获取此处扫描过的那次提交，并根据扫描时记录的哈希值逐一校验每个文件。只要有任何不一致，就不会写入任何内容。
npx @sourceweft/cli skills install gh-incident-io-skills-extensions-review添加 --agent claude-code、codex、cursor 或 universal 来选择安装给哪个智能体（默认为 Claude Code）。
上游安装器——未经 SourceWeft 校验
开源的 skills 安装器会获取同一个固定的提交，但不会根据 SourceWeft 记录的哈希值校验文件。
npx skills add https://github.com/incident-io/skills/tree/443f47164eda1f93108ebd908843925f681954ef/plugins/incident-io/skills/extensions-review来源与署名
来源：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.