Content
78%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.
A well-structured, information-dense skill body: exhaustive but tabular catalog coverage, actionable ordering steps with explicit validation and anti-assumption cautions, and exemplary one-level-deep progressive disclosure across 18 reference files. The main weaknesses are minor: no post-submission error-recovery loop and a somewhat long inline citation procedure.
Suggestions
Trim or move the arXiv citation-fetching procedure into a small reference file to keep the main body lean.
Add a short post-order verification loop (e.g., check order acknowledgment email/page for status, and what to do if the order is rejected or the template mismatches) to close the workflow's feedback-loop gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and domain-specific — protocol tables, a goal-to-protocol decision list, and ordering steps — with essentially no explanation of concepts Claude already knows. It falls short of the lean anchor at 5 mainly due to the ~15-line citation procedure (arXiv fetch-and-verify instructions) and catalog-snapshot date handling (2026-09-30), time-sensitive detail that sits in the main body rather than a reference or staleness note. It is well above the score-3 anchor, which expects unnecessary explanation; none is present. This matches the score-4 anchor: efficient, with minor instances that could be trimmed. | 4 / 5 |
Actionability | Guidance is concrete for a browser-storefront skill: numbered steps with exact URLs ('Select a protocol at https://cloud.ginkgo.bio/protocols', 'Download the template linked on that protocol page'), a Choosing-a-Protocol list mapping goals to named protocols with prices, and explicit artifact-preservation instructions. It does not reach the fully-executable anchor because several steps deliberately defer to external pages ('inspect its actual format and fields', 'Configure parameters') rather than providing field-level detail — an honest but incomplete level of specificity. It clearly exceeds the score-3 anchor: no pseudocode-vague directions, and per the scoring notes, absence of code in an instruction-only skill is not penalized. | 4 / 5 |
Workflow Clarity | The ordering workflow is a clear 5-step sequence with real validation checkpoints: recheck the live catalog page and configured quote before ordering, inspect the downloaded template's actual fields, review the service terms, and explicit what-does-not-count-as-confirmation cautions ('an added cart item is not an accepted or executed run', 'A feasibility report or quote is not evidence that execution has started'). It falls short of the score-5 anchor because there is no true validate->fix->retry feedback loop after submission (e.g., what to do on a rejected order beyond 'use the official contact page'), leaving minor validation gaps per the score-4 anchor. | 4 / 5 |
Progressive Disclosure | The body is a genuine overview — catalog tables linking each of 18 protocols to its own references/*.md file (all verified to exist), with categorized sections, selection guidance, and ordering policy inline. References are one level deep, clearly signaled by category, and the per-protocol detail (inputs, outputs, workflow, ordering) is appropriately split into the reference files. This matches the anchor 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation' exactly. | 5 / 5 |
Total | 17 / 20 Passed |