Extensions

作者 incident-io443f47164eda无许可证2 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

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.

仅含说明AI & Agents

仅公开文件列表。将技能安装到工作区后即可查看文件内容。

路径大小类型
references/choosing-a-mechanism.md4.5 KBtext/markdown
references/estate.md11 KBtext/markdown
references/extensions-product.md7.6 KBtext/markdown
references/scaffold.md6.3 KBtext/markdown
SKILL.md5.2 KBtext/markdown

来源与署名

来源:incident-io/skills位于plugins/incident-io/skills/extensions提交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.

待分类2今天更新

Extensions Review

incident-io

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.

待分类2今天更新

Doctor

incident-io

审查 incident.io 智能体资产(插件、技能与连接)的健康状况,并报告需要修复的内容,但不做任何更改。

DevOps & Cloud2今天更新

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.

Writing & Content2今天更新