SkillAgentSearch skills...

nw-role-invocation

KNOWLEDGE — how a wave entrypoint invokes its specialist: the real installed role definition, never a generic persona. Load when a wave delegates to a role.

Install / Use

npx skills add nWave-ai/nWave --skill nw-role-invocation

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

88/100

Category

Automation

Supported Platforms

Universal

Tags

Our assessment of nw-role-invocation

nw-role-invocation scores 88/100 on our quality scale, 1573rd of 2,790 Automation skills we index.

Its SKILL.md is 15 KB long, well organised into 12 sections with 1 code example: 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
17/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-role-invocation 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 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-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-role-invocation compared with similar skills

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

SkillScoreStarsUpdatedFormat
nw-role-invocation (this skill)by nWave-ai886172mo agoSKILL.md
Agent-Reachby Panniantong100112.3k8d agoCLAUDE.md
rufloby ruvnet10081.9ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md
Scraplingby D4Vinci100103.6k2d agoMCP Server

Frequently asked questions

How do I install nw-role-invocation?
Run npx skills add nWave-ai/nWave --skill nw-role-invocation. The install tabs above show the steps for each supported agent.
Which AI agents does nw-role-invocation 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-role-invocation 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-role-invocation still maintained?
The repository was last updated about 2 months ago, so nw-role-invocation is actively maintained.

name: nw-role-invocation description: "KNOWLEDGE — how a wave entrypoint invokes its specialist: the real installed role definition, never a generic persona. Load when a wave delegates to a role." user-invocable: false disable-model-invocation: true

nw-role-invocation (KNOWLEDGE)

Reference for wave entrypoints. The LLM chooses waves and operations; nwdes constructs handoffs, briefs, prompts and packets without workflow state or progression.

Rule

Delegate to the exact installed role definition (nw-<role>), with its real instructions and mandatory frontmatter skills. Missing mandatory instructions stop delegation; never substitute a generic persona. Conditional skills load on the role's own triggers. The LLM/native host owns model execution, provider/model/effort selection and orchestration. nwdes never launches a model.

Load nw-cross-cutting-invariants and apply flow:findings-go-to-the-owner-directly, including its dispatch-task instruction for every relevant role.

Invocation forms

For native delegation, select the installed specialist in the host tool: Claude Agent(subagent_type="nw-solution-architect", prompt=...); Codex spawn_agent(agent_type="nw-solution-architect", message=...). Substitute the exact role below, and pass the bounded task and its evidence. Do not select a generic agent and replace its definition with persona prose. The host's native tool may be named Agent or Task; use whichever it supports to select the exact installed role, with only parameters it supports. The wave caller invokes the role; the role does the semantic work and records its values through its nwdes verbs. If native delegation cannot start it with its declared tools ceiling, use a supported native CLI invocation or report the missing capability. Never substitute a generic worker or grant extra tools.

Read nw-nwdes for the current role/task mapping. Build the exact role's task with nwdes prompt and pass its output verbatim. Put bounded host context in --root-context only for recipes that admit it; examine refuses it and both host observation flags before any read or effect.

| Need | Exact installed role | Role-owned recording | |---|---|---| | Product decomposition | nw-product-owner | nwdes product record edits, nwdes product close | | Expectation charter | nw-product-owner --task charter | nwdes charter set, charter positive add, charter close | | Solution architecture | nw-solution-architect | nwdes design record edits, nwdes design close | | Acceptance oracle | nw-acceptance-designer | nwdes acceptance row add, close; host observes declared RED | | Implementation | nw-software-crafter / nw-functional-software-crafter | nwdes craft file add, command add, close; host observes declared GREEN | | Independent review | nw-software-crafter-reviewer / nw-acceptance-designer-reviewer | Follow Review evidence in the generated subject/slice scope | | Expectations / EXAMINE | nw-user-examiner | nwdes expectations row add/close or nwdes examine verdict set/close | | Operational facts | nw-platform-architect | Give semantic operational facts to the solution architect, who records the design values |

The bound functional paradigm selects nw-functional-software-crafter; otherwise use the ordinary crafter. Do not infer a new paradigm from the launcher or host language.

Selected independent operational review

When the authorized DESIGN or DEVOPS task selects independent platform review, the native wave caller invokes nw-platform-architect-reviewer on the actual current operational authority, its bound facts, authorized scope and available observations. Use the existing native invocation form and the reviewer's declared ceiling; no producer judgment substitutes for its result.

This is caller-owned orchestration, not a new review-task payload or builder operation. Add no delegation/reviewer/result fields to the design payload. Consume the actual verdict and findings; required revisions or unresolved load-bearing evidence remain with the platform authority owner. A configured or human-authorized skip is skipped, never approved. Builder success does not establish review approval or authorize rollout.

Reuse adequate authority without a new producer turn; do not add a review for a no-op when none is selected. Missing exact-role invocation capability is explicit, never a generic substitute or invented result.

Role-owned recording

nwdes prompt includes the generated verb reference for the selected role. Every recording invocation names its kind and scope. The role records semantic values with typed add/set/remove flags; the first such call creates the scoped draft. It then calls close --outcome ... --diagnostic .... nwdes constructs ids, structure, paths and serialization. The host passes no envelope and copies no reply into another command. The prompt binds repository, feature and applicable slice scope. Use the generated reference for required selectors; keep the same scope throughout the draft. Slash-separated verb lists describe separate calls, not one command. 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. Close with no draft validates empty values.

Every role, including the Product Owner and examiner, records through the nwdes CLI using Bash. They work from the user's point of view and have no need to inspect code; this is a task focus, not a code-access prohibition. The host supplies the generated prompt, not a substitute recording channel.

For an authority correction, the owning role uses open --from-current, edits the retained records and closes again. A close refusal retains the draft and leaves authority unchanged. Give the refusal's WHAT/WHY/HOW unchanged to that role, or fulfill its named host-owned prerequisite and rebuild the prompt if inputs changed. The host does not repair serialization or write the role's record.

For craft, record files with file add --path L --change Created|Modified|Deleted and commands with command add --command C --exit N. Craft closes with --outcome accepted|rejected --diagnostic T [--blocked-by L]. nwdes writes these closed records under the feature's runs/<kind>[.<slice>].json, beside the handoff rather than inside it. Their accepted outcomes replace neither host-observed GREEN nor EXAMINE.

Review evidence

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. Each run it actually executes is recorded with nwdes review observation add before it closes the review. Selection is mechanical, never memory-picked. Each literal run text includes actual argv, exit status, stdout and stderr, including empty or incomplete selection and absent tooling. Large UTF-8 payloads use --text-file PATH; inline payloads use --text TEXT. nwdes issues R ids and stamps commit/clean itself; revise or remove by --id R<n> or --at N.

nwdes review observation add --feature search --subject candidate --text-file run.txt
nwdes review finding add --feature search --subject candidate --location L --obligation T --observation T --remediation T --owner implementation
nwdes review close --feature search --subject candidate --outcome rejected --diagnostic T

Keep the generated subject and slice scope. Close requires at least one observation stamped clean at the current commit; ReviewUnobserved or StaleObservation retains the draft for correction. Preserve actual provenance and results. Missing observations remain indeterminate, never producer confidence. On rejection, nwdes names every finding owner role and its read command; the owner reads exactly its own findings with nwdes review findings --owner O. Native messaging is harness-dependent. Where the host supports it, a reviewer sends each completed finding directly to its owner, naming the owner's nwdes review findings --owner O read; where it does not, the host route delivers that read and no message is pretended. Each completed finding goes directly to its owner. Host owns models and checker execution. Preserve candidate source/oracle bytes and artifact ownership.

Native execution

A batch candidate owner is an exact installed crafter (nw-software-crafter or nw-functional-software-crafter by the bound paradigm) invoked through the native form above with its execution tools. It is not a new role row and takes the batch's composition and verification duties from nw-throughput (Batch candidate owner); reviewers stay separate.

The host runs each slice's declared verification command itself and observes RED on the original source before craft and GREEN after craft; nwdes does not run it. For a bugfix, never select HEAD as the baseline after it already contains the fix. A setup, import or collection failure is not the promised behavioral RED.

For an applicable prefactoring move, preserve the existing GREEN oracle and support/runtime identities. Run its declared command before the move and after only the preserving movement, before new behavior. Keep distinct production identities and actual run evidence as nw-code-craftsmanship requires.

Formal checker/model runs retain receipt files beside the model, with checker and version, literal argv, exit status, stdout/stderr and model sha256. Cite receipt paths in the design's evidence; nwdes stores paths, not proof.

Scope and permitted evidence

Resolve the explicit repository, feature handoff, slice and configured paths once and pass them to affected roles. Include the original Request, human exclusions/amendments and provenance in ordinary producer/reviewer context. Do not ask the human to repeat known facts or treat producer scope reduction as authorization.

A role with limited tools receives immutable facts and real host-run results through its generated prompt; it records only through its declared capability. A path is not evidence for a role that cannot read it. Truncated diff prose is not complete review evidence. EXAMINE judges the public contract and observed user results. Producer classifications and source inspection do not substitute for those observations. Reference nw-typesafe-system-one for role-owned unchanged-request relay; a skill mention is not evidence of client/caller-exchange capability.

Reviewer and examiner boundaries

For DISTILL before-code alignment, MUST read ~/.claude/skills/nw-at-completeness-check/SKILL.md. When the original value, selected contract, and prior adequate alignment are unchanged with no new finding, reuse it without another ATD review. The examiner's independent expectations are fixed once per feature by nwdes expectations close, before the first slice's acceptance designer, and revised only with nwdes expectations open --from-current, then nwdes expectations close --revise. Supply the fixed public expectations to the acceptance reviewer within its evidence boundary; keep oracle authoring independent. Alignment concerns observation feasibility and ambiguity, not runtime acceptance.

Build the examiner's generated prompt without host observations or root context. It names a public-only workspace, its committed public document index and nwdes examine read and nwdes examine probe. The examiner gathers its own public observations there and records each through its generated examination recording verbs before citing it. nwdes packet --kind examine follows the same contract; no source, diff, producer verification or private design reaches it.

Examine refuses host observation carriers. Missing public observations remain indeterminate, never supplied from producer conf

Truncated for display — read the full file on GitHub.

Related Skills

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