CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

research-add-items

Add items (research objects) to existing research outline.

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/research-en/research-add-items/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 concise and well-structured for a simple skill, but the workflow steps are underspecified — lacking concrete commands and a validation checkpoint before the in-place, potentially destructive outline modification.

Suggestions

Add concrete, executable guidance to Step 1 (e.g., a Glob pattern command) and Step 3 (e.g., a Python snippet or CLI for parsing, merging, and deduplicating outline.yaml by key).

Insert an explicit validation checkpoint in Step 3 before saving (e.g., display the diff and require user confirmation, and validate the YAML still parses).

Specify the deduplication key/strategy concretely so the 'Avoid duplicates' instruction is actionable rather than abstract.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — short section headers, terse step descriptions, and no padding or explanation of concepts Claude already knows; every token earns its place, matching the score-5 anchor.

5 / 5

Actionability

Steps give only high-level hints (e.g., 'Find */outline.yaml', 'Append new items to outline.yaml') with no concrete commands, code, or schema details to execute the merge/dedup, matching the score-2 'minimal concrete guidance; missing the specific steps to execute' anchor.

2 / 5

Workflow Clarity

A clear 3-step sequence is present, but Step 3 is a batch/destructive in-place modification of outline.yaml with only 'Avoid duplicates' and no validation or verification checkpoint (e.g., confirm-before-save, schema check), so per the feedback-loop cap it cannot exceed 3.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent) and the skill is under 50 lines with no need for external references, so the simple-skill exception applies: well-organized sections earn a 5.

5 / 5

Total

15

/

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 clearly states the skill's purpose but is terse and lacks an explicit 'Use when...' trigger clause, which caps its completeness. Trigger-term coverage is thin, with few natural phrases a user would actually say.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g., 'Use when the user wants to supplement an existing research outline with more sources or objects').

Expand keyword coverage with natural synonyms and file references (e.g., 'outline.yaml', 'research objects', 'add sources').

Make the action more concrete and distinctive, e.g., 'Append research objects to an existing outline.yaml and deduplicate against existing entries.'

DimensionReasoningScore

Specificity

It names the domain (research outline) and one concrete action ('Add items') with the parenthetical 'research objects', but offers no comprehensive set of specific actions; this matches the score-3 anchor of 'domain and 1-2 concrete actions, but not comprehensive'.

3 / 5

Completeness

It states a clear 'what' (add items to an existing outline) but contains no 'Use when...' clause or explicit trigger guidance, which per the guidelines caps completeness at 3; the 'when' is only weakly implied by the action verb.

3 / 5

Trigger Term Quality

The phrase 'Add items ... to existing research outline' captures the core intent but lacks natural synonyms or variations a user might say (e.g., 'research objects', 'outline', 'supplement'); keyword coverage is thin and generic, falling between the 1 and 3 anchors but noticeably below midpoint at 2.

2 / 5

Distinctiveness Conflict Risk

The 'research outline' niche is somewhat specific and distinct from generic file skills, but the wording is generic enough ('Add items') that it could overlap with other research or note-organizing skills, matching the score-3 'somewhat specific but could still overlap' anchor.

3 / 5

Total

11

/

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