Content
65%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concrete, well-organized guide with strong copy-paste examples and configs. Its biggest gap is progressive disclosure: seven reference files exist but are entirely orphaned, with their content duplicated inline rather than linked from the overview.
Suggestions
Link the seven references/ files from the body (e.g., a '## Further reading' section pointing to advanced-techniques.md, best-practices.md, examples.md, errors.md, conversation-context.md, managing-large-codebases.md) so the overview stays lean and the bundle is discoverable.
Move the inlined advanced/best-practice material (layered context, context priming, @-mention strategy advice) into the corresponding reference files and summarize one-liners in SKILL.md to reduce duplication.
Move the time-sensitive model token-limit table into a reference (or mark it as approximate/current) so the main body avoids date-sensitive facts, improving conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and product-specific (Cursor UI mechanics), but includes a time-sensitive model token-limit table not placed in a deprecated section and some mild explanatory prose ("managing it well is the single biggest lever"), so it could be tightened. | 2 / 3 |
Actionability | It supplies concrete, copy-paste-ready @-mention prompt templates per task type, a full .cursorignore block, and a .cursor/rules .mdc example, giving specific executable guidance rather than vague direction. | 3 / 3 |
Workflow Clarity | Content is organized by task category with per-task patterns, but there is no sequenced multi-step workflow with validation checkpoints; this is acceptable for a non-destructive guide, yet the structure is advisory rather than a clear procedural sequence. | 2 / 3 |
Progressive Disclosure | The body is sectioned (not a wall of text), but the seven files in references/ (advanced-techniques, best-practices, conversation-context, errors, examples, managing-large-codebases, context-optimization-strategies) are never linked or signaled from the body, and overlapping content is inlined, fitting the 'references present but not clearly signaled; content that should be separate is inline' anchor. | 2 / 3 |
Total | 9 / 12 Passed |