How this command is triggered — by the user, by Claude, or both
Slash command
/nlpm:score [path]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
## User Input ## Workflow ### Step 1: Load Config Read `.claude/nlpm.local.md` if it exists. Extract `score_threshold` (default: 70). ### Step 2: Parse Arguments | Input | Behavior | |-------|----------| | (empty) | Score all Category A+B artifacts in cwd | | directory path | Score all artifacts under that directory | | file path | Score that single file | | --changed | Score only files changed since last commit (uses `git diff --name-only HEAD`) | If `--changed` is present: run `git diff --name-only HEAD` to get changed files, then filter through `commands/shared/classify.md` to ke...
$ARGUMENTS
Read .claude/nlpm.local.md if it exists. Extract score_threshold (default: 70).
| Input | Behavior |
|---|---|
| (empty) | Score all Category A+B artifacts in cwd |
| directory path | Score all artifacts under that directory |
| file path | Score that single file |
| --changed | Score only files changed since last commit (uses git diff --name-only HEAD) |
If --changed is present: run git diff --name-only HEAD to get changed files, then filter through commands/shared/classify.md to keep only NL artifacts. Skip the full discovery step.
If path is a directory: use commands/shared/discover.md to find all NL artifacts.
If path is a file: use commands/shared/classify.md to determine its type.
If no artifacts found → "No NL programming artifacts found."
Dispatch two agents in parallel for each batch of up to 5 artifacts:
nlpm:scorer -- scores each artifact on the 100-point rubric (penalties, structure, heuristics)nlpm:vague-scanner -- counts vague quantifier words mechanically (fast, haiku)The scorer incorporates the vague-scanner's word counts into its penalty calculation. If the vague-scanner reports counts that differ from the scorer's own detection, use the vague-scanner's counts (deterministic grep is more reliable than heuristic detection for word counting).
Pass to both agents:
rule_overrides is present in .claude/nlpm.local.md)Collect results: per-artifact score + issue list.
NLPM Score Report
File Type Score Issues
───────────────────────────────────────────────────────────
{for each file}
Overall: {avg_score}/100 — {EXCELLENT|GOOD|ADEQUATE|WEAK|REWRITE} [threshold: {score_threshold}]
High: {N} | Medium: {N} | Low: {N}
Below threshold: {N} files
Top issues:
1. [{SEVERITY}] {file}:{line} — {issue} ({penalty})
2. ...
Score guide: 90+ Excellent | 80-89 Good | 70-79 Adequate | 60-69 Weak | <60 Rewrite
Error handling:
If .claude/nlpm-history.json does not exist, skip this step. Run /nlpm:trend to initialize tracking — it creates the history file on first run.
npx claudepluginhub afiyah-infinity-technologies/nlpm-for-claude3plugins reuse this command
First indexed Jul 12, 2026
/scoreScores vendor proposals against evaluation criteria with persistent structured storage. Also supports compare and audit subcommands.
/scoreCalculates lead scores by interactively weighting demographic and behavioral factors, with configurable models and output scope (Basic, Recommended, Complete). Optionally integrates with HubSpot.
/scoreScores NL programming artifacts on a 100-point quality scale, detecting issues like vague quantifiers and structural problems. Produces a report with per-file scores and overall rating.
/scoreCalculates automation potential scores for responsibilities using a 6-factor weighted algorithm, producing overall scores, factor breakdowns, tiers, priorities, ROI estimates, and risks.