CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-add-fields

Add field definitions to existing research outline.

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-codex-en/research-add-fields/SKILL.md

The canonical home for this skill is research-add-fields in Weizhena/Deep-Research-skills

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 token-efficient and cleanly organized into a sequenced four-step workflow, but it stops short of fully executable guidance and lacks a validation checkpoint after modifying fields.yaml. Specifying the search-agent invocation and adding a YAML-validity check after save would lift the weaker dimensions.

Suggestions

Specify how to launch the web-search agent in Step 2B (e.g., the agent type, query template, and how to surface results) so the guidance is executable rather than implied.

Add a post-save validation step in Step 4 (e.g., re-read fields.yaml and confirm it parses as valid YAML with the new entries present) to satisfy the destructive-operation feedback-loop requirement.

Show the expected fields.yaml entry schema (name, description, category, detail_level) so appended fields are consistently structured.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with every line carrying an action and no padding or explanation of concepts Claude already knows, matching the 5 anchor.

5 / 5

Actionability

Steps give concrete direction (locate */fields.yaml, offer A/B source choices, append and save) but leave key details unspecified such as how to launch the web-search agent and the expected fields.yaml entry format, fitting the 3 anchor.

3 / 5

Workflow Clarity

Steps are clearly sequenced and include a user-confirmation checkpoint, but the in-place fields.yaml modification lacks a post-save validation step; per the rubric, destructive/in-place file operations without validation are capped at 3.

3 / 5

Progressive Disclosure

At under 50 lines with no external references needed, the skill is well-organized into Trigger, Workflow, and Output sections, qualifying for the simple-skill exception that allows a 5.

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 names a clear, narrow capability, but it omits any 'when to use' trigger guidance and only surfaces a single action. Adding explicit trigger phrasing and one or two more concrete actions would raise specificity and completeness.

Suggestions

Append a 'Use when...' clause naming the situations or user phrases that should invoke this skill (e.g., 'Use when the user wants to add or expand fields in an existing research outline').

List one or two additional concrete actions beyond 'add' (e.g., suggest, categorize, deduplicate fields) to broaden capability coverage.

Include natural synonyms or file references users might say ('fields.yaml', 'research schema', 'data dictionary') to improve trigger term quality.

DimensionReasoningScore

Specificity

Names the domain ('existing research outline') and one concrete action ('Add field definitions'), matching the 3 anchor; it is not a 4 because only a single action is listed with no broader coverage.

3 / 5

Completeness

It clearly states what the skill does but provides no 'Use when...' trigger guidance, so per the rubric a missing when clause caps completeness at 3.

3 / 5

Trigger Term Quality

Domain-relevant terms ('field definitions', 'research outline') are present but lack natural user phrasings, synonyms, or file extensions, fitting the 3 anchor rather than the more comprehensive 4.

3 / 5

Distinctiveness Conflict Risk

The narrow niche of supplementing a research outline's field definitions is mostly distinct with only minor overlap risk against related research skills; it falls short of 5 because no explicit trigger phrases reinforce the boundary.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Weizhena/Deep-Research-skills

Path

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