CtrlK
BlogDocsLog inGet started
Tessl Logo

skill-gap-analyzer

Analyzes the user's skill library to identify coverage gaps, redundant overlaps, and optimization opportunities. Use when users want to understand their skill ecosystem, optimize their skill collection, find missing capabilities for common workflows, or reduce redundant coverage. Triggered by requests like "analyze my skills," "what skills am I missing," "are any of my skills redundant," or "optimize my skill library."

61

Quality

77%

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 ./.agents/skills/skill-gap-analyzer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%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 presents a clear, well-sequenced five-step methodology with sensible evaluation criteria, but it is roughly twice as long as it needs to be: the enumerated category lists assume Claude lacks knowledge it already has, and the absence of any worked example (sample inventory row, model recommendation) leaves the guidance more abstract than its 'keep recommendations specific' advice demands.

Suggestions

Cut the Step 2 and Step 3 category taxonomies (~100 lines of domain/workflow/file-type enumerations) down to a one-line prompt like 'assess coverage across domains, workflow stages, and file types' — Claude can generate these categories itself; keep only the gap-assessment criteria (Impact/Availability/Complexity/Priority), which are the skill's real value.

Add one worked example: a single sample inventory entry and one model recommendation (e.g., a Critical Gap with workflow, frequency, impact, and suggested skill name) so the output format is demonstrated rather than just described.

If the taxonomy detail is considered valuable, move it to a references/coverage-categories.md file and link it from Step 2, keeping SKILL.md as a lean overview — this would also raise the progressive_disclosure score.

DimensionReasoningScore

Conciseness

Roughly 100 of the ~200 lines enumerate domain/workflow/file-type taxonomies ("Document processing (word docs, PDFs, presentations)... Creative (design, content creation, media)") that Claude already knows and could generate unprompted — several padded sections restating common knowledge. It is not a 3 because the padding is systematic across Steps 2 and 3 rather than isolated, and not a 1 because there is no tutorial-style explanation of concepts.

2 / 5

Actionability

The five steps and the Output Format section give real structure, but there are no worked examples: no sample inventory entry, no example gap assessment, and no model recommendation to imitate. This matches anchor 3 ('some concrete guidance but incomplete; missing key details') — more than high-level hints (anchor 2) but lacking the concrete instances that would make it executable (anchor 4).

3 / 5

Workflow Clarity

A clear numbered five-step sequence with per-step criteria (Impact/Availability/Complexity/Priority; Complementary/Redundant/Partially redundant) and a defined output structure. Minor validation gap: no checkpoint to verify findings against the user's actual history beyond the general 'ask clarifying questions' note — anchor 4 rather than 5. The destructive/batch cap does not apply since this is a read-only analysis skill.

4 / 5

Progressive Disclosure

Good section headers and a coherent single-file layout, but the ~100-line workflow-category taxonomies in Steps 2-3 are exactly the reference material that belongs in a separate file, and the body is well over the ~50-line threshold where a single well-organized file would suffice. Matches anchor 3 ('some structure but... content that should be separate is inline') rather than 4, where most content would be appropriately placed.

3 / 5

Total

12

/

20

Passed

Description

95%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 strong description: third-person, concise, with an explicit 'Use when' clause and quoted natural trigger phrases covering multiple synonyms. The only soft spot is that the capability verbs are analytical abstractions rather than concrete operations, which is partly inherent to a meta-analysis skill.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ("identify coverage gaps, redundant overlaps, and optimization opportunities"), but verbs like "identify gaps" are one step more abstract than anchor-5 examples such as "extract text... fill forms... merge documents"; not a 5 because the actions describe analysis outcomes rather than concrete operations, and not a 3 because multiple distinct actions are explicitly listed.

4 / 5

Completeness

Explicitly answers both: what ("Analyzes the user's skill library to identify coverage gaps, redundant overlaps, and optimization opportunities") and when ("Use when users want to..." plus "Triggered by requests like...") with concrete trigger phrases — a direct match to the anchor-5 example structure. Not a 4 because the 'when' clause is fully explicit, not merely present.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms ("skill library," "skill ecosystem," "skill collection") plus four quoted user-voice phrases ("analyze my skills," "what skills am I missing," "are any of my skills redundant," "optimize my skill library"). This matches the anchor-5 pattern of covering natural terms and variations; anchor 4's 'a few natural terms missing' would understate the four quoted phrases plus the 'Use when' variations.

5 / 5

Distinctiveness Conflict Risk

A clear meta-niche (analyzing the skill library itself) with distinct quoted triggers; phrases like "what skills am I missing" would not plausibly fire a document- or data-processing skill. Slight generic risk from the word "optimize" is neutralized by the skill-scoped object ("my skill library"), keeping it at anchor 5 rather than 4.

5 / 5

Total

19

/

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
freightCognition/linehaulai-claude-marketplace
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.