CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

find-skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Quality

87%

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

92%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.

An extremely lean, perfectly actionable redirect stub that delegates entirely to a shared external skill file. Conciseness, actionability, and workflow clarity are all maximal for a single-purpose skill. The only weakness is progressive disclosure: the skill contains no overview content of its own and its sole reference points outside the bundle, so the skill is unusable if that external path is absent.

DimensionReasoningScore

Conciseness

The body is two lines with zero padding — a maintenance comment and a single directive — assuming Claude's competence with no re-explanation of known concepts, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

"Load and follow the shared skill at ~/.agents/skills/find-skills/SKILL.md" is a fully executable, unambiguous directive with a concrete path; per the rubric's scoring note, an instruction-only skill without code is not penalized when the guidance is this actionable.

5 / 5

Workflow Clarity

This is a single-task skill and its one action (load and follow the shared skill) is unambiguous, which the rubric's simple-skill guideline allows to score 5; no destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

The reference is clearly signaled and one level deep, but the body is a pure redirect with no overview content, and the target (~/.agents/skills/find-skills/SKILL.md) lies outside the skill directory with no bundle files (no references/, scripts/, or assets/ exist) to back it — placing it between the 'some structure' and 'good structure' anchors, closer to 3 given the unverifiable external pointer.

3 / 5

Total

18

/

20

Passed

Description

78%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.

A well-constructed description that clearly states both capability and usage triggers with natural user phrasings. Its main weakness is thin action coverage — 'discover and install' is the entire capability list — and the broad 'extending capabilities' phrasing introduces minor conflict risk. Trigger-term coverage is good though not exhaustive of synonyms.

Suggestions

Expand the 'what' beyond two verbs by naming 1-2 more concrete capabilities (e.g., searching a skill catalog, checking compatibility, managing installed skills) to lift specificity from '1-2 actions' toward comprehensive coverage.

Add a few more natural trigger variations such as 'add a skill', 'browse available skills', or 'skill marketplace/store' to broaden trigger-term coverage.

Tighten the broad phrase 'express interest in extending capabilities' to more specific triggers (e.g., 'wants to add new abilities to their agent') to reduce overlap with plugin- or tooling-management skills.

DimensionReasoningScore

Specificity

"discover and install agent skills" names the domain with exactly two concrete actions and no further coverage of what those involve, matching the '1-2 concrete actions, but not comprehensive' anchor rather than the 'several specific actions' of level 4.

3 / 5

Completeness

It explicitly answers both 'what' ("discover and install agent skills") and 'when' ("This skill should be used when the user is looking for functionality that might exist as an installable skill") with concrete quoted trigger phrases, matching the top anchor; the 'when' is explicit and specific, so level 4's 'could be more explicit' caveat does not apply.

5 / 5

Trigger Term Quality

Quoted phrases like "how do I do X", "find a skill for X", and "is there a skill that can..." are natural user utterances with good coverage, but common variations (e.g., "add a skill", "browse skills", "skill marketplace") are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The skill-discovery niche with quoted trigger phrases is mostly distinct, but "express interest in extending capabilities" is broad enough to overlap with plugin- or tooling-management skills, matching 'mostly distinct; minor overlap risk' rather than the minimal-conflict level 5.

4 / 5

Total

16

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

phatblat/dotfiles

Path

.agents/harness/adapters/antigravity/skills/find-skills/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.