CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-add-fields

向现有调研outline补充字段定义。

Quality

64%

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

Quality

Content

72%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 body is a concise, well-structured multi-step workflow with user-confirmation checkpoints, but it lacks concrete field-format details and a validation step for the file it modifies in place. Adding output validation and a fields.yaml schema example would raise actionability and workflow_clarity.

Suggestions

Add a validation/verification step after appending, e.g. re-read fields.yaml and confirm new fields parse and are non-duplicate before reporting done.

Include a concrete fields.yaml snippet showing the expected field structure (name, description, category, detail_level) so append format is unambiguous.

Specify how detail_level and category values are constrained (allowed values or where they come from) to close the actionability gap.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanation of concepts Claude already knows; every section and line earns its place, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

It gives concrete elements (glob `*/fields.yaml`, web-search-agent, appending to fields.yaml) but omits key details such as the yaml field structure, the exact append format, and how detail_level/category are recorded, matching the 'some concrete guidance but incomplete' anchor; not 4 because the gaps are material rather than minor.

3 / 5

Workflow Clarity

Four steps are clearly sequenced with a user-confirmation checkpoint, but the workflow performs in-place file modification (appending to fields.yaml) with no validation/verification of the resulting file, so per the destructive-operation cap workflow_clarity cannot exceed 3; not 4 because output validation is absent.

3 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well-organized with clear section headers (触发方式, 执行流程, Step 1-4, 输出), so per the simple-skill exception progressive_disclosure scores 5.

5 / 5

Total

16

/

20

Passed

Description

42%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 concrete purpose but omits any "Use when..." trigger guidance and natural user keywords, capping both completeness and trigger quality. It is functional but would benefit from explicit when-to-use phrasing and synonyms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to extend an existing research fields.yaml with new field definitions.'

Include natural trigger terms and synonyms users would say, such as 'research fields', 'add fields', 'fields.yaml', or '调研字段'.

Specify 1-2 more concrete actions (e.g. 'appends and categorizes fields with a detail_level') to lift specificity from 3 toward 4.

DimensionReasoningScore

Specificity

The phrase "向现有调研outline补充字段定义" names the domain (research outline fields) and one concrete action (supplement field definitions), matching the anchor that lists 1-2 concrete actions but is not comprehensive; it is not score 4 because only a single action is given.

3 / 5

Completeness

It gives a clear "what" (supplement field definitions to an existing research outline) but no "Use when..." trigger guidance, so per the rubric completeness is capped at 3; not 2 because the "what" is clear rather than vague.

3 / 5

Trigger Term Quality

It contains domain terms (调研outline, 字段定义) but no natural phrases a user would actually say and no synonyms or file extensions, fitting the anchor with one or two generic keywords missing the natural user phrasing; it is below 3 because common variations are absent.

2 / 5

Distinctiveness Conflict Risk

The niche (adding fields to a research outline) is somewhat specific but without explicit trigger guidance it could still overlap with other research-related skills, matching the "somewhat specific but could still overlap" anchor; not 4 because no distinct trigger phrases are provided.

3 / 5

Total

11

/

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

description_field

'description' is very short (19 chars), consider making it more detailed

Warning

allowed_tools_field

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

Warning

Total

14

/

16

Passed

Repository

Weizhena/Deep-Research-skills

Path

skills/research-zh/research-add-fields/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.