CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

search-first

Research-before-coding workflow. Search for existing tools, libraries, and patterns before writing custom code. Systematizes the "search for existing solutions before implementing" approach. Use when starting new features or adding functionality.

Quality

65%

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 ./.kiro/skills/search-first/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

56%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 delivers genuinely useful, safety-conscious guidance — an explicit read-only default, approval checkpoints, a concrete decision matrix, and a ready-to-use subagent prompt. Its quality is dragged down by padding (ASCII diagram, tool-name lists Claude already knows, a duplicated trigger section) and by the absence of any progressive disclosure, with auxiliary catalogs and examples inlined in the main file.

Suggestions

Cut the ASCII workflow diagram and the 'Search Shortcuts by Category' lists; the five steps are already conveyed by the section order and decision matrix, and Claude knows what eslint/pytest/prettier are.

Move the Search Shortcuts catalog and worked examples into a references/ file (e.g. references/examples.md), keeping SKILL.md as a lean overview with one clearly signaled link per topic, and remove the 'When to Use This Skill' section that duplicates 'Trigger'.

Make the Evaluate step executable: specify how to score candidates (e.g., a 1-5 rubric over functionality, maintenance, docs, license, deps) and the threshold that maps to each decision-matrix row.

DimensionReasoningScore

Conciseness

Several padded sections push this noticeably below 'mostly efficient': the 26-line ASCII diagram restates the same five steps the surrounding sections describe, the 'Search Shortcuts by Category' lists tool names (eslint, prettier, black, gofmt, jest, pytest) Claude already knows, 'When to Use This Skill' near-duplicates the 'Trigger' section, and the 'Integration Points' section speculates about planner/architect agents. Not a 1: no basic-concept explanations and the core guidance (scope rules, decision matrix, examples) is tight; not a 3: this is more than 'some' unnecessary content — whole sections could be deleted without losing guidance.

2 / 5

Actionability

The decision matrix maps concrete signals to named actions, and Full Mode provides a copy-paste-ready subagent prompt template with slots for description, language, and constraints; the three worked examples show the full search→found→action pattern. Not a 5: a few steps remain vague hints ('Check for latest docs', 'Check MCP configuration and search', 'Score candidates' without any scoring method or threshold), leaving minor execution gaps.

4 / 5

Workflow Clarity

The five-step sequence (Need Analysis → Parallel Search → Evaluate → Decide → Approval/Implement) is clearly ordered, and the approval checkpoint is an explicit validation gate for the skill's write actions — reinforced by the Scope and Approval Rules section, so the destructive/batch cap does not apply. Not a 5: the Evaluate step names scoring dimensions but gives no scoring method or threshold, and there is no explicit error-recovery loop (e.g., what to do when search results are ambiguous or an install fails).

4 / 5

Progressive Disclosure

There are no bundle files (no references/, scripts/, or assets/), so everything is inline in a ~170-line SKILL.md with clear section headers. The Search Shortcuts catalog and the three worked examples are auxiliary material that clearly belongs in a one-level-deep reference file, matching the anchor for 'content that should be separate is inline'. Not a 4: this is more than a minor organization gap — two substantial sections are inlined that would keep the overview lean; not a 2: sections are well-labeled and navigable, not a wall of text.

3 / 5

Total

13

/

20

Passed

Description

58%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 third-person, honest, and includes an explicit 'Use when...' clause, satisfying the completeness floor. Its main weaknesses are redundant meta-wording ('Systematizes the...approach' restates the first sentence), a thin set of trigger synonyms relative to the body's own richer trigger list, and a broad when-clause that creates overlap risk with general feature-development skills.

Suggestions

Replace the redundant 'Systematizes the "search for existing solutions before implementing" approach' sentence with the downstream actions the skill performs, e.g. 'Evaluate candidates and recommend adopt/extend/build before any install.'

Broaden the 'when' clause with the body's own triggers: 'Use when adding a dependency or integration, writing a new utility or helper, or whenever about to write net-new code.'

Add natural trigger synonyms users would actually say ('before reinventing the wheel', 'existing library for X') to improve routing distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('Research-before-coding workflow') and one concrete action ('Search for existing tools, libraries, and patterns before writing custom code'), but coverage is not comprehensive — it omits the evaluate/decide/recommend actions the body actually performs, and the sentence 'Systematizes the "search for existing solutions before implementing" approach' is a meta-restatement rather than an action. Not a 4: several specific actions are not listed; not a 2: the domain is named and a concrete search action is stated.

3 / 5

Completeness

Explicitly answers both: the 'what' ('Search for existing tools, libraries, and patterns before writing custom code') and the 'when' ('Use when starting new features or adding functionality'). Not a 5: the 'when' clause is present but thinner than the anchor's concrete trigger phrasing — it lacks the richer triggers the body itself enumerates (dependencies, integrations, utilities/helpers). Not a 3: 'when' is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

Contains relevant natural phrases ('starting new features', 'adding functionality', 'existing tools, libraries, and patterns') but misses common variations a user would actually say, such as 'add a dependency', 'before implementing', 'integration', or 'reinventing the wheel'. Not a 4: those missing synonyms are among the most likely user phrasings, not just a few edge terms.

3 / 5

Distinctiveness Conflict Risk

The 'search before coding' framing gives it a recognizable niche, but the trigger 'starting new features or adding functionality' is broad and would overlap with general coding, planning, and dependency-management skills. Not a 4: the when-clause is generic enough that a feature-request could plausibly route to several other skills; not a 2: the research-first purpose is distinct from domain skills.

3 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

.kiro/skills/search-first/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.