CtrlK
BlogDocsLog inGet started
Tessl Logo

deep-research

Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.

65

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/deep-research/SKILL.md

The canonical home for this skill is deep-research in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

75%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, 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.

DimensionReasoningScore

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

Description

83%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.

A strong description: concrete actions, named tooling, an explicit "Use when" clause, and the natural trigger phrase "thorough research". The main improvement opportunities are adding common trigger synonyms (deep dive, investigate) and slightly broadening the action list toward full workflow coverage.

DimensionReasoningScore

Specificity

Quotes several concrete actions — "Searches the web, synthesizes findings, and delivers cited reports with source attribution" — and names the concrete tooling ("using firecrawl and exa MCPs"). Not a 5 because coverage has minor gaps: no mention of sub-question planning, source deep-reading, or report structure; not a 3 because it lists several specific actions rather than just 1-2.

4 / 5

Completeness

Explicitly answers both parts: what — "Searches the web, synthesizes findings, and delivers cited reports with source attribution" — and when — "Use when the user wants thorough research on any topic with evidence and citations". This matches the anchor-5 pattern of a clear what paired with a concrete explicit trigger clause; not a 4 because the when-clause is already explicit and specific rather than merely serviceable.

5 / 5

Trigger Term Quality

Includes the natural phrases users would say — "thorough research on any topic", "evidence and citations" — which is good keyword coverage. Not a 5 because common variations like "deep dive", "investigate", or "look into" are missing (they appear only in the body, not the description); not a 3 because the primary natural term plus context phrases are present, not just bare keywords.

4 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — "Multi-source deep research using firecrawl and exa MCPs ... cited reports with source attribution" distinguishes it from single-source web-search or summarization skills. Not a 5 because "research on any topic" is broad and could overlap with a general web-search skill; not a 3 because the MCP tooling and citation/report framing give it a clear identity.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing

Warning

Total

14

/

16

Passed

Repository
affaan-m/ECC
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.