Content
90%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.
An exemplary single-file skill: dense with genuinely non-obvious operational knowledge, fully executable commands, and hard-won gotchas (quoting semantics, the outer PDB-stem key in fixed_positions_jsonl) presented as compact tables. The only real improvements are an explicit output-verification step after a run and a decision on whether the two tables belong in a reference file.
Suggestions
Add an explicit post-run validation step — e.g., "check the score= and seq_recovery= headers in out/seqs/<stem>.fa, and confirm fixed positions were held" — to close the workflow-clarity gap.
If the skill grows, move the checkpoint-selection and error tables into a references/ file and keep SKILL.md as a lean overview with clearly signaled links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its tokens with non-obvious, repo-specific knowledge: the string-parsing quirks of --sampling_temp and --pdb_path_chains, the silent fixed-positions failure mode, the checkpoint-noise table, and the error table. Nothing re-explains concepts Claude already knows — the first paragraph's model background exists only to route between proteinmpnn/ligandmpnn/solublempnn, which is decision-relevant rather than padding. | 5 / 5 |
Actionability | The skill provides a copy-paste-ready clone-and-run command block, the exact output location (out/seqs/<pdb_stem>.fa), a concrete chain-diagnostic grep (grep '^ATOM' file.pdb | cut -c22 | sort -u), and the named helper script make_fixed_positions_dict.py — fully executable guidance covering the common cases. | 5 / 5 |
Workflow Clarity | The run → interpret output → recover-from-errors flow is clear, and the silent-redesign gotcha plus the errors table give real feedback loops (including the silent all-positions-redesigned case). It falls short of the top anchor only because there is no explicit post-run verification step, e.g., checking score=/seq_recovery= headers or confirming fixed positions took effect before proceeding. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the ~73-line body is well-sectioned and self-contained with nothing that clearly demands a separate file. It sits just past the under-50-line simple-skill exception and the checkpoint/error tables are borderline candidates for a reference file, so structure is good but not the textbook clear-overview-plus-signaled-references shape. | 4 / 5 |
Total | 18 / 20 Passed |