CtrlK
BlogDocsLog inGet started
Tessl Logo

find-similar-functions

Use truffler to find similar or pre-existing JavaScript/TypeScript symbols before implementing new code, especially helpers, utilities, parsers, formatters, scanners, fuzzy matchers, and other reusable functions. Agents should use this skill whenever they are about to add or refactor functionality in a JS/TS repository and need to avoid duplicating existing code, even if the user does not explicitly mention deduplication.

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable with concrete, executable truffler recipes and a clear multi-step workflow supported by useful strategy and decision guides. It is held back slightly by minor over-explanation and the absence of explicit validation feedback loops despite being a low-risk discovery task.

DimensionReasoningScore

Conciseness

The body is mostly efficient with tight command recipes and short guides, but a few lines restate the description ("Use this skill before writing new JavaScript or TypeScript code that might overlap") and over-explain intent ("The goal is to discover nearby functions ..."), keeping it just below the lean 5.

4 / 5

Actionability

It provides copy-paste-ready executable commands with real flags (e.g. `truffler "normalize path" src --kind function,method,constant,type --limit 20`) across installed, in-repo, and bunx variants, plus a concrete reporting template covering the common cases.

5 / 5

Workflow Clarity

A clear 6-step sequence runs from stating behavior through reporting, with an implicit inspect-before-edit checkpoint, but it lacks explicit validate-then-retry feedback loops, which caps it at 4 even though the task is non-destructive.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections (Workflow, Command Recipes, Search Strategy, Reuse Decision Guide, Reporting Template) with no bundle files to reference, but the body exceeds a lean overview length and has minor organization gaps versus the ideal one-level-deep reference structure of a 5.

4 / 5

Total

17

/

20

Passed

Description

83%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 answers both what the skill does and when to use it, with concrete symbol categories and natural developer trigger phrases. It is held back only by a single primary action and a moderately broad refactor trigger that invites minor overlap with general coding skills.

DimensionReasoningScore

Specificity

It names the core action ("find similar or pre-existing JavaScript/TypeScript symbols") and enumerates concrete symbol categories ("helpers, utilities, parsers, formatters, scanners, fuzzy matchers"), giving several specific actions with minor coverage gaps rather than the comprehensive multi-action list of a 5.

4 / 5

Completeness

It explicitly states what ("Use truffler to find similar or pre-existing JavaScript/TypeScript symbols") and when ("whenever they are about to add or refactor functionality in a JS/TS repository ... even if the user does not explicitly mention deduplication"), with concrete trigger phrases matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural developer terms appear ("add or refactor functionality", "avoid duplicating existing code", "deduplication") plus symbol-type synonyms, but a few common phrases a user might say (e.g. "DRY", "reuse") are not surfaced, stopping short of the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The truffler/JS-TS symbol-search-for-deduplication niche is mostly distinct, but the broad "about to add or refactor functionality" trigger carries minor overlap risk with general coding skills, placing it at 4 rather than the minimal-conflict 5.

4 / 5

Total

17

/

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
millionco/react-doctor
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.