Content
50%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill's core workflow — a detailed drafting prompt followed by a concrete formatting script call — is genuinely actionable, and script references are real and correctly pointed. However, the body is buried under substantial auto-generated boilerplate, contains duplicated validation sections and a dangling cross-reference, and shows a fabricated expected output for its validation command, which undermines both conciseness and workflow reliability.
Suggestions
Remove the generic boilerplate sections (Key Features, Required Inputs, Validation and Safety Rules, Failure Handling, Deterministic Output Rules, Completion Checklist) and consolidate the two validation sections into one, keeping only the skill-specific workflow (inputs, drafting prompt, format command).
Replace the fabricated "Expected output format" block under Quick Validation with the actual argparse help text of `scripts/format_result.py --help`, or drop it entirely.
Fix the dangling "See `## Workflow` above for related details" reference in Implementation Details (the Workflow section appears later in the file), and add a short example of the final formatted output (text with inserted "(Figure 1)" citation and appended caption) so the expected deliverable is unambiguous.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is noticeably verbose with several padded boilerplate sections that teach Claude nothing: "Key Features" repeats the frontmatter description verbatim, and generic template blocks ("Required Inputs", "Validation and Safety Rules", "Failure Handling", "Input Validation", "Deterministic Output Rules", "Completion Checklist") state obvious generic discipline rather than skill-specific knowledge. It is above anchor 1 because the core workflow and usage instructions are skill-specific and non-trivial, so not "extensively" explaining known concepts, but multiple sections are pure padding. | 2 / 5 |
Actionability | The core path is concrete and executable: a full drafting prompt template with explicit requirements (">300 words", "analyze each domain (D1-D5)", "Use specific numbers") and a copy-paste command `python scripts/format_result.py --text "<generated_text>" --language "{{language}}"` that matches the actual script's interface. It stops short of anchor 5 because the "Quick Validation" section shows an expected output ("Result file: meta_results_risk_of_bias_result.md ...") that the command `format_result.py --help` does not actually produce, and no example of the final formatted output is given. | 4 / 5 |
Workflow Clarity | The two-step sequence (draft with the role prompt, then format via the script) is clearly listed and a validation shortcut exists, so it is above anchor 2. But validation checkpoints are unreliable or duplicated: the "Expected output format" block for the validation command is fabricated, "Validation Shortcut" and "Quick Validation" repeat the same command, and "Implementation Details" contains a dangling cross-reference ("See `## Workflow` above for related details" — the Workflow section appears later in the document). These are more than minor gaps, matching anchor 3 ("steps listed but validation gaps"). | 3 / 5 |
Progressive Disclosure | Bundle structure is sound at one level: `scripts/format_result.py` and `scripts/validate_skill.py` exist and are referenced with correct, clearly signaled paths, with no nested reference chains. However, the body itself is poorly organized into a single ~180-line file with redundant overlapping sections (two validation sections, three checklists, a duplicated description block) that should be consolidated or split, matching anchor 3 ("some structure but could be better organized"). | 3 / 5 |
Total | 12 / 20 Passed |