Content
67%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, largely executable reference for installing and applying Geist in Next.js, with useful typography direction and anti-patterns. Its main weakness is token efficiency: a redundant 'Key Points' recap, a content-free 'Subset Configuration' section, and tabulated facts Claude already knows could be trimmed or split into reference files.
Suggestions
Remove the 'Key Points' section — all seven bullets restate content already covered above, and the same lines could be deleted with no loss of information.
Either replace the 'Subset Configuration' section with actual executable configuration or delete it; an import statement followed by two comments and no code teaches nothing.
Move the font-weight table and Geist Pixel variant table into a reference file (e.g., references/fonts.md) to keep SKILL.md a lean overview, and add a Geist Pixel import example so its usage is actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and code-first, but includes unnecessary material: the 'Key Points' section recapitulates facts already stated (import paths, CSS variables, ligatures), 'Subset Configuration' is an empty code block with only comments, and the 9-row weight table adds little Claude cannot infer. Not score 2 because padding is limited to a few sections rather than pervasive. | 3 / 5 |
Actionability | Mostly executable guidance: copy-paste-ready app/layout.tsx, tailwind.config.ts, CSS variable usage, and concrete type recipes, plus exact ligature settings for VS Code and CSS. Minor gaps — no Pages Router example and no import code for Geist Pixel despite documenting its variants — keep it below fully copy-paste-complete coverage. | 4 / 5 |
Workflow Clarity | This is a single-purpose configuration skill and the path is unambiguous and ordered (install via npm, wire fonts into the root layout, extend Tailwind, use the utility classes), with no destructive or batch operations requiring validation checkpoints. It stays at 4 rather than 5 because multiple scenarios (App Router, Tailwind, subsets) are presented side-by-side without an explicit ordered flow or checkpoints. | 4 / 5 |
Progressive Disclosure | No bundle files exist, so everything is inline in a single SKILL.md with well-organized section headers and a flat, navigable structure. Content is mostly appropriately placed, though separable reference material (the weight table, Geist Pixel variant table, and typography direction section) is inlined rather than split into references, which is a minor organization gap. | 4 / 5 |
Total | 15 / 20 Passed |