CtrlK
BlogDocsLog inGet started
Tessl Logo

research

Deep research before planning. Launches parallel agents to search docs, web, and codebase, then synthesizes findings into actionable context.

60

Quality

70%

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 ./research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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-orchestration skill with strong workflow sequencing and mandatory validation checkpoints. The main drag is mild verbosity in some philosophical asides and the dense inline agent descriptions.

Suggestions

Trim philosophical asides (e.g. 'Delight is the absence of friction plus a moment of care') to keep the body lean and token-efficient.

Consider moving the seven agent-type definitions into a references/ file with a concise summary table inline, improving progressive disclosure toward the 5 anchor.

DimensionReasoningScore

Conciseness

The body is mostly efficient procedural guidance Claude would not auto-generate, but includes some philosophy padding ('Delight is the absence of friction plus a moment of care') and elaborated agent descriptions that could be tightened.

3 / 5

Actionability

Gives concrete, executable guidance for an orchestration skill — naming specific tools (AskUserQuestion, EnterPlanMode, mcp__context7__resolve_library_id, /ui) and concrete file sources (package.json, Gemfile, requirements.txt) — with only minor gaps.

4 / 5

Workflow Clarity

Six steps are clearly sequenced with explicit MANDATORY checkpoints at Steps 1 and 4, plus feedback loops (re-ask if ambiguities remain, surface contradictions before synthesizing), matching the validate-and-recover anchor.

5 / 5

Progressive Disclosure

Well-organized with clear section headers across a self-contained procedural skill that needs no external references; the 7 agent-type descriptions are somewhat dense inline but the structure is navigable, falling just short of the ideal split.

4 / 5

Total

16

/

20

Passed

Description

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

The description is specific and action-oriented in third person, with decent trigger terms and a clear niche. Its main weakness is the missing explicit 'Use when...' clause, leaving the trigger context only weakly implied.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants deep research before planning or implementation, especially for complex problems requiring multi-source investigation.'

Include natural trigger synonyms such as 'investigate', 'look into', or 'explore' alongside 'research' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Launches parallel agents to search docs, web, and codebase' and 'synthesizes findings into actionable context' — covering three search domains and a synthesis step, with only minor gaps in coverage relative to the comprehensive 5 anchor.

4 / 5

Completeness

The 'what' is clear (parallel agent research + synthesis), but the 'when' is only weakly implied via 'before planning' and lacks an explicit 'Use when...' clause, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural phrases a user would say ('Deep research', 'before planning', 'docs, web, and codebase') with good keyword coverage, though common synonyms like 'investigate', 'look into', or 'explore' are absent.

4 / 5

Distinctiveness Conflict Risk

The 'before planning' + 'parallel agents' framing carves a clear niche distinct from generic research, with only minor overlap risk against other research/investigation skills.

4 / 5

Total

15

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
figlabhq/agent-skills
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.