Content
100%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.
Exemplary skill body: a tight overview with fixed rules, a clearly sequenced workflow with explicit stop/error conditions, and clean one-level-deep progressive disclosure into four real reference files. It assumes Claude's competence, never over-explains, and every instruction is directly executable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative throughout — rules, a six-step workflow, and a decision table with no explanation of concepts Claude already knows. Even the prescriptive loading-state spec (exact colors, pixel sizes, timing) is reproducibility specification rather than padding, and nothing can be trimmed without losing actionability. | 5 / 5 |
Actionability | Concrete, executable guidance throughout: exact MCP tool names ('list_available_accounts_or_orgs', 'get_stripe_account_info'), a client-to-output decision table, precise fallback behaviors ('If the Stripe tools are missing, blocked, or need sign-in, say so in one line with the fix... and stop. Don't produce an empty dashboard'), and account-selection rules keyed on 'acct_' prefixes. Per the rubric's scoring note, the absence of code in this instruction-only skill is not penalized because the guidance is fully actionable. | 5 / 5 |
Workflow Clarity | Six clearly sequenced steps (choose output, show progress, choose account, read references, build, hand over) with explicit validation and stop conditions for each failure mode: missing/blocked tools, no account listed, and an API-key session with a defined alternate path. The skill is read-only, so the destructive/batch validation cap does not apply. | 5 / 5 |
Progressive Disclosure | The body is a genuine overview: layout, queries, and per-output build instructions live in four one-level-deep reference files (all verified present in references/), each assigned via the decision table and step 4, with a fallback URL for hosted fetching. No content that belongs in references is inlined beyond what step 2 requires before references are read. | 5 / 5 |
Total | 20 / 20 Passed |