nlpm

Check cross-component consistency — reference integrity, orphans, contradictions

Auto-fix fixable issues in NL artifacts — missing fields, heading gaps, field renames

Initialize NLPM for this project — detect artifacts, set lint strictness

Discover and inventory all natural language programming artifacts in a repository

Score NL programming artifacts — 100-point quality analysis per file

Cross-component consistency analyzer for NL programming artifacts. Checks reference integrity, detects orphans, finds behavioral contradictions, and identifies terminology drift across plugin components. <example> Context: User runs /nlpm:check on a plugin directory user: "/nlpm:check" assistant: "I'll use the checker to verify cross-component consistency." </example> <example> Context: Developer renamed a skill directory and wants to verify no broken references assistant: "I'll dispatch the checker to find any broken skill references across agents and commands." </example>

Discover and classify all NL programming artifacts in a repository. <example> Context: User wants to inventory their NL artifacts user: "/nlpm:scan" assistant: "I'll use the scanner to discover all NL artifacts." </example> <example> Context: User wants to check a specific project user: "/nlpm:scan ~/github/myproject" assistant: "I'll scan that project for NL programming artifacts." </example>

Scores NL programming artifacts on a 100-point scale using deterministic penalties. Use this agent when scoring plugin components, checking artifact quality, or running quality analysis on commands, agents, skills, rules, hooks, or CLAUDE.md. <example> Context: User runs /nlpm:score on a directory assistant: "I'll use the scorer to analyze and score these artifacts." </example> <example> Context: Quality check before a plugin release assistant: "I'll dispatch the scorer to verify all artifacts meet the threshold." </example> <example> Context: Fix command needs to identify issues before applying repairs assistant: "I'll use the scorer to identify issues and their penalties." </example>

Scan Claude Code plugins for security risks in executable artifacts: hooks, scripts, MCP configs, dependencies, and prompt injection surfaces. <example> Context: Auditing an external plugin before submitting PRs user: "Scan this plugin for security issues" assistant: "I'll use the security-scanner agent to check all executable artifacts." <commentary> Pre-contribution security gate. Must pass before any PRs are submitted to external repos. </commentary> </example> <example> Context: User wants to vet a plugin before installing user: "Is this plugin safe to install?" assistant: "I'll use the security-scanner agent to check for dangerous patterns." <commentary> Safety check for plugin consumers. Reports execution surfaces and risk level. </commentary> </example>

Evaluate NL artifacts against test specifications. Predicts trigger accuracy, checks output format expectations, validates frontmatter, and scores against thresholds. <example> Context: Developer wrote a spec for a new agent and wants to check if it passes user: "/nlpm:test" assistant: "I'll use the tester to evaluate your artifacts against their specs." </example> <example> Context: Developer is doing TDD — wrote the spec first, artifact doesn't exist yet user: "/nlpm:test agents/my-agent.spec.md" assistant: "I'll use the tester to check — the artifact doesn't exist yet, so this will be RED." </example>

How to design and build Claude Code plugins -- architecture decisions, component selection, file structure, manifest configuration, marketplace publishing. Use when planning, creating, or reviewing a Claude Code plugin.

How to write Claude Code hooks -- event selection, hook types, matcher patterns, blocking vs advisory, portable paths. Use when creating hooks for quality gates, automation, or policy enforcement.

Use when writing, reviewing, or validating Claude Code plugin artifacts — check frontmatter schemas, hook event names, naming conventions, prompt structure, or reference syntax. Loaded by the NLPM scorer and checker agents for schema validation.

Multi-agent workflow patterns for Claude Code -- parallel dispatch, sequential pipelines, QC gates, retry loops, shared partials. Use when designing systems with multiple agents, commands, or processing stages.

Use when writing or reviewing NL artifacts and need to check for anti-patterns — vague quantifiers, prohibitions without alternatives, oversized skills, write-on-read-only agents, monolithic prompts, or linter-duplicating rules.

1 hook across 1 event