Content
96%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 workflow skill: dense with non-derivable project constraints, fully executable commands at every step, and explicit validation checkpoints with stop conditions and error-recovery loops. The only structural headroom is that the alternate export routes and naming rules could eventually be split into reference files as the skill grows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every sentence carries project-specific constraints Claude could not infer — "Figma's variables REST API is Enterprise-only, so the CLI's own fetch answers `403`", "A `use_figma` result can't carry it: it caps at 48 KB" — with zero padding and no explanation of concepts Claude already knows. This is anchor 5's 'lean and efficient; every token earns its place'. | 5 / 5 |
Actionability | Copy-paste-ready commands throughout: `npx tokens-bruecke@latest --input snapshot.json -c figma-export.config.json -o tokens/json --split-by-collection`, `git diff -U0 tokens/json | grep ... | grep -v createdAt`, `node scripts/diff-css-vars.mjs "$TMPDIR/tokens-before.css" tokens/tokens.css`, `pnpm --filter @gitbutler/but-ui-react check:tokens`, plus a concrete REST URL with header for the snapshot fetch. Fully executable and covering the common cases plus alternate routes, matching anchor 5. | 5 / 5 |
Workflow Clarity | A clearly numbered 5-step pipeline with explicit validation and stop conditions: step 2's diff check ("No output: `git checkout -- tokens/json`, tell the user Figma has no changes, and stop"), step 3's diff report with interpretation guidance, and step 4's broken-reference check with a recovery path (`scripts/rename-tokens.mjs` reading `token-map.json`). Error handling is explicit (403 → "Stop and ask; never hand-edit the JSON instead"), satisfying anchor 5's feedback loops for a batch operation. | 5 / 5 |
Progressive Disclosure | Well-organized numbered sections with a clearly signaled one-level pointer ("The package README has the pipeline in full"), and no bundle files exist to reference. It sits at anchor 4 rather than 5 because at ~95 dense lines the alternate export routes (Enterprise CLI, Figma agent, PR server) and the CSS naming rules are candidates for extraction into reference files, leaving minor organization headroom. | 4 / 5 |
Total | 19 / 20 Passed |