Content
82%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 content is a well-structured, highly actionable research playbook: concrete MCP tool-call syntax, specific source-count targets, a full report template, and a quality-rules checklist, organized into a clear six-step workflow. Its main weaknesses are minor — validation guidance sits outside the step sequence, and the Examples section duplicates trigger phrases already covered under When to Activate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence — no explanations of what research or web search are — with every section carrying operational content (tool signatures, source targets, report template). Minor trimmable padding exists, such as the "Examples" section largely duplicating the trigger phrases already listed under "When to Activate", which keeps it below the level-5 "every token earns its place" anchor but above level 3's noticeably-unnecessary-explanation bar. | 4 / 5 |
Actionability | Guidance is copy-paste ready: concrete tool-call signatures with real parameters ("firecrawl_search(query: ..., limit: 8)", "web_search_advanced_exa(..., startPublishedDate: \"2025-01-01\")", "crawling_exa(url: ..., tokensNum: 5000)"), specific numeric targets (15-30 unique sources, 3-5 sub-questions, deep-read 3-5 sources), a complete report template, and explicit delivery rules. This matches the level-5 anchor for fully executable guidance covering the common cases. | 5 / 5 |
Workflow Clarity | The six steps (Understand → Plan → Search → Deep-Read → Synthesize → Deliver) are clearly sequenced, and the Quality Rules section supplies most checkpoints ("Every claim needs a source", "If only one source says it, flag it as unverified", "Acknowledge gaps"). It falls short of level 5 because validation lives outside the sequence — there is no explicit pre-delivery verification step and no error-recovery path for failed searches or unavailable MCPs; this is not a destructive/batch operation, so no level-3 cap applies. | 4 / 5 |
Progressive Disclosure | The single-file skill has no bundle files, and its content (workflow overview, tool calls, quality rules) is appropriately placed inline with clear section headers and easy navigation. The ~150-line body slightly exceeds what the under-50-line exception rewards, and items like the 30-line report template and the redundant Examples section could be consolidated or split out, placing it at "good structure; minor organization gaps" rather than level 5. | 4 / 5 |
Total | 17 / 20 Passed |