CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research

对目标话题进行初步调研,生成调研outline。用于学术调研、benchmark调研、技术选型等场景。

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 ./skills/research-zh/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 skill body is a well-structured, actionable research workflow with concrete prompt templates and user-confirmation checkpoints. Its main weakness is verbosity from a largely redundant one-shot example and underspecified merge logic in Step 4.

Suggestions

Trim or replace the One-shot example, which duplicates the prompt template structure, with a single concrete filled-in snippet or move it to a reference file.

Add explicit validation/feedback steps (e.g., what to do if web-search returns no new items or if the user rejects the framework) to strengthen workflow clarity.

Specify the Step 4 merge logic concretely — how {step1_output}, {step2_output}, and user fields are combined and how conflicts are resolved.

DimensionReasoningScore

Conciseness

The body is mostly efficient and avoids explaining concepts Claude already knows, but the One-shot example largely restates the prompt template structure with '...' fillers, which is duplicative padding that could be tightened.

3 / 5

Actionability

It provides a concrete, copy-paste prompt template with named variables and a hard constraint to reproduce it verbatim, plus a structured output spec; minor gaps in the Step 4 field-merge logic keep it just below fully executable.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with AskUserQuestion confirmation checkpoints at multiple stages; it lacks explicit error-recovery/feedback loops, so it does not reach the validation-rich 5 anchor.

4 / 5

Progressive Disclosure

The single self-contained file is well-organized into clear sections (触发方式, 执行流程, 输出路径, 后续命令) with no external references needed, but at ~146 lines it exceeds the simple-skill exception that would allow a 5.

4 / 5

Total

15

/

20

Passed

Description

62%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 concise and third-person, covering both what the skill does and when to use it via concrete scenario triggers. It is held back by limited action coverage and a lack of trigger-term synonyms.

Suggestions

Expand the 'what' to list a few more concrete actions (e.g., verify items, merge user-defined fields) to lift specificity.

Add natural trigger synonyms and an explicit 'Use when...' clause to improve trigger-term coverage and completeness.

Drop or sharpen the generic '等场景' (and other scenarios) to reduce overlap risk with adjacent skills.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — '进行初步调研' and '生成调研outline' — matching the anchor for 1-2 concrete actions, but offers no broader coverage of capabilities to reach 4.

3 / 5

Completeness

It states both what ('进行初步调研,生成调研outline') and when ('用于学术调研、benchmark调研、技术选型等场景'), providing explicit trigger guidance equivalent to 'Use when', though the 'when' could be more concrete.

4 / 5

Trigger Term Quality

It lists relevant terms ('学术调研', 'benchmark调研', '技术选型') a user might say, but lacks common synonyms/variations and a 'Use when' phrasing, so it sits at 'some relevant keywords' rather than 'good coverage'.

3 / 5

Distinctiveness Conflict Risk

The research-outline niche with concrete trigger scenarios is mostly distinct with only minor overlap risk; the trailing '等场景' (and other scenarios) slightly broadens it, keeping it just below a clear-niche 5.

4 / 5

Total

14

/

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