CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-deep

Read research outline, launch independent agent for each item for deep research. Disable task output.

Quality

66%

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

Quality

Content

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

The skill provides an actionable, sequenced batch-research workflow with a reproducible prompt template and validation step. It is somewhat held back by a redundant one-shot example and the absence of any progressive-disclosure reference structure.

Suggestions

Remove or condense the One-shot Example, or move it to a separate reference file, since it duplicates the Prompt Template.

Reconcile the variable names between the template ({output_dir}) and the example ({project_dir}) so the guidance is internally consistent.

Add an explicit orchestrator-side verification that each batch item's validation passed before marking it complete, rather than relying on the sub-agent's prompt.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the "One-shot Example" largely duplicates the Prompt Template structure with variables filled, adding tokens without new instructional value.

3 / 5

Actionability

A strictly-reproducible prompt template and a concrete validation command (python ~/.claude/skills/research/validate_json.py …) give mostly executable guidance, with minor path/variable inconsistency ({project_dir} vs {output_dir}).

4 / 5

Workflow Clarity

Five clearly sequenced steps with batch-level user-approval checkpoints and an embedded validation requirement; validation lives inside the agent prompt rather than being orchestrator-enforced, a minor gap.

4 / 5

Progressive Disclosure

Sectioning is reasonable, but no bundle/reference files exist and the inlined one-shot example is content that could live in a separate file; referenced paths are runtime data (outline.yaml, fields.yaml) rather than skill reference docs.

3 / 5

Total

14

/

20

Passed

Description

53%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 conveys a clear purpose and a few concrete actions but is written in operational rather than user-facing language and entirely lacks a "Use when…" trigger clause. It is reasonably distinct but not comprehensive.

Suggestions

Add an explicit "Use when…" trigger clause naming the natural situations or phrases that should invoke this skill.

Rephrase with third-person capability language and include natural user keywords (e.g. "deep research", "research outline", "parallel research agents") over operational config terms.

List the concrete capabilities more comprehensively (e.g. batching, resume, validation) instead of the single trailing "Disable task output" detail.

DimensionReasoningScore

Specificity

Names the research domain and a few concrete actions ("launch independent agent for each item", "Disable task output"), but coverage is minimal and not comprehensive.

3 / 5

Completeness

The "what" is clear (read outline, launch agents, disable output), but there is no "Use when…" clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Relevant keywords like "research outline" and "deep research" appear, but the language is operational ("launch independent agent", "Disable task output") rather than the natural phrases a user would say.

3 / 5

Distinctiveness Conflict Risk

The "deep research" batching niche tied to an outline.yaml mechanism is mostly distinct from other skills, with only minor overlap risk.

4 / 5

Total

13

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

Weizhena/Deep-Research-skills

Path

skills/research-en/research-deep/SKILL.md

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.