Content
75%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-built, anti-drift skill: it consistently redirects from stale model memory to version-matched bundled docs, with concrete commands and paths for most operations. Main gaps are unnamed reference targets in two sections, mild repetition of the core warning, and the absence of an explicit recovery loop for type-check failures.
Suggestions
Name the actual file paths for the two unnamed references — replace 'read the bundled guide' and 'read the bundled DevTools documentation' with the specific paths under node_modules/ai/docs/ (and the DevTools package docs), matching the precision used elsewhere in the skill.
Consolidate the don't-trust-memory warning into a single section and reference it from 'Choosing a Model' and 'After Making Changes' instead of restating it, saving tokens without losing the point.
Add an explicit error-recovery sequence in 'After Making Changes' (type check fails → re-grep bundled docs for the changed API → fix → re-run), turning the current implicit loop into a checkpointed workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with directives and avoids explaining background concepts, but it is mildly repetitive: the don't-trust-memory point is made three times ('Whatever you remember... is likely outdated', 'Never write AI SDK code from memory', and again in 'Choosing a Model' and 'After Making Changes'), and the 'What the AI SDK Is' paragraph is partially redundant with the description. Fits anchor 4 — efficient with minor instances that could be trimmed — rather than 5. | 4 / 5 |
Actionability | Mostly executable guidance: concrete paths (node_modules/ai/docs/, <package>/node_modules/@ai-sdk/<name>/docs/), runnable commands (curl + jq model listing, npm view ai version, pnpm add ai --filter <pkg>), URL patterns (.md suffix, search-docs endpoint), and an env var name. It falls short of 5 because two sections defer with unnamed targets — 'read the bundled guide' and 'read the bundled DevTools documentation' give no file path, leaving the reader to discover what to open. | 4 / 5 |
Workflow Clarity | The doc-verification workflow is a clear numbered sequence (check install → read bundled docs → fallback to web search → explicitly say so if unsupported), with checkpoints for version currency (installed vs npm view ai version) and post-change validation (run the type checker, re-check docs on errors). No destructive or batch operations, so no cap applies. Not 5 because there is no explicit fix-and-retry loop for, e.g., type-check failures — it says to re-check docs but doesn't sequence the recovery. | 4 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), and the skill appropriately avoids inlining SDK documentation by delegating to the version-matched bundled docs at concrete one-level-deep paths, with well-organized sections. It falls short of 5 because 'the bundled guide' and 'the bundled DevTools documentation' are referenced without naming the specific files, creating minor navigation gaps. | 4 / 5 |
Total | 16 / 20 Passed |