SkillAgentSearch skills...

nw-por-review-criteria

Review dimensions and bug patterns for journey artifact reviews

Install / Use

npx skills add nWave-ai/nWave --skill nw-por-review-criteria

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Supported Platforms

Universal

Our assessment of nw-por-review-criteria

nw-por-review-criteria scores 84/100 on our quality scale, 2977th of 4,702 Development & Engineering skills we index.

Its SKILL.md is 4.7 KB long, well organised into 14 sections with 5 code examples: a solid amount of guidance for an agent.

It has 617 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so nw-por-review-criteria is actively maintained.
  • Our last check on 2026-11-06 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-09. Automated pattern scan on 2026-10-09. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nw-por-review-criteria compared with similar skills

All 4 of these similar skills score higher than nw-por-review-criteria; compare them before choosing.

SkillScoreStarsUpdatedFormat
nw-por-review-criteria (this skill)by nWave-ai846172mo agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
lobehubby lobehub10085.7ktodayMCP Server

Frequently asked questions

How do I install nw-por-review-criteria?
Run npx skills add nWave-ai/nWave --skill nw-por-review-criteria. The install tabs above show the steps for each supported agent.
Which AI agents does nw-por-review-criteria work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is nw-por-review-criteria safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is nw-por-review-criteria still maintained?
The repository was last updated about 2 months ago, so nw-por-review-criteria is actively maintained.

name: nw-por-review-criteria description: Review dimensions and bug patterns for journey artifact reviews user-invocable: false disable-model-invocation: true

Review Criteria Skill

Domain knowledge for product-owner-reviewer (Eclipse). Covers journey coherence, emotional arcs, shared artifacts, example data quality, CLI UX patterns.

Review Dimensions

Journey Coherence

Validate complete flow with no gaps.

Checks: all steps start-to-goal defined | no orphan steps | no dead ends | decision branches lead somewhere | error paths guide to recovery

Severity: critical = missing main flow steps / dead ends | high = orphan steps | medium = ambiguous decisions | low = minor clarity

Emotional Arc

Validate emotional design quality.

Checks: arc defined (start/middle/end) | all steps annotated | no jarring transitions | confidence builds progressively | error states guide not frustrate

Severity: critical = no arc / major jarring transitions | high = missing key annotations | medium = confidence doesn't build | low = minor polish

Shared Artifact Tracking

Validate ${variable} sources and consistency.

Checks: all ${variables} have documented source | single source of truth | all consumers listed | integration risks assessed | validation methods specified

Severity: critical = undocumented ${variables} / multiple sources | high = missing consumers / unassessed risks | medium = incomplete validation | low = minor consumer docs

Example Data Quality

Key review skill -- analyze data for integration gaps.

Checks: realistic not generic | reveals integration dependencies | catches version mismatches | catches path inconsistencies | consistent across steps

Severity: critical = generic placeholders hide issues | high = inconsistent across steps | medium = doesn't reveal deps | low = could be more realistic

Apply: 1) trace ${version} through all steps -- same? 2) compare ${install_path} step 2 vs 3 -- match? 3) does data show actual integration points?

Generic "v1.0.0" or "/path/to/install" hides bugs. Realistic "v1.2.86" from "pyproject.toml" reveals bugs.

CLI UX Patterns

Checks: command vocabulary consistent | help available | error messages guide to resolution | progressive disclosure respected

Severity: critical = inconsistent commands | high = no error recovery guidance | medium = missing progressive disclosure | low = minor vocabulary

Four Bug Patterns

Pattern 1: Version Mismatch

Multiple version sources. Trace ${version} through all steps -- same source?

Step 1: v${version} from pyproject.toml
Step 2: v${version} from version.txt  <-- MISMATCH

Pattern 2: Hardcoded URLs

URLs without canonical source. For each URL: "where is this defined?"

Install: git+https://github.com/org/repo
<-- Where is this URL canonically defined?

Pattern 3: Path Inconsistency

Paths from different sources. Trace ${path} -- same source?

Install to: ${install_path} from config
Uninstall from: ~/.claude/agents/nw/  <-- HARDCODED

Pattern 4: Missing Commands

CLI commands without slash equivalents. Check both contexts exist.

Terminal: crafter run
Claude Code: /nw-execute  <-- EXISTS?

Review Output Schema

review_id: "{timestamp}"
reviewer: "nw-product-owner-reviewer (Eclipse)"
artifact_reviewed: "{file path}"

strengths:
  - strength: "{Positive aspect}"
    example: "{Specific evidence}"

issues_identified:
  journey_coherence:
    - issue: "{Description}"
      severity: "critical|high|medium|low"
      location: "{Where}"
      recommendation: "{Fix}"
  emotional_arc:
    - issue: "{Description}"
      severity: "critical|high|medium|low"
      location: "{Where}"
      recommendation: "{Fix}"
  shared_artifacts:
    - issue: "{Description}"
      severity: "critical|high|medium|low"
      artifact: "{Which ${variable}}"
      recommendation: "{Fix}"
  example_data:
    - issue: "{Description}"
      severity: "critical|high|medium|low"
      data_point: "{Which data}"
      integration_risk: "{What bug it might hide}"
      recommendation: "{Fix}"
  bug_patterns_detected:
    - pattern: "version_mismatch|hardcoded_url|path_inconsistency|missing_command"
      severity: "critical|high"
      evidence: "{Finding}"
      recommendation: "{Fix}"

recommendations:
  critical: ["{Must fix before approval}"]
  high: ["{Should fix before approval}"]
  medium: ["{Fix in next iteration}"]
  low: ["{Consider for polish}"]

approval_status: "approved|rejected_pending_revisions|conditionally_approved"
approval_conditions: "{If conditional, what must be done}"

Approval Criteria

  • approved: No critical, no high issues
  • conditionally_approved: No critical, some high addressable quickly
  • rejected_pending_revisions: Critical issues exist, or multiple high

Related Skills

View on GitHub
GitHub Stars617
CategoryDevelopment
Updated2mo ago
Forks63

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions