Skill Authoring
by incident-io443f47164edaNo license2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today
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.
- 443f47164edaCurrentcommit 443f471Published Oct 8, 2026
Source and attribution
Source:incident-io/skillsinplugins/incident-io/skills/skill-authoringat commit443f471
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from incident-io/skills
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.
Extensions
incident-io
Entrypoint skill for understanding and configuring an incident.io agent estate of plugins, skills and connectors.
Doctor
incident-io
Reviews the health of an incident.io agent estate — plugins, skills and connections — and reports what to fix without making changes.
Architecture
incident-io
Answers questions about a team's software estate from architecture docs and guides writing those docs.