SkillAgentSearch skills...

nw-command-design-patterns-classification

How to size and categorize a command, the declarative command template, and the WHAT-vs-HOW logic-placement rule

Install / Use

npx skills add nWave-ai/nWave --skill nw-command-design-patterns-classification

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Supported Platforms

Zed

Our assessment of nw-command-design-patterns-classification

nw-command-design-patterns-classification scores 81/100 on our quality scale, 3526th of 4,698 Development & Engineering skills we index.

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

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

Substance
26/30
Structure
17/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-command-design-patterns-classification 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-command-design-patterns-classification compared with similar skills

All 4 of these similar skills score higher than nw-command-design-patterns-classification; compare them before choosing.

SkillScoreStarsUpdatedFormat
nw-command-design-patterns-classification (this skill)by nWave-ai816172mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

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

name: nw-command-design-patterns-classification description: How to size and categorize a command, the declarative command template, and the WHAT-vs-HOW logic-placement rule user-invocable: false disable-model-invocation: true

Command Classification, Sizing, and Declarative Template (KNOWLEDGE)

Kind: KNOWLEDGE (reference). Composed by nw-command-design-patterns core. Fires when: a command must be classified, sized, or restructured against the declarative template (the "what category / what size / what shape" question). No forced sequence.

The Forge Model (Gold Standard)

forge.md at 40 lines is the reference dispatcher. Contains: header (wave, agent, overview) | Agent invocation (name + command + config) | Success criteria (checklist) | Next wave handoff | Expected outputs. Every dispatcher should aspire to this pattern.

Command Categories

| Category | Description | Size Target | Examples | |----------|-------------|-------------|----------| | Simple | Direct action, minimal delegation | 40-80 lines | forge, start, version, git | | Dispatcher | Delegates to one agent with context | 40-150 lines | research, review, execute | | Orchestrator | Coordinates multiple agents/phases | 100-300 lines | develop, document |

Declarative Command Template

Commands declare WHAT, not HOW. The agent knows how to do its job.

# DW-{NAME}: {Title}

**Wave**: {WAVE_NAME}
**Agent**: {persona} ({agent-id})

## Overview

One paragraph: what this command does and when to use it.

## Context Files Required

- {path} - {why needed}

## Agent Invocation

@{agent-id}

Execute \*{command} for {parameters}.

**Context Files:**
- {files the orchestrator reads and passes}

**Configuration:**
- {key}: {value} # {comment}

## Success Criteria

- [ ] {measurable outcome}
- [ ] {quality gate}

## Next Wave

**Handoff To**: {next wave or workflow step}
**Deliverables**: {what this command produces}

# Expected outputs:
# - {file paths}

Size Targets and Evidence

Research (Chroma Research, Anthropic context engineering): focused prompts (~300 tokens) outperform full prompts (~113k tokens) | Claude shows most pronounced performance gap | Information buried mid-prompt gets deprioritized ("Lost in the Middle") | Opus 4.6 is proactive/self-directing; verbose instructions cause overtriggering

Targets: Dispatchers 40-150 lines | Orchestrators 100-300 lines | Current average 437 lines; target under 150

When Commands Should Contain Logic vs Delegate

Contain in command (declarative):

  1. Which agent to invoke
  2. What context files to read/pass
  3. Success criteria and quality gates
  4. Next wave handoff

Delegate to agent:

  1. Methodology (TDD phases, review criteria, refactoring levels)
  2. Domain-specific templates/schemas
  3. Tool-specific config (cosmic-ray, pytest)
  4. Quality assessment rubrics

Rule: if content describes HOW the agent does its work, it belongs in agent definition or skill, not command.

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