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.

62

Quality

75%

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

65%

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

A highly actionable, well-sequenced research skill with concrete tool calls and a usable report template. Weaker on workflow validation checkpoints (lives outside the flow) and progressive disclosure (monolithic, no external references).

Suggestions

Embed a verification checkpoint inside the workflow (e.g. Step 5.5: cross-reference claims and flag any sub-question with insufficient sources before writing the report) rather than relegating it to Quality Rules.

Move the full report markdown template and/or the example prompts into a referenced file (e.g. REPORT_TEMPLATE.md) so SKILL.md stays a lean overview with one-level-deep navigation.

Remove or trim the 'Examples' section since its prompts overlap with 'When to Activate', recovering tokens without losing trigger coverage.

DimensionReasoningScore

Conciseness

The body is largely action-dense and avoids explaining known concepts, but the trailing 'Examples' section duplicates 'When to Activate' and the full inline report template is verbose, so it could be tightened.

2 / 3

Actionability

Concrete, parameterized MCP calls (firecrawl_search limit:8, web_search_advanced_exa with startPublishedDate), specific numeric targets (15–30 sources, 2–3 keyword variations), and a copy-ready report template give fully executable guidance.

3 / 3

Workflow Clarity

The six steps are clearly sequenced, but verification/gap-checking guidance sits in a separate 'Quality Rules' section rather than as embedded checkpoints in this batch research workflow, so validation is implicit.

2 / 3

Progressive Disclosure

At ~153 lines with no bundle files, the skill is a well-sectioned but monolithic document; the report template and example prompts are inline content that could be split into one-level references.

2 / 3

Total

9

/

12

Passed

Description

85%

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, specific description with an explicit trigger clause and concrete third-person actions. Its only gap is trigger-term breadth — several natural phrasings users would say live in the body but not the description itself.

Suggestions

Fold one or two natural trigger phrasings from the body (e.g. 'deep dive', 'investigate', 'what's the current state of') into the description's 'Use when' clause to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in third person — 'Searches the web, synthesizes findings, and delivers cited reports with source attribution' — matching the top anchor for specific capabilities.

3 / 3

Completeness

Clearly answers what (multi-source search, synthesis, cited reports) and when via an explicit 'Use when the user wants thorough research on any topic with evidence and citations' clause.

3 / 3

Trigger Term Quality

'thorough research' and 'evidence and citations' are natural terms, but common variations users say ('deep dive', 'investigate') appear only in the body, not the description, so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The multi-source cited-report niche anchored to named firecrawl/exa MCPs is a clear, distinct trigger unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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.

Validation14 / 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.