Skill IO Contract
When to Use
Use this skill when preparing, reviewing, or releasing an agent skill and you need proof that the skill states its input and output contract clearly.
Required Inputs
- Path to a
SKILL.mdfile. - Optional JSON fixture file containing example cases.
- Optional output path for the generated Markdown report.
Outputs
- A Markdown report containing a pass/fail result and check score.
- An optional report file when
--reportis provided.
Side-Effect Boundaries
This skill is read-only for source artifacts. It may write a report file only when the user or automation explicitly provides --report.
Approval Requirements
Unqualified writes; package publishing, repository pushes, messages, and use, uses, or using wording for live connectors; and create, update, edit, delete, or remove actions on clearly external resources (including GitHub releases or artifacts, repository issues, pull requests, and external accounts) require explicit approval in fixture contracts. Explicitly local report/file writes and read-only external actions do not require approval metadata, but a local-write clause does not exempt another external or unqualified write in the same description. This checker only reports those boundaries; taking an external action is outside the skill.
Examples
skill-io-contract check --skill SKILL.md --fixtures fixtures/cases.json
skill-io-contract check --skill ../my-skill/SKILL.md --report io-contract.md
Validation Workflow
Run npm test, npm run check, and npm run smoke. Attach the generated report to the release-candidate PR.