Incident.io

• Risk level: Low
• Analyzed: Feb 25, 2026, 2:03 AM
• Findings: 0
• Version: 1.0.0

Overview

The skill's requests and runtime instructions align with its stated purpose (managing incident.io via the REST API) and only ask for the single expected API key and common CLI tools (curl, jq).

This skill appears coherent, but follow best practices before installing: only provide a scoped API key with the minimum required permissions; avoid placing the key in shared or persistent environments; test in a staging/org sandbox if possible; verify the API base URL (api.incident.io) and the documentation link in SKILL.md; and consider whether you want to allow autonomous agent invocation to perform incident operations automatically or restrict it to manual use. Note: the registry metadata lists no homepage/source, though the SKILL.md references the official API docs — if provenance matters to you, confirm the skill's author/source before trusting it with production credentials.