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 instruction-only skill body: token-dense, purely project-specific, and actionable at the symbol level, with embedded verification checkpoints in its mini-workflows. The only meaningful improvement areas are pulling inline session-policy detail into a reference and adding a feedback-loop pattern for error recovery.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~80-line body is dense, purely project-specific constraint ("An Account refuses foreign origins before attaching credentials and does not follow redirects"), explains nothing Claude already knows, and explicitly economizes ("Do not restate either here or in code comments"). This matches the 5 anchor — lean, assumes competence, every token earns its place — and is clearly not the 4 anchor, which requires identifiable over-explanation to trim. | 5 / 5 |
Actionability | Guidance is concrete throughout: exact constructors per app type in the composition table (`createBrowserOAuth`, `createTauriAuth()`, `createCookieSessionAuth`), exact options ("`account.fetch` uses `credentials: 'omit'`"), exact verbs (`startSignIn`/`completeSignIn`), exact keying (`{#key auth.state.account}`), and explicit status mapping (401 vs retryable 503). Per the rubric's instruction-only note, absent code is not penalized when guidance is this actionable; specific examples cover the common cases, matching 5 rather than 4's "minor gaps". | 5 / 5 |
Workflow Clarity | Several mini-workflows carry real checkpoints: "ask DeepWiki a narrow question…, then verify decisive details against the installed source", "Pending work checks the captured Account after each await", and "Test provider-link callback binding and implicit same-email linking separately". This matches 4's "clear sequence with most checkpoints present"; it is not 5 because no end-to-end validate→fix→retry feedback loop is laid out, and not 3 because checkpoints are explicit rather than missing. | 4 / 5 |
Progressive Disclosure | Sections are well-labeled and delegation is exemplary and one level deep ("The README owns the explanation; the contract owns the signatures"), matching the 4 anchor's good structure with minor gaps. It falls short of 5 because there is no quick-start/navigation framing and fairly deep operational detail is inlined (session-policy specifics: 30-day sliding expiry, `freshAge` 600 seconds) that a stricter split would move to a reference file. | 4 / 5 |
Total | 18 / 20 Passed |