CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-scout

Search existing local, marketplace, GitHub, and web skill sources before creating a new skill. Use when the user wants to create, build, fork, or find a skill for a workflow.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable, with a clear sequenced workflow, an explicit external-vetting checkpoint, and concrete command shapes plus worked examples. Its only weakness is a few lines of provenance and justification that do not earn their place in the token budget.

Suggestions

Remove the "Source: salvaged from stale community PR #1232 by redminwang" provenance line; it does not help Claude execute the skill.

Tighten justifications such as "Local sources are preferred because they are already part of the user's environment" to a bare statement ("Prefer local sources.") and let the step ordering carry the rationale.

Optionally include one fully-worked search example with real keywords (not just the keyword|synonym placeholder) so a command is copy-paste runnable end-to-end.

DimensionReasoningScore

Conciseness

The body is mostly lean with no concept explanations, but lines like "Source: salvaged from stale community PR #1232 by redminwang" and "Local sources are preferred because they are already part of the user's environment" add justification/provenance that could be tightened away.

2 / 3

Actionability

It gives concrete, real command shapes (find, gh search repos, gh search code), a worked result table, and explicit ranking criteria; the literal keyword placeholders are justified by Step 1's keyword-capture step rather than being unjustified pseudocode.

3 / 3

Workflow Clarity

A clear six-step sequence is given, and Step 4 is an explicit vetting checkpoint (read frontmatter, scan for unexpected shell/network/credential handling, review the diff) before any adoption, with creation gated on user choice or no-match.

3 / 3

Progressive Disclosure

With no bundle files present, the body is organized into clear, well-labeled sections (When to Use, How It Works, Examples, Anti-Patterns, Related) with no nested references and no content that obviously needs to be split out.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong: it states a concrete action across four named source types and pairs it with an explicit, natural-language trigger clause. It clearly answers both what the skill does and when to use it with minimal risk of conflicting with other skills.

DimensionReasoningScore

Specificity

"Search existing local, marketplace, GitHub, and web skill sources" names four concrete source types and a concrete action, matching the anchor that lists multiple specific concrete actions.

3 / 3

Completeness

It explicitly states what the skill does ("Search existing ... skill sources before creating a new skill") and when to use it via an explicit "Use when" clause, answering both what and when.

3 / 3

Trigger Term Quality

"Use when the user wants to create, build, fork, or find a skill for a workflow" covers the natural phrasings a user would actually say, giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The skill occupies a clear niche (search-before-create for skills) with distinct triggers unlikely to fire for unrelated skills, and uses third-person imperative voice with no first/second-person penalty.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.