Content
92%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.
Highly operational content: an executable command with exact flags, a precise input schema with validation logic, explicit preflight checks, output semantics, and clear boundaries against unavailable features. The only trimmable material is a small amount of repeated disclaimer text.
Suggestions
State the research-signal disclaimer (not a clinical diagnosis, not expression-direction) once — either in the intro or in Outputs — instead of twice.
The intent-confirmation guidance in the body's opening paragraph substantially repeats the description's trigger conditions; it could be tightened to a single sentence pointing back to the trigger rule.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with project-specific facts (checkpoint name and revision, CSV schema, validation predicate, exact flags, output filenames) and assumes Claude's competence throughout. It is not a 5 because of minor duplication — the research-not-clinical disclaimer appears both at the top ("not a clinical diagnosis or an expression-direction prediction") and again in Outputs ("It does not say whether expression goes up or down"). | 4 / 5 |
Actionability | The Examples section gives a complete, copy-paste-ready command with every flag, plus the exact CSV columns, a literal validation predicate, exact output filenames, and LLR sign semantics. The single environment substitution ("substitute that environment's interpreter path if the alias is unavailable") is explicitly justified. | 5 / 5 |
Workflow Clarity | The sequence — confirm context, inspect source without installing the runtime, check v1 executability, resolve and validate inputs, execute and verify score arrays — is explicit, with a numbered Preflight checklist, hard validation gates ("Validate the CSV headers before starting a GPU job", the row-check predicate), and documented error paths (report the required schema; return validated inputs with the missing prerequisite identified). Batch-operation validation is present, so no cap applies. | 5 / 5 |
Progressive Disclosure | A single-file skill with well-organized sections (Instructions, Preflight, Inputs, Examples, Outputs, Reporting, Boundaries) and no bundle files to split out; the only external pointers are clearly signaled one-level links to repo source (the parser and model configuration) used to explain the missing-feature path. | 5 / 5 |
Total | 19 / 20 Passed |