CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill

Overlay fixture

Quality

32%

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 ./tests/fixtures/kits/overlay/extends-on-10/SKILL.md

The canonical home for this skill is skill in constructorfabric/studio

SKILL.md
Quality
Evals
Security

Quality

Content

33%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 consists solely of a heading, so it is maximally token-efficient but contains no actionable guidance, no workflow, and no meaningful structure — it is a placeholder rather than a usable skill. Its one strength (zero waste) is inseparable from its core failure: there is no content to waste.

Suggestions

Add the actual instruction content under the heading — concrete, executable guidance (commands, code, or specific steps) for the task the skill performs.

If the task is multi-step or involves batch/destructive operations, lay out a numbered sequence with explicit validation checkpoints and a fix-and-retry loop.

Organize the content into well-labeled sections and split detailed material into one-level-deep reference files under references/ with clearly signaled links.

DimensionReasoningScore

Conciseness

The body is a single heading ("# Overlay fixture") with zero padding and no explanations of concepts Claude already knows, matching anchor 5 ("Lean and efficient; assumes Claude's competence; every token earns its place") in the vacuous sense — there is nothing wasted. It is not 4 because there are no instances of over-explanation to trim.

5 / 5

Actionability

The body contains no concrete guidance, code, commands, or even an abstract instruction — only the title "Overlay fixture" — matching anchor 1 ("Entirely vague or abstract; no concrete code or commands; only describes rather than instructs"); it does not even describe. It is not 2 because anchor 2 requires high-level hints toward steps, and none exist.

1 / 5

Workflow Clarity

No steps or sequence of any kind are present, matching anchor 1 ("Steps missing or incoherent; no sequence; no validation for risky operations"). It is not 2 because anchor 2 requires at least a rough sequence; the simple-skill exception does not apply because there is no unambiguous single action — the action content is entirely absent.

1 / 5

Progressive Disclosure

The body is a bare heading with no sections, overview, or navigation, and no bundle files exist (no references/, scripts/, or assets/ directories), matching anchor 2 ("Minimal structure"). It is not 1 because there is no monolithic text wall or nested references, and not 3 because there are no sections or references at all to organize.

2 / 5

Total

9

/

20

Passed

Description

0%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 "Overlay fixture" is a two-word placeholder that names no capabilities, no domain, no triggers, and no use cases, scoring the minimum on all four dimensions. It reads as an internal test-fixture label rather than a skill description, giving users and Claude no way to know what it does or when to invoke it.

Suggestions

Replace "Overlay fixture" with a third-person description of concrete actions, e.g., "Overlays X onto Y to produce Z" — name what the skill actually does.

Append an explicit "Use when..." clause listing natural trigger phrases a user would say, plus relevant file extensions or synonyms.

State the specific domain and distinguishing triggers so the skill cannot be confused with other similar skills.

DimensionReasoningScore

Specificity

The description is the two-word noun phrase "Overlay fixture" with no action verbs ("Processes", "Extracts") or concrete capabilities, matching anchor 1 ("Entirely vague; no concrete actions; pure abstract language") even more strongly than the "Helps with documents" example. It is not 2 because it does not even name a domain of action — "overlay fixture" is unexplained internal jargon.

1 / 5

Completeness

Neither "what" (an unexplained noun phrase describes nothing the skill does) nor "when" (no "Use when..." or equivalent trigger guidance) is present, matching anchor 1. It is not 2 because anchor 2 requires at least a vague "what" or a "when" — here both are entirely absent.

1 / 5

Trigger Term Quality

"Overlay fixture" contains no natural keywords a user would say when they need this skill; it is purely internal jargon, matching anchor 1 ("No natural keywords; only technical jargon or entirely generic language"). It is not 2 because there are not even one or two generic keywords like "files" — the phrase has no user-facing vocabulary at all.

1 / 5

Distinctiveness Conflict Risk

"Overlay fixture" gives no basis to distinguish this skill from any other and would conflict with virtually any skill, matching anchor 1. It is not 2 because anchor 2 still requires a broad stated domain (e.g., "Helps with document files") and even that is missing.

1 / 5

Total

4

/

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

description_field

'description' is very short (15 chars), consider making it more detailed

Warning

Total

15

/

16

Passed

Repository

constructorfabric/studio

Path

tests/fixtures/kits/overlay/extends-on-10/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.