Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise router with strong workflow sequencing and validation gates, plus real executable validation/build commands. Its main weakness is that the manifest-based routing core (manifest.yaml and the static/ fragments it points to) is not present in the bundle, which makes the load entry point and detailed gate criteria non-executable as shipped.
Suggestions
Ship manifest.yaml and the static/core/ and static/fragments/ files the body references, or inline the always_load list and stage-gate criteria so the skill is self-contained and the load step actually executes.
Add a fallback in section 1 for when manifest.yaml is unavailable (e.g., proceed with the always_load defaults listed inline) so the entry point is not a dead end.
Confirm every path cited in the body (e.g., static/core/output-contract.md, static/fragments/task/technical-disclosure.md) exists in the bundle or convert dangling references into inline guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean directive prose that assumes Claude's competence — no preamble explaining what a patent or Office Math is — and every line instructs (ID schemes, support states, stage gates, output languages). Not a 2 because there is no unnecessary explanation or padding to tighten. | 3 / 3 |
Actionability | Gives concrete, copy-paste-ready commands ('python scripts/validate_patent_draft.py draft.json', 'python scripts/build_patent_package.py draft.json --output-dir outputs --prefix patent') and specific schemas (P001/E001/F001/C001; explicit/inherent/needs-confirmation/unsupported), but the primary load entry point ('Read manifest.yaml, then read every file under always_load') and the static/core/workflow.md, static/fragments/task/* targets are absent from the bundle, leaving the load steps non-executable as written. | 2 / 3 |
Workflow Clarity | Five ordered stages (Load → Preserve grounding → Draft through stage gates → Produce formal documents → Validate) with explicit gates ('Do not move to formal claims until the source map, terminology ledger, inventories, evidence ledger, and invention concept pass their gates') and a validate→resolve-errors→deliver feedback loop. Not a 2 because sequencing and validation checkpoints are explicit in the body. | 3 / 3 |
Progressive Disclosure | Has a clear 5-section overview with one-level-deep references to real files (references/draft-schema.md, references/disclosure/disclosure_self_check.md, scripts/...), but the routing linchpin — manifest.yaml and the entire static/ tree (workflow.md, fragments, output-contract.md) — is referenced yet missing from the bundle, breaking the router→manifest→fragment navigation. Not a 3 because of these dangling entry-point paths; not a 1 because genuine structure and several valid references are present. | 2 / 3 |
Total | 10 / 12 Passed |