Inspect every bundled file
Review scripts, references, templates, network calls, and generated outputs before installation.
Official source verified Jul 10, 2026
A skill is a folder containing a SKILL.md playbook and, when useful, scripts, references, or assets. The format is now supported across major agent products, making it a practical portability layer for repeatable work.
Monitored revision 38a2ff82958a
The formats are complementary. Keeping each one focused reduces repeated context and makes agent behavior easier to maintain.
A useful description helps the agent decide when the skill applies. The body should make the required inputs, steps, output, and final checks unambiguous.
---
name: release-check
description: Verify a release candidate before production deployment.
---
# Release check
## Required inputs
- Target environment and release identifier
- Approved acceptance criteria
## Workflow
1. Run the documented build and test commands.
2. Check migrations, environment changes, and rollback steps.
3. Verify the critical user journey end to end.
4. Report failures with evidence; do not deploy on a failed check.
## Output
- Decision: ready or blocked
- Evidence reviewed
- Failed checks and owners
- Known limitations
Skills may contain scripts and may direct an agent to use powerful tools. Portability does not imply safety or quality.
Review scripts, references, templates, network calls, and generated outputs before installation.
Confirm the skill asks only for the permissions and systems required by its stated workflow.
Use positive and negative prompts to verify when the skill loads and when it stays out of context.
Record required packages, CLIs, versions, environment variables, and operating-system assumptions.
Run representative cases and compare accuracy, correction time, and failures against the workflow without the skill.
Track source, license, maintainer, version, review date, and a process for updates or removal.