| name | agent-skills-review |
| description | Review SKILL.md quality for Waza readiness and agent-skills-instructions compliance. Use when evaluating SKILL.md quality, checking compliance with skill authoring standards, preparing skills for release, reviewing skill PRs, or running waza readiness checks. |
| license | Apache-2.0 |
| metadata | {"author":"y-miyazaki","version":"1.0.6"} |
Input
- Target:
<agent-root>/skills/*/SKILL.md
- Evidence:
scripts/validate_waza.sh and scripts/validate.sh outputs
Output Specification
Execution Scope
- Run validation scripts and parse results to assess SKILL.md quality against S-, Q-, P-, and BP- checks.
- Check
waza check token output; when SKILL.md exceeds 500 tokens, add Q-09 advisory in ## Issues (not a Failed row unless sibling consistency was violated).
- Do not merge PRs or edit unrelated files.
- Do not review product runtime behavior or application business logic.
USE FOR:
- review new SKILL drafts before release
- note token budget advisories when
waza check exceeds 500 tokens (secondary to sibling consistency)
- fix SKILL spec compliance findings in PR reviews
- apply DIST-01 / S-07 portability when the target skill is intended for reuse outside the authoring repository (redistributed skill tree, shared package, or equivalent)
Portability scope: DIST-01 and S-07 judge whether skill text and links still work when the skill is installed or copied into a different repository. Defer S-07 for local-only skills that live under <agent-root>/skills/ and are not redistributed — run structural and quality checks (S-01, Q-, P-) only. Report DIST-01 violations in ## Issues for reuse-intended targets. Checklist neutrality in references/ is defined in companion agent-skills instructions (DIST-01 Scope), not as a universal rule for every skill tree.
DO NOT USE FOR:
- implement product features
- debug product runtime failures unrelated to SKILL quality checks
- run benchmark content evaluations (
waza run eval.yaml) as a substitute for compliance checks
- modify or overwrite the target SKILL.md without explicit user approval (review output only; do not write or commit changes)
Reference Files Guide
Workflow
- Run
bash scripts/validate_waza.sh <skill-name> and bash scripts/validate.sh <SKILL.md> (CWD: <agent-root>/skills/agent-skills-review/).
- Record token budget from
waza check when present; if count > 500, add Q-09 advisory to ## Issues (do not Fail Q-09 on count alone).
- Apply checks in order:
S-* (structure), Q-* (quality language), P-* (workflow/policy), BP-* (best-practice rules).
- Report failed/deferred items with ItemIDs.
- If target
SKILL.md does not exist, return status: failed and stop without running other checks.
- If one validation script fails and the other succeeds, report successful checks normally and mark unresolved checks as deferred with script name and exit status.
- If both validation scripts fail, return
status: failed and include both commands, exit statuses, and stderr summaries.
Error Handling
| Condition | Severity | Action |
|---|
Target SKILL.md does not exist | Fatal | Return status: failed; stop without other checks |
validate_waza.sh or validate.sh missing | Fatal | Stop; report missing script path |
| One validation script fails, the other succeeds | Recoverable | Report successful checks; defer failed script checks with exit status |
| Both validation scripts fail | Fatal | Return status: failed with command, exit status, and stderr summary |
common-checklist.md unavailable | Fatal | Stop; report missing dependency |
common-output-format.md unavailable | Recoverable | Use inline output contract from Output Specification |
| Script output missing after one rerun | Recoverable | Defer affected checks; include command and stderr per troubleshooting |
Examples
- Prompt:
Review SKILL.md and report only failed/deferred items.
- Output skeleton:
## Checks Summary
- Total checks: <number>
- Passed: <count>
- Failed: <count>
- Deferred: <count>
## Checks (Failed/Deferred Only)
| ItemID | Status | Evidence | Fix |
| ------ | ------ | -------- | --- |
## Issues
1. <ItemID>: <ItemName>
- File: <path>#L<line>
- Problem: <specific issue>
- Impact: <scope and severity>
- Recommendation: <specific fix>