Conciseness

Efficient and dense with operational specifics, but with minor trimming opportunities: the file-modification-times prohibition appears twice ("Never use another `date` format or file modification times" in Timestamps and "Observation time is the scan's own `finishedAt`. Never use file modification times" in Keep the bundle honest), and a few similar restatements across sections. This fits anchor 4 ("minor instances of over-explanation that could be trimmed") better than anchor 5 ("every token earns its place").

Actionability

Fully executable, copy-paste-ready guidance: exact tool-argument table (e.g., `snyk_sca_scan` with `{path, all_projects: true, include_ignores: true}`), exact shell commands (`date -u +%Y-%m-%dT%H:%M:%SZ`, `git -C <path> rev-parse HEAD`, `python3 -m json.tool <output> > /dev/null`, PowerShell equivalents), explicit defaults (output path, scan order), and per-failure handling. Specific commands cover the common cases, matching anchor 5.

Workflow Clarity

Clear six-step sequence (snapshot context, scanner version, scans, build records, write-and-check, report) with an explicit validation checkpoint ("Confirm it parses: `python3 -m json.tool <output> > /dev/null`") and feedback loops for error recovery (auth error → stop and ask; tool unavailable → record `outcome: "unavailable"`; other failure → retry once, record, continue). This matches anchor 5's explicit validation plus error-recovery loops.

Progressive Disclosure

The body stays an orchestration overview while field mapping and bundle shaping are clearly signaled, one-level-deep references that exist as substantive files: "Map fields and choose identifiers with [references/evidence-profiles.md](references/evidence-profiles.md)" and "Shape the bundle and set availability states with [references/bundle-format.md](references/bundle-format.md)". Content is appropriately split with easy navigation, matching anchor 5.

Specificity

Multiple specific concrete actions with comprehensive coverage: "Runs only the Snyk scans the user puts in scope through the local Snyk MCP server, keeps each native record, and writes one JSON bundle plus a short coverage summary. Read-only." Each action is distinct and concrete (scoped scans, native-record preservation, single JSON bundle output, coverage summary), matching the anchor-5 example's level of detail rather than leaving minor coverage gaps.

Completeness

Explicitly answers both questions: what ("Runs only the Snyk scans the user puts in scope through the local Snyk MCP server, keeps each native record, and writes one JSON bundle plus a short coverage summary") and when ("Use when the user wants Snyk findings collected or exported as structured records with their supporting evidence", followed by three concrete example trigger phrases). This mirrors the anchor-5 example's structure; it also adds scope exclusions, exceeding anchor 4's "when could be more explicit".

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and literal user phrasings: "export Snyk findings for this repo as JSON", "collect Snyk SCA and Code results with evidence", "machine-readable Snyk findings bundle", plus variations "collected or exported" and "structured records". These are exactly the phrases a user would naturally say, so it matches anchor 5 rather than anchor 4 ("a few natural terms missing").

Distinctiveness Conflict Risk

Clear niche with distinct triggers and explicit disambiguation: "Not for fixing issues (use snyk-fix) or choosing packages (use secure-dependency-health-check)" removes overlap with the closest sibling skills, and the export/evidence framing is distinct from generic scanning or fixing. Minimal conflict risk, matching anchor 5.