CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

visible-skill

Carries a marker token. Load it when asked to report the markers of your skills.

Quality

80%

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/workspace/cases/workspaces/agent_e2e_workspace/.claude/skills/visible-skill/SKILL.md
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, single-purpose skill that states its token and gives one direct, executable instruction. The only weakness is that the `markers` destination is assumed rather than defined.

DimensionReasoningScore

Conciseness

The body is two sentences — "This skill carries the token MARKER-SKILL-VISIBLE. Copy it into `markers`." — with no padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

"Copy it into `markers`" is a concrete instruction with a literal token value, but the destination `markers` is never defined (a file? a field? an output format?), leaving a minor gap versus fully copy-paste-ready guidance.

4 / 5

Workflow Clarity

This is a single-action skill and the one step — copy MARKER-SKILL-VISIBLE into `markers` — is unambiguously stated; no destructive or batch operations exist that would require validation checkpoints, so the simple-skill exception applies.

5 / 5

Progressive Disclosure

The body is one line with no external references needed; no bundle directories (references/, scripts/, assets/) exist and none are referenced, so nothing is inlined or nested — the under-50-lines exception applies.

5 / 5

Total

19

/

20

Passed

Description

57%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 has an explicit and natural "when" clause and occupies a distinct niche, but the capability statement is minimal ("Carries a marker token") and trigger coverage is a single phrase with no variations. It is functional but under-specified relative to the good examples.

Suggestions

Replace the minimal "Carries a marker token" with a concrete capability statement, e.g., "Provides the token MARKER-SKILL-VISIBLE for inclusion in a markers report."

Broaden trigger coverage with natural variations users might say, such as "list your skill markers" or "show which marker skills are loaded".

Make the "what" half as explicit as the "when" half by stating what the token is used for (what the resulting "markers" output is).

DimensionReasoningScore

Specificity

"Carries a marker token" names the domain but describes only a single minimal state rather than concrete actions, matching the "Processes PDF files" anchor; it lacks the 1-2 concrete actions needed for anchor 3.

2 / 5

Completeness

Both halves are present — what ("Carries a marker token") and when ("Load it when asked to report the markers of your skills") — but the "what" is thin: it never says what the token is for or what to do with it, so it falls short of the fully explicit anchor 5 while clearly exceeding the missing-when anchor 3.

4 / 5

Trigger Term Quality

"report the markers of your skills" is a relevant natural phrase and "marker token" is on-topic, but there are no synonyms or common variations (e.g., "list markers", "which skills are visible"), fitting the "some relevant keywords but missing variations" anchor.

3 / 5

Distinctiveness Conflict Risk

The marker-token niche with its distinct trigger is unlikely to collide with ordinary skills, but the generic trigger "report the markers of your skills" would match any sibling marker-carrying skill, giving minor overlap risk with closely related skills rather than the minimal conflict of anchor 5.

4 / 5

Total

13

/

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

dlt-hub/dlt

Path

tests/workspace/cases/workspaces/agent_e2e_workspace/.claude/skills/visible-skill/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.