Content
56%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 delivers actionable, copy-paste-ready guidance and a well-sequenced manuscript workflow, but it is significantly over-long, explaining basic scientific-writing concepts Claude already knows and inlining material that should live in reference files. Progressive disclosure is undermined by both the inline bulk and the absence of the referenced bundle files.
Suggestions
Move the field-specific terminology section and the figure-requirement tables into dedicated reference files, keeping SKILL.md as a concise overview that links to them.
Cut explanations of concepts Claude already knows (common figure types, basic gene/chemical/species nomenclature, SI units) and retain only field-specific conventions that are non-obvious.
Reduce the redundant mandatory-figure emphasis (repeated MANDATORY/CRITICAL/EXTENSIVELY blocks) to a single concise instruction, and create the referenced references/, scripts/, and assets/ files so signaled paths resolve.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is noticeably verbose and explains concepts Claude already knows — IMRAD definitions, common figure types ('Bar graphs: Comparing discrete categories'), and field nomenclature across seven subsections (gene italics, IUPAC, binomial nomenclature, SI units) — plus heavily padded redundant emphasis ('MANDATORY', 'CRITICAL', 'EXTENSIVELY') on figure generation. Not a 1 because the content is on-topic rather than off-domain padding, and not a 3 because the unnecessary explanations are extensive, not occasional. | 2 / 5 |
Actionability | Provides mostly executable guidance: copy-paste bash commands ('python scripts/generate_schematic.py "..." -o figures/...'), full LaTeX environments, and a concrete two-stage outline-to-prose example with sample text. Not a 5 because some guidance stays abstract ('Establish the research problem's importance') and referenced scripts are not verified present, and not a 3 because the concrete code/commands substantially cover common cases. | 4 / 5 |
Workflow Clarity | A clear four-stage manuscript workflow (Planning, Drafting, Revision, Final Preparation) plus a sequenced two-stage writing process, with the Revision stage acting as a checkpoint. Not a 5 because explicit validate→fix→retry feedback loops are absent, and not a 3 because the sequence is well-defined with checkpoints; the destructive/batch validation cap does not apply to a writing skill. | 4 / 5 |
Progressive Disclosure | References are signaled one level deep ('refer to references/imrad_structure.md'), but large sections that belong in reference files are inlined (the seven-subsection field terminology guide, figure-requirement tables, LaTeX examples), and no references/, scripts/, or assets/ bundle directories exist so the signaled paths lead nowhere. Not a 4 because content that should be separate is substantially inline and the bundle is missing, and not a 2 because section headers and reference signals do provide some structure. | 3 / 5 |
Total | 13 / 20 Passed |