CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

Conduct preliminary research on a topic and generate research outline. For academic research, benchmark research, technology selection, etc.

Quality

73%

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

Quality

Content

67%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 content is a well-sequenced, actionable workflow with concrete prompt templates and explicit user-confirmation checkpoints at every step. Its main weaknesses are a duplicated one-shot example that hurts token efficiency and the absence of concrete YAML output examples and agent-output validation.

Suggestions

Collapse the one-shot example or move it to a reference file so it does not duplicate the prompt template structure inline, improving conciseness.

Show complete concrete outline.yaml and fields.yaml examples instead of bullet-list descriptions to make the output fully copy-paste-ready.

Add an explicit validation/review step for the background web-search-agent's returned output before merging it in Step 4, strengthening the workflow's feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-structured steps, but the ~40-line one-shot example largely duplicates the prompt template structure, which is padding that could be tightened; it is not 4 because that duplicated block is a noticeable inefficiency, and not 2 because the rest is lean and not padded with concepts Claude already knows.

3 / 5

Actionability

Concrete copy-paste-ready prompt template, explicit parameter definitions ({topic}, {time_range}, etc.), and a filled one-shot example give mostly executable guidance; it is not 5 because the outline.yaml/fields.yaml outputs are described as bullet lists rather than shown as complete concrete YAML examples, leaving a minor gap.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit AskUserQuestion confirmation checkpoints at each step forming user-feedback loops; it is not 5 because there is no explicit validation of the background web-search-agent's returned output before merging, and not 3 because checkpoints are explicit rather than missing or implicit.

4 / 5

Progressive Disclosure

No bundle files exist and the body is well-organized into Trigger, Workflow, Output Path, and Follow-up Commands sections with clear navigation; it is not 5 because the long duplicated one-shot example could be moved to a one-level-deep reference file, leaving a minor organization gap, and not 3 because structure is clean and content is appropriately placed.

4 / 5

Total

15

/

20

Passed

Description

70%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 states both what the skill does and when to use it with concrete, scenario-based trigger terms, making it largely distinct and actionable. Its main weakness is moderate specificity (only two core actions) and a slightly open-ended "etc." that keeps the when-clause from being fully explicit.

Suggestions

Add one or two more concrete actions (e.g., "compile a sources list", "produce a structured fields definition") to lift specificity toward comprehensive coverage.

Replace the trailing "etc." with an explicit "Use when..." clause listing the concrete trigger phrases users would say.

Include common synonyms such as "literature review" or "landscape scan" to broaden natural trigger-term coverage.

DimensionReasoningScore

Specificity

Quotes "Conduct preliminary research on a topic" and "generate research outline" name the domain plus two concrete actions, matching the 3 anchor (1-2 concrete actions, not comprehensive); it is not 4 because there are not several distinct actions, and not 2 because the actions are concrete rather than minimal/generic.

3 / 5

Completeness

The "what" is clear ("Conduct preliminary research... and generate research outline") and the "when" is supplied via "For academic research, benchmark research, technology selection, etc.", an equivalent explicit trigger guidance; it is not 5 because the trailing "etc." leaves the when less than fully specific, and not 3 because both what and when are explicitly present.

4 / 5

Trigger Term Quality

Phrases "academic research", "benchmark research", "technology selection", and "preliminary research" give good natural keyword coverage across scenarios; it is not 5 because common synonyms like "literature review" or file/extension cues are missing, and not 3 because coverage goes beyond a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

The preliminary-research-and-outline niche with scenario-specific triggers is mostly distinct with only minor overlap risk against a related deep-research skill; it is not 5 because the broad term "research" could still collide with related research skills, and not 3 because the triggers are specific rather than generic.

4 / 5

Total

15

/

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

allowed_tools_field

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

Warning

relative_links

Relative link issues: 4 missing

Warning

Total

14

/

16

Passed

Repository

Weizhena/Deep-Research-skills

Path

skills/research-en/research/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.