CtrlK
BlogDocsLog inGet started
Tessl Logo

deep-research

Deep research on any topic using parallel sub-agents and built-in tools only (WebSearch/WebFetch + free APIs, no keys). Use when the user asks for a thorough multi-source investigation with a cited report — "深度调研X"、"deep research"、"帮我全面研究一下"、"多方求证"、"写一份调研报告". NOT for simple lookups (single WebSearch suffices) and NOT for academic literature surveys (use auto-research skill instead).

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean orchestration skill with a clear phased workflow and genuine reflection/critique feedback loops. The main weaknesses are bundle files referenced in the body that are absent, and a machine-specific absolute path in the alternative-workflow section that adds padding.

Suggestions

Ship the referenced bundle files (reference/subagent-prompt.md, reference/sources.md, reference/report.md) or inline their essential content so the offloaded executable detail is actually available.

Remove or generalize the machine-specific path '/Users/mi/claude-workspace/.mimocode/workflows/deep-research-pro.js' — it bloats the skill and is not portable.

Tighten the 'Alternative: scripted workflow' Notes block, which currently restates resume behavior already implied by the convergent-checkpoint description.

DimensionReasoningScore

Conciseness

The body is lean — terse phase descriptions, a compact depth table, and a workspace tree with no explanation of concepts Claude already knows. It drops below the lean/efficient anchor 5 because the 'Alternative: scripted workflow' section carries a machine-specific absolute path ('/Users/mi/claude-workspace/...') and somewhat verbose notes that could be trimmed.

4 / 5

Actionability

Gives concrete commands ('Run `date +%Y-%m-%d`', 'Spawn one sub-agent per angle in a single message') and specific file paths plus a copy-ready workflow invocation block. It is not a 5 because the core executable detail (sub-agent prompt template, sources, report format) is offloaded to referenced files that are not present in the bundle, leaving minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced Step 0 → Phases 1-5 pipeline with explicit validation checkpoints: Phase 4 reflect/gap-check feeds back into targeted delta-query sub-agents, and Phase 5 includes a skeptical-reviewer critique pass — a genuine validate→fix→retry feedback loop for a batch operation.

5 / 5

Progressive Disclosure

Good structure with clearly signaled one-level-deep references ('[reference/subagent-prompt.md]', '[reference/sources.md]', '[reference/report.md]') and content appropriately split by phase. It is not 5 because those referenced files do not exist in the bundle, so the navigation targets do not resolve.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: concrete capabilities, rich natural trigger terms in two languages, and explicit positive-plus-negative usage boundaries that distinguish it from adjacent research skills. The only minor gap is that the 'specificity' actions all elaborate one capability rather than enumerating several distinct ones.

DimensionReasoningScore

Specificity

Names the domain plus several concrete mechanisms — 'parallel sub-agents', 'built-in tools only (WebSearch/WebFetch + free APIs, no keys)', 'multi-source investigation with a cited report'. It lists multiple specific actions but they all describe one research capability rather than several distinct ones, so it sits just below the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ('Deep research on any topic using parallel sub-agents...') and when ('Use when the user asks for a thorough multi-source investigation with a cited report'), plus explicit negative boundary triggers ('NOT for simple lookups', 'NOT for academic literature surveys').

5 / 5

Trigger Term Quality

Gives comprehensive natural trigger phrases with synonyms in two languages — 'deep research', '帮我全面研究一下', '多方求证', '写一份调研报告' — matching the comprehensive-coverage-with-synonyms anchor; no file extensions apply to this skill type.

5 / 5

Distinctiveness Conflict Risk

Clear niche (multi-source cited investigation) with explicit disambiguation against adjacent skills — 'NOT for simple lookups (single WebSearch suffices)' and 'NOT for academic literature surveys (use auto-research skill instead)' — giving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
XiaomiMiMo/MiMo-Code
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.