Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with executable commands, complete code, and a well-sequenced workflow backed by a verification checklist. Its weaknesses are token-efficiency (duplicated `convex dev --once` explanations across sections) and a monolithic structure that inlines framework-specific and tutorial material instead of offloading it to reference files.
Suggestions
De-duplicate the `npx convex dev --once` explanation: describe its behavior once in 'Path 1' or an 'Agent Mode' section and reference it from 'Path 2' and 'Verify' rather than restating it each time.
Extract the per-framework provider wiring (React/Vite, Next.js, Vue/Svelte/RN links) and the 'Writing Your First Function' tutorial into reference files under references/ and link to them from SKILL.md to reduce the monolithic inline body.
Trim the explanatory prose around template selection and the dev-loop options; the command tables and code already convey what to run.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | It is predominantly concrete commands and code, but quotes like 'Provisions an _anonymous_ local Convex backend bound to `127.0.0.1`. No browser login, no team/project prompts.' and the repeated `npx convex dev --once` explanation across 'Path 1', 'Path 2', 'Agent Mode', and 'Verify' show redundancy and explanatory padding that could be tightened. It is not a 1 because it does not explain concepts Claude already knows, and not a 3 because of the duplicated `--once` prose and extra scaffolding commentary. | 2 / 3 |
Actionability | Quotes like 'npm create convex@latest my-app -- -t react-vite-shadcn', 'npx convex dev --once', and the full ConvexReactProvider TSX snippets are fully executable, specific, and copy-paste ready, matching the top anchor. | 3 / 3 |
Workflow Clarity | The numbered 'Workflow' (1-6), the 'Verify the Setup' checklist, and the feedback loop 'The output tells the agent whether the schema and functions are valid' give a clear sequence with explicit validation checkpoints and error-recovery guidance. | 3 / 3 |
Progressive Disclosure | No bundle files exist (references/ and scripts/ are absent; only assets/icon.svg), and substantial content such as the multi-framework provider code, 'Writing Your First Function', and 'Development vs Production' is inlined in a ~450-line SKILL.md. Sectioning is clear (not a 1), but content that should be split into one-level-deep reference files is inline and no references are used despite the length, so it does not reach the top anchor. | 2 / 3 |
Total | 10 / 12 Passed |