nwave-ai/nw-review-workflow
nWave/skills/nw-review-workflow/SKILL.md
Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews
$ install --global
skillsauthnpx skillsauth add nwave-ai/nwave nw-review-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:41 PM2.1s1 file scanned
SKILL.md
- name:
- nw-review-workflow
- description:
- Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews
- user-invocable:
- false
- disable-model-invocation:
- true
Agent Review Workflow
V2 Validation Checklist (11 Points)
Run against every agent under review. Each item pass/fail.
- Frontmatter format:
---delimited YAML withnameanddescription - Size compliance: Under 400 lines; domain knowledge in Skills
- Divergence-only: Only behaviors diverging from Claude defaults
- Calm language: No "CRITICAL", "MANDATORY", "ABSOLUTE"
- Examples present: 3-5 canonical for critical/subtle behaviors
- Least privilege tools: Minimum needed in frontmatter
- maxTurns set: Present in frontmatter
- Platform safety: Via frontmatter/hooks, not prose
- Affirmative phrasing: "Do X" not "Don't do Y"
- Consistent terminology: One term per concept
- Clear delegation: Description states when to delegate
Scoring Methodology
Per-Dimension Scoring
For each of 7 critique dimensions (from critique-dimensions skill):
- Pass: All checks satisfied
- Fail: One or more checks not satisfied
Verdict Logic
IF any high-severity dimension fails:
verdict = "revisions_needed"
ELIF count(medium-severity failures) >= 3:
verdict = "revisions_needed"
ELSE:
verdict = "approved"
High-severity: template_compliance, size_and_focus, safety_implementation, priority_validation Medium-severity: divergence_quality, language_and_tone, examples_quality
Evidence Requirements
Every finding includes: Dimension (which of 7) | Severity (high/medium/low) | Finding (observed, with line numbers/counts) | Recommendation (specific fix action)
Common V1 to V2 Migration Issues
| Residual Pattern | What to Flag |
|-----------------|-------------|
| Embedded YAML config blocks | Should be frontmatter or removed |
| activation-instructions section | Remove -- Claude Code handles activation |
| IDE-FILE-RESOLUTION section | Remove -- not needed in v2 |
| commands with 10+ entries | Reduce to 3-5 focused |
| Inline embed_knowledge | Extract to Skills |
| 5+ "production frameworks" | Remove -- platform handles safety |
| CRITICAL: prefixed instructions | Rephrase as calm direct statements |
| Python/YAML safety code examples | Remove -- aspirational, not executable |
Peer Review Protocol
- Receive agent file path from builder
- Execute full dimension review
- Return structured YAML verdict
- If
revisions_needed, include prioritized fix list - Builder revises and resubmits (max 2 iterations)
- On second rejection, escalate to user
Command Template Review
Additional checks for nWave command files (tasks):
- Size: 50-60 lines target; >60 warning, >150 major, >500 blocker
- Structure: agent activation metadata, context files section, success criteria
- Delegation: business logic belongs in agent, not command
- No embedded procedural steps (STEP 1, STEP 2)
Related Skills
nwave-ai/nw-distill
testing
VerifiedTrustedCommunity
Acceptance test creation methodology for the DISTILL wave. Domain knowledge for the acceptance designer agent: port-to-port principle, prior wave reading, wave-decision reconciliation, graceful degradation, and document back-propagation.
504SKILL.mdUpdated May 21, 2026
nwave-ai/nw-test-optimization
testing
VerifiedTrustedCommunity
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
504SKILL.mdUpdated May 5, 2026
nwave-ai/nw-test-optimization
testing
VerifiedTrustedCommunity
Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation
504SKILL.mdUpdated May 5, 2026
nwave-ai/nw-test-design-mandates
development
VerifiedTrustedCommunity
Design mandates for acceptance tests - hexagonal boundary, business language abstraction, user journey completeness, pure function extraction, 3 Pillars (domain language / chained narrative / production composition), and the layered ATD discipline (Universe-bound assertion, layer-dependent PBT mode, two-tier acceptance, example-based sad paths)
504SKILL.mdUpdated Apr 16, 2026