Content
86%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, lean patterns skill that assumes expertise, gives concrete directives with exemplars, and cleanly defers detail to three clearly-signaled reference files. The only gap is the absence of inline executable code snippets, which is acceptable for an instruction-only skill but keeps actionability just below maximum.
Suggestions
Add 1-2 short inline code snippets for the most common decisions (e.g. a `SvelteMap`-backed collection read via `fromWorkspace` + `$derived`) to make the guidance copy-paste ready rather than exemplar-by-path.
Show a minimal before/after for one legacy-to-runes migration (e.g. `export let` + `on:click` → `$props()` + `onclick`) since the 'Avoid legacy patterns' bullet enumerates many APIs without an example.
Tighten the longest Core Decisions bullets (the `$state.raw` and `SvelteSet` entries) into a decision + one-line exemplar so the dense paragraphs scan as quickly as the shorter bullets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense, expert-targeted guidance that assumes Claude's competence—no basic explanations of what Svelte/runes are—and every bullet earns its place with high-signal decisions, exemplars, and concrete file paths. | 5 / 5 |
Actionability | Concrete, executable directives with specific function names (e.g. `fromWorkspace`, `createSubscriber`) and file exemplars (`packages/svelte-utils/src/from-workspace.svelte.ts`); as an instruction-only skill it lacks inline code snippets but the guidance is specific and actionable, leaving only minor gaps. | 4 / 5 |
Workflow Clarity | Clear sequencing via Source Checks → Upstream Grounding → Svelte 5 Baseline → Core Decisions → Reference Map, with verification checkpoints (check upstream docs before changing X); not a destructive/batch workflow so no cap applies, but multi-step validation loops are not its primary shape. | 4 / 5 |
Progressive Disclosure | The body is a clear overview with a Reference Map pointing one-level-deep to three real reference files, each explicitly signaled with when-to-read conditions, and all referenced paths verified to exist. | 5 / 5 |
Total | 18 / 20 Passed |