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/plain/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 is an empty shell: a single heading with no instructions, examples, workflow, or references. Its only virtue is that it wastes no tokens; on every substantive dimension it sits at or near the bottom anchor.

Suggestions

Add actual instructional content beneath the heading — the body currently provides no guidance at all.

Include at least one concrete, executable example or command covering the skill's common case.

If the task involves any sequence, list the steps explicitly with a validation checkpoint; if it is single-purpose, state the one action unambiguously.

DimensionReasoningScore

Conciseness

The body is a single heading ('# Overlay fixture') with zero padding and zero explanation of concepts Claude already knows — nothing could be trimmed, matching 'Lean and efficient; every token earns its place'. Not a 4 because that anchor requires 'minor instances of over-explanation that could be trimmed', and there are none.

5 / 5

Actionability

The body contains no code, commands, or guidance of any kind — only a title — matching 'Entirely vague or abstract; no concrete code or commands; only describes rather than instructs' (it does not even describe). Not a 2 because there are no high-level hints toward execution either.

1 / 5

Workflow Clarity

No steps or sequence exist anywhere in the body ('# Overlay fixture' and nothing more), matching 'Steps missing or incoherent; no sequence'. The simple-skill exception does not apply because no single action is identified, let alone unambiguous.

1 / 5

Progressive Disclosure

The body is a bare heading with no sections, no overview content, and no navigation — literally 'minimal structure'. Not a 1 because it is neither a monolithic wall of text nor a set of nested references; not a 3 because that anchor presumes sections or references that merely need better organization, and there is nothing to organize. No bundle files exist (references/, scripts/, and assets/ are absent), so there are no referenced paths to verify.

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 placeholder label rather than a skill description: it names no capabilities, no domain, no triggers, and no use context. It matches the lowest anchor on all four dimensions.

Suggestions

Replace 'Overlay fixture' with third-person capability statements naming the domain and concrete actions the skill performs.

Add an explicit 'Use when...' clause with natural trigger phrases, synonyms, and relevant file extensions that users would actually say.

State the specific artifacts or tasks the skill handles so it is distinguishable from other skills and unlikely to trigger for the wrong one.

DimensionReasoningScore

Specificity

The description 'Overlay fixture' names no domain and no concrete actions — it is a bare label, matching 'Entirely vague; no concrete actions; pure abstract language' ('Helps with documents'). Not a 2 because that anchor requires naming a domain with minimal or generic actions (e.g., 'Processes PDF files'), which even this does not do.

1 / 5

Completeness

Neither 'what does this do' nor 'when should Claude use it' is addressed — 'Overlay fixture' describes no capability and includes no 'Use when...' clause or equivalent, matching 'Missing both what and when, or both are extremely vague'. The missing-trigger cap of 3 is not reached because the 'what' is itself absent.

1 / 5

Trigger Term Quality

'Overlay fixture' contains no natural keywords a user would say when needing this skill; it is meta-jargon about the artifact's role, matching 'No natural keywords; only technical jargon or entirely generic language'. Not a 2 because even 'one or two generic keywords' are absent.

1 / 5

Distinctiveness Conflict Risk

The description states no capability and no domain, making it indistinguishable from virtually any other skill and likely to trigger wrongly, matching 'Entirely generic; would conflict with virtually any skill'. Not a 2 because even 'very broad; high overlap risk' (e.g., 'Helps with document files') presupposes some stated domain.

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/plain/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.