Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is concise, well-sequenced, and includes an explicit validation step with graceful fallback, making conciseness and workflow clarity strong. Actionability and progressive disclosure are weaker: the output is a placeholder template and the single referenced shared file does not exist.
Suggestions
Make the shared reference real or remove it: create ../shared-references/patent-writing-principles.md (the Problem-Solution-Advantage framework and claimable-subject-matter guidelines) so the "Load ..." instruction is not a broken path.
Tighten actionability by replacing placeholder output fields ([invention title], [formal problem statement]) with worked example values or explicit derivation instructions tied to the input artifacts.
Consider moving the claim-category, drawing-plan, and output-template tables into a reference file so the SKILL.md body stays an overview, improving progressive-disclosure depth to one level.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — it never explains what a patent or claim is, and every section (framework, decomposition, tables, dependency map) earns its place, matching the 3-anchor of efficient content where every token counts. | 3 / 3 |
Actionability | It provides concrete reference material (claim-category table, dependency-map example, a real mcp__codex__codex call config) but the production steps are descriptive ("Determine what categories", "Plan what figures") and the output is a placeholder skeleton ([invention title], [formal problem statement]) rather than copy-paste-ready guidance, fitting the 2-anchor of concrete but incomplete. | 2 / 3 |
Workflow Clarity | The 7 steps are clearly sequenced and Step 6 is an explicit validation checkpoint, with graceful degradation in Key Rules ("If mcp__codex__codex is not available, skip cross-model validation and note it"), matching the 3-anchor of a clear sequence with explicit validation and error recovery. | 3 / 3 |
Progressive Disclosure | The body is well-sectioned and its one external reference is clearly signaled ("Load ../shared-references/patent-writing-principles.md for the Problem-Solution-Advantage framework"), but no references/scripts/assets bundle exists and that shared-references path is broken (file absent), while heavy tables and the output template live inline — fitting the 2-anchor of decent structure with signaling/organization gaps rather than the 3-anchor of well-split one-level references. | 2 / 3 |
Total | 10 / 12 Passed |