Content
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body has a clear, well-validated workflow and concrete tooling/path guidance, but it is verbose with repeated layout guidance, lacks executable code snippets, and keeps all detail inline in a monolithic file rather than using progressive disclosure. Weakest areas are conciseness, actionability, and progressive disclosure.
Suggestions
Consolidate the overlapping layout sections (Layout adaptation rule, Slide archetype defaults, Visual density rule, Nature-style page composition) into one section — they repeat the same 'avoid 1:1 splits, crop dense figures, let one side dominate' guidance multiple times.
Add at least one minimal executable snippet (e.g., a python-pptx slide-creation or PyMuPDF text-extraction example) so the named toolchain is copy-paste ready instead of only described.
Move Paper-Type Guidance and Style Rules into separate reference files (e.g., references/paper_types.md, references/style.md) to shrink the monolithic body, and add the missing UPSTREAM_LICENSE.txt that the body references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is operationally dense and avoids explaining concepts Claude already knows, but it is verbose: the "avoid 1:1 splits, crop dense figures, let one side dominate" guidance is repeated across Layout adaptation rule, Slide archetype defaults, Visual density rule, and Nature-style page composition, so it could be tightened. It is not a 1 because it does not pad with basic concept explanations, and not a 3 because of the substantial repetition. | 2 / 3 |
Actionability | It names concrete tooling (PyMuPDF, Pillow, python-pptx, zipfile) and concrete output paths and filenames, but provides no executable code snippets or copy-paste commands, and many rules ("use asymmetric layouts", "let one side dominate") are directives rather than executable steps. It is an instruction-heavy skill with specific guidance but not copy-paste ready, so it sits at 2 rather than 3. | 2 / 3 |
Workflow Clarity | Steps 1–8 give a clearly sequenced process, and Step 8 plus the Default Fast Path include an explicit verification/feedback loop — reopen the PPTX, check slide/media/notes counts, revise defects, document in qa_report.md — matching the anchor for clear sequence with validation checkpoints. | 3 / 3 |
Progressive Disclosure | The body is a ~500-line monolithic document with well-organized sections but no reference files to offload detail (Paper-Type Guidance, Style Rules could be separate files), and the one referenced file (UPSTREAM_LICENSE.txt) does not exist in the bundle. It is not a 1 because sections are well-structured, and not a 3 because content that should be split stays inline and a referenced path is missing. | 2 / 3 |
Total | 9 / 12 Passed |