SkillAgentSearch skills...

nw-rigor

Configure explicit Codex or Claude model facts for nWave defaults or published roles, consumed by the native host where supported. Never derives a model from a competence label.

Install / Use

npx skills add nWave-ai/nWave --skill nw-rigor

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Claude Code
OpenAI Codex

Tags

Our assessment of nw-rigor

nw-rigor scores 92/100 on our quality scale, 117th of 319 Customer Support skills we index (top 37%).

Its SKILL.md is 19 KB long, well organised into 40 sections with 23 code examples: a thorough specification that gives an agent plenty to work with.

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

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

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so nw-rigor is actively maintained.
  • Our last check on 2026-10-28 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-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

nw-rigor compared with similar skills

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

SkillScoreStarsUpdatedFormat
nw-rigor (this skill)by nWave-ai926172mo agoSKILL.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install nw-rigor?
Run npx skills add nWave-ai/nWave --skill nw-rigor. The install tabs above show the steps for each supported agent.
Which AI agents does nw-rigor work with?
It is written for Claude Code and OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
Is nw-rigor 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-rigor still maintained?
The repository was last updated about 2 months ago, so nw-rigor is actively maintained.

name: nw-rigor description: "Selects a quality-vs-token-consumption profile (lean, standard, thorough, exhaustive, custom, inherit) and persists it globally (~/.nwave/global-config.json) or per-project (.nwave/des-config.json). Use when tuning how much rigor wave commands apply." user-invocable: false argument-hint: '[profile] - Optional: lean, standard, thorough, exhaustive, custom, inherit. Omit for interactive selection.'

NW-RIGOR: Quality Profile Selection

Wave: CROSS_WAVE | Agent: Main Instance (self) | Command: /nw-rigor [profile]

Overview

Interactive command to select a quality-vs-token-consumption profile. Persists choice to either ~/.nwave/global-config.json (global scope) or .nwave/des-config.json (project scope) under the rigor key. All wave commands read this config to adjust agent models, review policy, TDD phases, and mutation testing.

You (the main Claude instance) run this directly. No subagent delegation.

Note on TDD phase canons (dual-canon, ADR-025, 2026-05-07): the canonical TDD cycle is 3-phase v5 (RED, GREEN, COMMIT) as described in nw-tdd-methodology. The legacy 5-phase v4 (PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT) is preserved for backward-compat audit-log replay of pre-2026-05-07 commits. The .nwave/des-config.json tdd_phases field accepts BOTH canons: writers of new logs may emit v5; the validator + schema (step-tdd-cycle-schema.json) dispatch on schema_version ("5.0" → canonical, anything else → legacy). The profile table below shows both canons side-by-side: pick v5 for new features, keep v4 only when extending a feature whose audit log was started under the legacy canon.

Profile Mappings (Single Source of Truth)

| Setting | lean | standard [recommended] | thorough | exhaustive | inherit | |--------------------|---------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------|------------------------------------------------------------------------------| | agent_model | haiku | sonnet | opus | opus | inherit | | reviewer_model | skip | haiku | sonnet | opus | haiku | | review_enabled | false | true | true | true | true | | double_review | false | false | true | true | false | | tdd_phases (v5 canonical, ADR-025) | [RED, GREEN] | [RED, GREEN, COMMIT] | [RED, GREEN, COMMIT] | [RED, GREEN, COMMIT] | [RED, GREEN, COMMIT] | | tdd_phases (v4 legacy, audit-replay) | [RED_UNIT, GREEN] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | [PREPARE, RED_ACCEPTANCE, RED_UNIT, GREEN, COMMIT] | | refactor_pass | false | true | true | true | true | | mutation_enabled | false | false | false | true | false |

Behavior Flow

Mode Detection

  • No argument -> Mode 1 (Interactive Selection)
  • Argument is a preset name (lean, standard, thorough, exhaustive, inherit) -> Mode 2 (Quick Switch)
  • Argument is custom -> Mode 3 (Custom Builder)

Mode 1: Interactive Selection (no argument)

Step 1: Welcome

Read .nwave/des-config.json. If missing or .nwave/ directory absent -> error: "No nWave config directory found. Run nwave install first."

If JSON is invalid -> backup as .nwave/des-config.json.bak, reset config to {}, note: "Config was corrupted. Backed up and reset."

Display current profile (from config.rigor.profile) or "none set" if absent.

Brief explanation: "Rigor profiles control how much quality infrastructure nWave applies per wave: agent models, review depth, TDD phases, mutation testing. Higher rigor = better guarantees, higher token cost."

Step 1.5: Scope Selection

Display the current project rigor (from .nwave/des-config.json) and current global rigor (from ~/.nwave/global-config.json, if it exists).

Ask via AskUserQuestion:

Where do you want to save this configuration?

Options:

  1. Globally (~/.nwave/global-config.json) — applies to all projects without their own rigor
  2. This project only (.nwave/des-config.json) — overrides global for this project

Store the user's choice as {scope} and the corresponding file path as {target_file}:

  • If global: {target_file} = ~/.nwave/global-config.json
  • If project: {target_file} = .nwave/des-config.json

Step 2: Comparison Table

Display this table:

+-----------+--------+----------+----------+------------+---------+
|           | lean   | standard | thorough | exhaustive | inherit |
+-----------+--------+----------+----------+------------+---------+
| Agent     | haiku  | sonnet   | opus     | opus       | *yours* |
| Reviewer  | --     | haiku    | sonnet   | opus       | haiku   |
| Review    | no     | yes      | double   | double     | yes     |
| TDD       | R->G   | 5-phase  | 5-phase  | 5-phase    | 5-phase |
| Refactor  | no     | yes      | yes      | yes        | yes     |
| Mutation  | no     | no       | no       | yes        | no      |
+-----------+--------+----------+----------+------------+---------+
| Est. cost | lowest | moderate | higher   | highest    | varies  |
| Est. time | fast   | moderate | slower   | slowest    | varies  |
+-----------+--------+----------+----------+------------+---------+

Mark "standard" as [recommended]. Below the table, note: "Or choose custom to configure each setting individually. Type inherit to use your current session model."

Step 3: User Selection

Ask user to select via AskUserQuestion (4 options + Other for inherit/custom):

  1. standard [recommended]
  2. lean
  3. thorough
  4. exhaustive

Note in the question text: "Type 'custom' to build your own profile, or 'inherit' to use your session model."

If user selects or types "custom" -> jump to Mode 3 (Custom Builder). If user types "inherit" -> proceed with inherit profile to Step 4.

Step 4: Detail View

Show the detail view for the selected profile. Render in a code block for visual clarity.

lean:

WHAT YOU GET:
  - Haiku agent (fastest, cheapest)
  - RED -> GREEN TDD (skip PREPARE, RED_ACCEPTANCE, COMMIT phases)

WHAT YOU LOSE:
  - No code review
  - No PREPARE phase (no test fixture setup)
  - No RED_ACCEPTANCE phase (no acceptance tests)
  - No COMMIT phase (no refactoring pass)
  - No mutation testing

WHEN TO USE:
  Config changes, documentation, simple bug fixes, spikes/prototypes

ESTIMATED IMPACT:
  Lowest token cost | Fastest per step

standard [recommended]:

WHAT YOU GET:
  - Sonnet agent (balanced quality/speed)
  - Full 5-phase TDD (PREPARE -> RED_ACCEPTANCE -> RED_UNIT -> GREEN -> COMMIT)
  - Haiku reviewer (cost-effective review)
  - Refactoring pass in COMMIT phase

WHAT'S NOT INCLUDED:
  - No double review (single pass only)
  - No mutation testing
  - Not opus-level reasoning

WHEN TO USE:
  Most development work — features, integrations, refactoring

ESTIMATED IMPACT:
  Moderate token cost | Moderate time per step

thorough:

WHAT YOU GET:
  - Opus agent (strongest reasoning)
  - Sonnet reviewer (deeper review analysis)
  - Double review (two independent review passes)
  - Full 5-phase TDD
  - Refactoring pass

WHAT IT COSTS:
  Higher token cost | Slower per step

WHEN TO USE:
  Critical features, security-sensitive code, public APIs, complex algorithms

exhaustive:

WHAT YOU GET:
  - Opus agent and opus reviewer (strongest at every stage)
  - Double review (two independent review passes)
  - Full 5-phase TDD
  - Refactoring pass
  - Mutation testing (>= 80% kill rate gate)

WHAT IT COSTS:
  Highest token cost | Slowest per step

WHEN TO USE:
  Critical production systems, compliance-sensitive code, long-lived core modules

inherit:

WHAT YOU GET:
  - Your session model for agents (nWave inherits, does not override)
  - Haiku reviewer
  - Full 5-phase TDD
  - Single review pass
  - Refactoring pass

WHAT THIS MEANS:
  nWave respects your model choice and controls the process around it.
  If your session runs opus, agents get opus. If sonnet, agents get sonnet.

WHEN TO USE:
  When you have strong opinions about which model to use,
  or your organization controls model selection externally.

Step 5: Confirm

Ask user to confirm via AskUserQuestion:

  1. Yes, apply this profile
  2. No, go back to selection (return to Step 2)
  3. Cancel (exit without saving)

Step 6: Save to Config

  1. If {scope} is global AND the directory ~/.nwave/ does not exist, create it with parents=True
  2. Read {target_file} (handle missing file or corrupt JSON: start with {})
  3. Parse JSON
  4. Set config["rigor"] to the full profile object:
    {
      "profile": "{selected}",
      "agent_model": "...",
      "reviewer_model": "...",
      "tdd_phases": [...],
      "review_enabled": true/false,
      "double_review": true/false,
      "mutation_enabled": true/false,
      "refactor_pass": true/false
    }
    
  5. Write back to {target_file}, preserving all other top-level keys (audit_logging_enabled, skill_tracking, update_check, etc.)

Step 7: Summary

Display all resolved settings:

Rigor profile saved: {name}

  Resolved settings:
  +-----------------------+---------------------------------

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars617
CategoryCustomer
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