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-structured, actionable research workflow: concrete MCP calls with parameters, a six-step sequenced process, and explicit quality rules. The main gaps are the absence of an explicit pre-delivery validation step and outline-style (rather than ready-to-use) subagent prompts.
Suggestions
Add an explicit final validation step to the workflow (e.g., Step 6 becomes 'Verify every claim in the report has a citation; re-check flagging of single-source claims before delivery') to strengthen the feedback loop.
Replace the outline-style subagent plan ('Agent 1: Research sub-questions 1-2') with a copy-paste-ready prompt template each agent receives.
Consider moving the report template and user-prompt examples into a short reference file so SKILL.md stays a lean overview.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and assumes Claude's competence — tool signatures like `firecrawl_search(query: "<sub-question keywords>", limit: 8)` and a compact report template with no filler explaining what research or MCP is. Not a 5 because of minor trimmable material: the drift warning is a bit padded and the "Examples" section of user prompts largely duplicates the description's trigger list; not a 3 because there are no padded explanations of concepts Claude already knows. | 4 / 5 |
Actionability | Gives concrete, near-executable guidance: exact MCP tool calls with parameters (`web_search_advanced_exa(query: "<keywords>", numResults: 5, startPublishedDate: "2025-01-01")`, `crawling_exa(url: "<url>", tokensNum: 5000)`), concrete numeric targets ("2-3 keyword variations", "15-30 unique sources", "Read 3-5 key sources"), and a full report template. Not a 5 because the subagent section is outline-style ("Agent 1: Research sub-questions 1-2") rather than copy-paste-ready prompts, and tool calls are signatures rather than literal invocations; not a 3 because the guidance is far beyond pseudocode. | 4 / 5 |
Workflow Clarity | A clear six-step sequence with well-defined steps, branch handling ("If the user says 'just research it' — skip ahead with reasonable defaults"), and quality checkpoints ("If only one source says it, flag it as unverified", "Acknowledge gaps"). Not a 5 because there is no explicit final validation pass before delivery (e.g., "verify every claim has a citation before writing the report") — the Quality Rules are stated as rules rather than as a step in the sequence; not a 3 because the sequence is explicit with most checkpoints present. | 4 / 5 |
Progressive Disclosure | The single SKILL.md file (~150 lines) is well-organized into clearly signaled sections (When to Activate, MCP Requirements, Workflow, Parallel Research, Quality Rules) with no bundle files and no nested references. Not a 5 because at this length a couple of sections (the report template, the examples) could be split into reference files to keep the overview lean; not a 3 because all content is appropriately placed for a self-contained skill, with nothing buried or misfiled. | 4 / 5 |
Total | 16 / 20 Passed |