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, actionable routing skill that keeps the overview lean and pushes detail to clearly-signaled one-level-deep references. Slightly more padding in a couple of critical-rule explanations and implicit (rather than explicit) validate→fix→retry loops keep it just short of top marks.
Suggestions
Tighten the payment_method_types rule: move the dashboard/dynamic-methods rationale into the payments reference and keep only the do/don't in SKILL.md to reduce token overhead.
Add one explicit validate→fix→retry feedback loop for the tax registration check (e.g., confirm registration → if missing, direct user to set one up before enabling automatic_tax).
For the highest-frequency cases (one-time payments, subscriptions), include one short copy-paste code snippet inline in the routing row or a pointer to a specific example section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean rules, tables, and pointers that assume Claude's competence; a few explanatory passages (the dynamic payment methods rationale, sandbox explanation) are slightly padded but largely earn their place. Not a 5 because the payment_method_types paragraph and webhook sentence carry some over-explanation that could be tightened. | 4 / 5 |
Actionability | Concrete commands (`stripe sandbox create`, `stripe whoami --format json`) and exact parameter names (`automatic_tax: { enabled: true }`, `integration_identifier`, `payment_method_configurations`) with a precise routing table. Mostly executable guidance; gaps are appropriate for an instruction-routing skill but it lacks complete copy-paste code examples for the common cases. | 4 / 5 |
Workflow Clarity | The routing table plus 'Read the relevant reference file before answering' gives a clear sequence, and critical rules act as a checklist with an explicit tax registration checkpoint. Not a 5 because validation feedback loops are implicit rather than spelled out as validate→fix→retry steps. | 4 / 5 |
Progressive Disclosure | Clear overview with a routing table pointing to one-level-deep reference files (payments.md, connect.md, billing.md, tax.md, treasury.md, security.md), all confirmed present in references/; navigation is well-signaled via `<references/...>` paths. | 5 / 5 |
Total | 17 / 20 Passed |