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

67%

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-codex-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-structured, actionable research workflow with concrete prompt templates, output schemas, and user-confirmation checkpoints throughout. Main weaknesses are a redundant one-shot example that duplicates the template and the lack of explicit validation for generated YAML outputs.

Suggestions

Collapse the one-shot example or shorten it to only the filled-in differences from the template to remove redundancy.

Add an explicit validation/confirmation step that checks outline.yaml and fields.yaml are well-formed before finalizing.

Move the full prompt template and example into a referenced file if the skill grows, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient with a concrete prompt template and parameter list, but the one-shot example reproduces the template almost verbatim, adding redundancy that could be tightened rather than fully lean.

3 / 5

Actionability

Provides a reproducible prompt template with explicit parameter substitution, a parameter-retrieval list, and concrete output file schemas (outline.yaml, fields.yaml) with only minor gaps in field-level detail.

4 / 5

Workflow Clarity

Five steps are clearly sequenced with explicit request_user_input confirmation checkpoints at steps 1, 2, 3, and 5 serving as validation feedback loops; minor gap is the absence of any structural validation of the generated YAML files.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Trigger, Workflow, Output Path, Follow-up Commands) with no bundle files needed; the inlined one-shot example is a minor organization gap that keeps it at 4 rather than 5.

4 / 5

Total

15

/

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 states a clear purpose and two concrete actions but lacks an explicit 'Use when...' trigger clause, leaving the 'when' weakly implied through scenario labels. It is reasonably distinct but would benefit from natural trigger phrases and broader keyword coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when starting academic research, benchmarking tools, or selecting technologies').

Expand keyword coverage with synonyms and concrete file/format terms users actually say.

Tighten the scenario list into actionable trigger phrases rather than abstract domain labels.

DimensionReasoningScore

Specificity

Names the research domain and two concrete actions ('Conduct preliminary research', 'generate research outline'), but coverage is not comprehensive, matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

Has a clear 'what' but the 'when' is only weakly implied via the 'For academic research, benchmark research, technology selection, etc.' clause with no explicit 'Use when...' trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Lists relevant scenario keywords ('academic research', 'benchmark research', 'technology selection') but these are domain labels rather than the natural phrases users say, missing common variations and synonyms.

3 / 5

Distinctiveness Conflict Risk

The niche (preliminary research outline generation) is mostly distinct with only minor overlap risk against general research skills; the explicit scenario list narrows triggering, though 'research' itself is broad.

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

relative_links

Relative link issues: 4 missing

Warning

Total

15

/

16

Passed

Repository

Weizhena/Deep-Research-skills

Path

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