Conciseness

The body is dense and prescriptive with no padding or explanation of concepts Claude already knows — every rule is task-specific ('Never infer a physical column from an item name alone', 'Never emit [truncated]'). It falls at anchor 4 rather than 5 because some constraints are repeated across sections: the no-target-proposals rule appears in 'Non-Negotiable Boundaries', again in 'Run Modes' ('If an older specification contains target proposals, POC assumptions, target tests...'), and again in step 6, and the durable-document bullet list overlaps the package-responsibilities list.

Actionability

It provides fully executable commands with concrete flags for each pipeline stage — 'python <skill-dir>\scripts\oracle_spec_inventory.py <input> --module <module-id> --output <temp-manifest>', the compiler invocation with '--extraction-mode fresh --self-check', and the guard '--evidence ... --spec ... --output' — plus exact ID formats, output folder layouts, a concrete Section 12 column schema, hard row-length thresholds (4,000/5,000 characters), and a copy-paste screenshot link example. This matches 'Fully executable; copy-paste ready code or commands; specific examples cover the common cases' (fresh, refresh, and audit-only variants are all addressed).

Workflow Clarity

The 7-step workflow has a clear sequence and an explicit validation step with commands and an exhaustive failure catalog ('Validation must fail for missing template sections or markers, ... an omitted Forms item, ... oversized Section 6/12 rows'), plus a decode-retry loop ('Repeatedly decode Forms XML text until stable'). It sits at 4 rather than 5 because there is no explicit error-recovery loop — nothing says what to do when the guard fails (fix and re-run is implied by the failure catalog, not instructed), which anchor 5 requires ('feedback loops for error recovery').

Progressive Disclosure

References are well signaled and genuinely one level deep: the 'Required References' section lists six files, all of which exist in references/, and the template/contract/gates/lenses detail is correctly deferred to them ('The master specification must implement all 22 numbered sections and Appendices A-J in references/specification-template.md'). It is a 4 rather than 5 because the body still inlines exhaustive policy detail (the 15-bullet durable-document list, readability/deduplication rules, row-length limits) that reads as contract material rather than the 'clear overview' anchor 5 describes.

Specificity

The description lists multiple concrete actions with comprehensive coverage: 'Extract a complete, source-traceable legacy evidence specification' enumerates the exact input formats (Forms XML/FMT/FMB/FMX, PLL/PLD, DDL, message catalogues, menus/object libraries, screenshots) and the exact output elements ('every evidenced screen region, tab, field, operation, rule, message, database dependency, provenance locator, uncertainty'), plus explicit exclusions ('without inventing target requirements, target architecture, target tests, POC assumptions'). It matches the anchor 'Lists multiple specific concrete actions; comprehensive coverage' — below that there is no anchor with this breadth, and nothing is vague enough to sit at 4.

Completeness

Both questions are explicitly answered: the 'what' ('Extract a complete, source-traceable legacy evidence specification for one Oracle Forms module from...') and the 'when' ('Use for fresh or incremental reverse engineering when the output must preserve every evidenced...'). This matches anchor 5, 'Clearly and explicitly answers both what AND when with concrete trigger phrases'; a 4 would require the 'when' to be less explicit than this dedicated 'Use for' clause.

Trigger Term Quality

It covers the natural terms a user in this niche would say — 'Oracle Forms', 'reverse engineering', 'legacy', 'DDL', 'screenshots' — plus the file extensions/forms FMB, FMT, FMX, PLL, and PLD, matching 'Comprehensive coverage of natural terms including synonyms and file extensions'. The only near-miss synonyms (e.g., 'modernization', 'migration') are indirectly covered by 'fresh or incremental reverse engineering', so it is not the 'a few natural terms missing' anchor at 4.

Distinctiveness Conflict Risk

It occupies a clear niche with distinct triggers — Oracle Forms module extraction from FMB/FMT/FMX/PLL artifacts — that virtually no other skill would claim, matching 'Clear niche with distinct triggers; minimal conflict risk'. It is far more discriminating than the anchor-4 example ('Works with PDF and Word document files').