Ask your agent
Manual lifecycle
1
Create the draft
2
Write representative tests
Include requests that should activate the skill, nearby requests that
should not, and at least one realistic end-to-end task.
3
Verify the package
--no-auto-fix when
you want verification to report missing artifacts without creating them.4
Review before distribution
Confirm the package contents, permissions, external tools, failure modes,
and validation report. Publishing or global installation requires a
separate approval.
Success criteria
- The description states both capability and activation conditions.
- Instructions define the result, important constraints, and failure behavior.
- Positive, negative, and realistic tasks are represented.
- Verification identifies the exact skill version it tested.
- The package remains local until you approve publication or installation.