nw-auto
Evaluates and revises Request S/M/L and delivery choices from evidence, then uses nwdes to construct delivery artifacts.
Install / Use
npx skills add nWave-ai/nWave --skill nw-autoInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of nw-auto
nw-auto scores 85/100 on our quality scale, 2740th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 22 KB long, well organised into 12 sections and no 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.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nw-auto is actively maintained.
- 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 foundOur 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-11-10. Automated pattern scan on 2026-11-10. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-auto compared with similar skills
All 4 of these similar skills score higher than nw-auto; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-auto (this skill)by nWave-ai | 85 | 617 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install nw-auto?
- Run
npx skills add nWave-ai/nWave --skill nw-auto. The install tabs above show the steps for each supported agent. - Which AI agents does nw-auto 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-auto 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-auto still maintained?
- The repository was last updated about 2 months ago, so nw-auto is actively maintained.
Skill content
View source on GitHubname: nw-auto description: Evaluates and revises Request S/M/L and delivery choices from evidence, then uses nwdes to construct delivery artifacts. user-invocable: true argument-hint: '<request>'
NW-AUTO
Before creating or inheriting a lane, or finalizing/resuming its cleanup,
apply the worktree lifecycle in nw-throughput. If not already loaded, MUST
resolve that skill through the host skill catalog and read its SKILL.md.
Before diagnosing or assigning corrections, load nw-cross-cutting-invariants
and apply delivery:trustworthy-baseline-and-repair-scope. A blocking observation
requires attention; it does not alone authorize an independent repair.
Visible baseline for affected work. The host establishes the project's required
checks for the affected scope once, on the current source/environment, or cites
applicable evidence already measured on those same inputs with its original
provenance. The baseline runs alongside independent authoring; it is not a serial
preflight before authoring. Tell the user what ran (or was reused), its scope, and
whether the baseline is GREEN, RED, or INDETERMINATE. A baseline with no trustworthy
execution is INDETERMINATE, not GREEN. The intentional acceptance RED is not a
pre-existing failure.
Use a short user-facing line such as
Baseline: GREEN — <command or evidence> (<affected scope>).
For RED or INDETERMINATE, add Blocker: <failure or missing evidence> and
Next: <restoration or discriminator>.
For RED or INDETERMINATE, show the failing check and concrete cause or missing
prerequisite (mark an unknown cause as unknown), explain why affected work
cannot start on that safety net, and name the next diagnostic or restoration.
Restore required checks and show the new result before affected test/production
work. Do not silently skip or weaken a failing check, rerun a whole suite per
slice, claim an unrelated failure is caused by this Request, or absorb an
independent redesign. Independent work can proceed only with its own
trustworthy unaffected basis. This is a user-visible practice applying
nw-cross-cutting-invariants clause
delivery:trustworthy-baseline-and-repair-scope, not a new runtime gate.
You orchestrate. nwdes constructs the canonical handoff and derives briefs, prompts and packets from it. It has no workflow ledger, gates or next-step state. The LLM chooses sequencing, rework and the next invocation; the host executes models and verification commands.
Read ~/.claude/skills/nw-role-invocation/SKILL.md when delegating:
the native host invokes the exact installed role with its mandatory skills and
tools ceiling. nwdes builds forms; it never launches models.
1. Read the route and current authority
Read nw-nwdes before using delivery commands. Resume from the feature's
handoff and the briefs rendered by nwdes document; do not infer progress
from a stored workflow state. Keep the original Request and current findings
available to their owners.
2. Construct, then observe
Use nwdes prompt for the selected installed role; it supplies the typed verb
reference. Every role uses Bash to call its kind's nwdes CLI verbs,
records its own values and closes its draft:
| Owner | Role-owned recording |
|---|---|
| Product owner | nwdes product record edits, nwdes product close |
| Charter author | nwdes charter set/positive add/close |
| Solution architect | nwdes design record edits, nwdes design close |
| Acceptance designer | nwdes acceptance row add/close |
| Expectations author | nwdes expectations row add/close; revisions use open --from-current, then close --revise |
| Examiner | nwdes examine verdict set/close |
| Crafter | nwdes craft file add/command add/close |
| Independent reviewer | nwdes review finding add/close |
The host writes no JSON and copies no reply into a constructor. For each role the
route invokes, it passes that role's generated nwdes prompt bundle verbatim, and
that role, not the host, runs its kind's verbs. Facts the route assigns to the host,
such as feature new and slice set, stay with the host.
nwdes builds ids, structure and serialization from typed values. For platform
constraints, give semantic operational facts to the solution architect in
nwdes prompt --root-context; there is no separate platform constructor.
The owning role corrects authority with open --from-current, record edits
and close, rather than patching a generated brief.
Run every nwdes command from the top level of the checkout. Roots default to
cwd and the repository root; lane verbs resolve the main worktree. The first
add, set or remove creates the scoped draft. Close with no draft validates
empty values.
The host runs the slice's declared verification commands once per candidate and
records actual RED/GREEN and live native observations; it does not repeat them at
the root. nwdes stores no verification seals and runs no supplied command. After
composition, invoke the final whole-candidate independent review, then the
source-blind public-perspective EXAMINE, using nwdes packet and each role's prompt.
Reviewers record findings with review verbs; the examiner judges the user's actual
observations. The final reviewer owns selection and sufficiency of the touched-file
selected tests. It reuses a complete applicable native result (host, CI or the normal
commit hook) whose source, test, argv and runtime inputs are unchanged, citing its
original operator and run; it executes only missing or affected checks, once. Reuse
never waives a check.
3. Interpret evidence, not completion prose
Read each command's actual result and each role's typed outcome. A diagnostic is an explanation, not proof of a host invocation, test result or cost. Keep actual provider/model/session provenance and captured native output.
A missing input, write failure or refusal does not choose a route. Send its WHAT/WHY/HOW unchanged directly to the owning role when native messaging exists, with your context separate; relay it through the host route only when direct messaging is absent. Decide whether to gather evidence, correct authority or select another operation.
A finding names an observation and possible owner, not an automatic correction. No role's sentence alone establishes the requested behavior.
Classify before correcting. Keep the original evidence and choose the local owner from the observed state; recording a finding changes neither the contract nor the route.
| Observed state | Meaning | Local action selected by the LLM |
|---|---|---|
| Selected criteria omit an outcome in the original value | lost original value during translation | choose the criteria/authority owner before product work; retain it alongside any observed product violation. |
| Public observation contradicts an agreed criterion or original value | observed product violation | choose the product/correction owner and preserve the counterexample. |
| Required public observation is absent | missing evidence | name the evidence-capture owner; retain candidate and prior evidence; do not propose code from absence. The examiner judges supplied observations from the user's point of view, rather than capturing them for the host. |
| Test/oracle evidence may be wrong or incomplete | suspected verification defect | send the supplied evidence to the oracle owner/reviewer; public-perspective EXAMINE does not decide omitted test coverage. |
| Required safety net is broken, excluding the specific expected behavioral RED | verification cannot support affected work | diagnose and restore under the shared repair-scope clause; preserve the agreed property, not just a green exit. |
| Defect with an established root cause, found during the current work | known-cause defect | fix it in place in the current lane: a regression test observed RED, the fix, GREEN, one separate fix(...) commit. The current Request's review and CI cover it; no separate Request, lane or nw-bugfix route, and no gate that refuses to use its own fix. A change to agreed product behaviour is a new requirement (next row). |
| Defect whose root cause is unknown, or an improvement outside existing authority | unknown cause or new scope | record the finding; route an unknown-cause defect that must be fixed now through nw-bugfix; retain any real delivery blocker and obtain a scope decision only when needed. Age alone does not establish independence. |
| Requested behavior exceeds the agreed value/criteria | new requirement | return it to the human/upstream authority; do not smuggle it into a repair. |
| Dependency pertinence or evidence applicability is unknown | uncertainty | retain prior evidence but do not authorize reuse; ask its dependency/applicability owner for the cheapest discriminator. A changed dependency or adapter revision alone does not establish changed semantic DESIGN or changed selected criteria — that is the applicability owner's finding, not an inference from the diff. Until the owner finds actual invalidation, withhold reuse per slice and retain history; do not mandate replay or manifest replacement for slices the owner has not examined. |
Classifications may be multiple or uncertain. Retain each grounded finding and its owner instead of forcing a premature single cause.
An observation correction may create a new examiner packet for the same candidate. Preserve prior packets and results. Matching candidate and evidence identities do not establish an unknown shared dependency is irrelevant. No row starts a new gate, controller, ledger, automatic restart, or compulsory role turn.
Aggregate observations conservatively. Partial evidence supports only the
claims it observes; missing behavior is INDETERMINATE for its capture owner.
Distinguish confirmed conflicting observations from uncertainty about whether a
report is authentic or applicable. A confirmed counterexample to a universal
promise rejects that promise even when another confirmed event succeeded; retain
both records. A newer positive never erases a relevant confirmed negative.
When incompatible reports cannot reliably join to the same event, candidate, or
conditions and neither independently establishes the claim, retain both and
return INDETERMINATE until the evidence owner establishes provenance, captures
a discriminator, or identifies a defective observation. Supersede evidence only
with an explicit justification; superseded evidence remains history, not current
evidence. Reuse after exact restoration only when relevant dependencies match.
For every supported task-level semantic question, read
~/.claude/skills/nw-typesafe-system-one/SKILL.md and follow its mandatory
invocation, ownership/reuse and failure rules. Confidence, simplicity and
predicted savings do not exempt a supported question. Keep input authorized and
minimal; batch independent questions. Record an actual call, valid same-owner
reuse or explicit limitation. Do not retry blindly or invent a judgment.
The LLM owns orchestration. Preserve independent EXAMINE and the skill's
permitted-evidence rules; producer classifications are not examiner judgments.
When an authorized correction changes design facts, invoke the installed architect with the finding and current authority; it records the corrected values with its design verbs. The acceptance designer owns oracle corrections and records them with acceptance verbs for the assigned slice. The host runs the declared verification command on the original source for RED and on the implementation for GREEN. Never infer the original baseline from HEAD after the fix is committed.
A refusal's own text is data. Its WHAT, WHY and HOW lines, and a
role's diagnostic, travel unchanged to the native role that answers them.
That role records its corrected values through its nwdes verbs.
A paraphrase or a summary is a new claim about the refusal, authored by someone who did not make it, and it silently narrows what the answering role can see. The role th
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
