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.
The body is highly actionable with executable commands and complete copy-paste examples, organized into a clear sequenced workflow. Its weaknesses are redundancy across the three full examples and repeated best-practices guidance, plus a thin validation step.
Suggestions
Cut to one or two example subagents — the data-scientist example largely duplicates what the code-reviewer and debugger examples already demonstrate, saving ~30 lines.
Merge the 'Best Practices' section into 'Writing Effective Descriptions' and the workflow steps to eliminate repeated guidance about descriptions and proactive language.
Strengthen the validation checkpoint with a concrete check, e.g. re-reading the created file to confirm the frontmatter parses (or a YAML lint command) before testing the agent.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient, but the three full-length example subagents (~90 lines) overlap heavily — the data-scientist example adds little beyond the first two — and the 'Best Practices' section repeats guidance already given in 'Writing Effective Descriptions' ('Write detailed descriptions', 'Use proactive language'). | 3 / 5 |
Actionability | Fully executable guidance throughout: copy-paste-ready example agent files, concrete bash commands ('mkdir -p .cursor/agents', 'touch .cursor/agents/my-agent.md'), a required-fields table, and a specific test invocation ('Use the my-agent subagent to [task description]') covering the common cases. | 5 / 5 |
Workflow Clarity | The 5-step workflow (decide scope, create file, define configuration, write system prompt, test) is clearly sequenced with a test step and a troubleshooting recovery path; however validation is light — 'Verify YAML frontmatter syntax is valid' names no concrete check or command. | 4 / 5 |
Progressive Disclosure | With no bundle files present, the single-file structure is well organized (clear headers, a locations table, distinct sections) and easy to navigate; the only content arguably belonging in a separate file is the three inlined full example agents. | 4 / 5 |
Total | 16 / 20 Passed |