CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-add-fields

Add field definitions to existing research outline.

Quality

69%

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-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 concise and well-organized for a simple single-purpose skill, but its actionability and workflow clarity are limited by missing field-schema details and absent validation for the in-place YAML modification. Adding concrete format guidance and a verification checkpoint would raise the weaker dimensions.

Suggestions

Document the fields.yaml entry schema (e.g. required keys for name, description, category, detail_level) so append operations are unambiguous.

Add a validation step after saving, such as re-reading fields.yaml to confirm valid YAML and no duplicate field names.

Specify how new fields are merged (appended under the correct category, preserving existing entries) to make the append action fully executable.

DimensionReasoningScore

Conciseness

The body is lean and well-structured with no padding or explanation of concepts Claude already knows; every section (Trigger, Workflow steps, Output) earns its place, matching the 'lean and efficient; assumes Claude's competence' anchor.

5 / 5

Actionability

Steps are concrete at a high level (find */fields.yaml, ask user, display, confirm, append and save) but miss key details such as the fields.yaml schema, how category/detail_level are represented, and how to merge/append without clobbering existing entries; this fits 'some concrete guidance but incomplete' rather than the mostly-executable 4.

3 / 5

Workflow Clarity

The four steps are clearly sequenced and include a user-confirmation checkpoint, but the in-place modification of fields.yaml is a destructive/batch-style operation with no post-save validation (e.g. YAML validity, duplicate-field checks), so per the destructive-operation cap workflow_clarity cannot exceed 3.

3 / 5

Progressive Disclosure

This is a simple, single-purpose skill under 50 lines with no bundle files, and its content is organized into clearly labeled sections (Trigger, Workflow, Output), satisfying the simple-skill exception that allows progressive_disclosure to score 5 with just well-organized sections.

5 / 5

Total

16

/

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 is concise and states a clear, specific purpose, but it omits any explicit "Use when..." trigger guidance and lacks keyword variations or synonyms. It is distinct enough to avoid most conflicts yet would benefit from explicit trigger phrasing.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user wants to extend a research outline with new field definitions.'

Include synonyms and concrete terms users might say, such as 'research template', 'data fields', or 'fields.yaml'.

Optionally mention a second concrete action (e.g. categorizing or setting detail_level) to broaden coverage.

DimensionReasoningScore

Specificity

"Add field definitions to existing research outline" names the domain (research outline) and one concrete action (adding field definitions), matching the 'names domain and 1-2 concrete actions' anchor; it is not a 2 because the action is concrete rather than generic, and not a 4 because only a single action is given with no comprehensive coverage.

3 / 5

Completeness

It clearly states what the skill does ("Add field definitions to existing research outline") but provides no "Use when..." trigger guidance, so per the missing-trigger-clause cap it stays at 3 rather than reaching a 4 that requires both what and when.

3 / 5

Trigger Term Quality

The phrases "field definitions" and "research outline" are relevant domain keywords but the description lacks common variations, synonyms, file extensions, or an explicit trigger clause, fitting the 'some relevant keywords but missing common variations' anchor rather than the fuller coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

The niche of supplementing field definitions in research outlines is fairly distinct with only minor overlap risk against adjacent research/document skills; it is not a 5 because no explicit distinct trigger phrases are given.

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