CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hidden-skill

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

Quality

76%

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/hidden-skill/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 maximally lean and appropriately self-contained for a single-purpose skill, with the token payload provided inline. Its main weakness is that the single instruction depends on an undefined destination (`markers`), which leaves the one action partially ambiguous.

Suggestions

Define the destination for `markers` (e.g., "append the token to the `markers` file in the working directory" or "output the token under a `markers` heading"), so the copy instruction is unambiguous and executable.

State when the copy action applies relative to the trigger (e.g., "When asked to report skill markers, respond with the token below") to make the single workflow fully self-explanatory.

DimensionReasoningScore

Conciseness

The body is two lean sentences — "This skill carries the token MARKER-SKILL-HIDDEN. Copy it into `markers`." — with the concrete payload inlined and zero padding. Every token earns its place, matching the anchor 'Lean and efficient; assumes Claude's competence'.

5 / 5

Actionability

"Copy it into `markers`" is a concrete instruction with the actual token provided, but the destination `markers` is undefined (a file? a field? a directory?), so key execution details are missing. It is not 4 because the undefined destination blocks copy-paste readiness, and not 2 because the instruction is specific and the payload is given inline.

3 / 5

Workflow Clarity

This is a simple single-task skill and its one action is stated directly, so sequence is trivially clear and no destructive/batch validation cap applies. It is not 5 because the single action is not fully unambiguous — copying into `markers` leaves the destination underspecified.

4 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained, needs no external references, and no bundle files (references/, scripts/, assets/) exist. Per the simple-skill guidance, a well-organized self-contained body matches the top anchor for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

61%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 answers both what and when with an explicit, distinctive trigger phrase, giving it low conflict risk and acceptable completeness. However, the stated capability ("Carries a marker token") is vague about what the skill actually does for the user, and the keyword coverage lacks natural variations.

Suggestions

Replace the vague "Carries a marker token" with the concrete action the skill performs (e.g., "Returns its marker token for skill-reporting audits"), so the what describes a real capability.

Broaden trigger keywords with natural phrasings and synonyms users would actually say, such as "list skill markers", "report skill tokens", or "skill audit markers", to improve trigger coverage beyond the single phrase "report the markers of your skills".

DimensionReasoningScore

Specificity

"Carries a marker token. Load it" names the domain (marker tokens) but the actions are minimal and generic — "carries" and "load" are not concrete capability actions, matching the anchor 'Names the domain but actions are minimal or generic'. It falls short of 3 because no 1-2 genuinely concrete actions are described.

2 / 5

Completeness

Both parts are present: a what ("Carries a marker token") and an explicit when ("Load it when asked to report the markers of your skills"). It is not 5 because the what is vague about the actual capability provided, and not 3 because the when is explicitly stated rather than missing or weakly implied.

4 / 5

Trigger Term Quality

"marker", "token", and "report the markers of your skills" provide some relevant keywords and an explicit trigger phrase, but natural variations and synonyms users might say are missing. It is not 4 because keyword coverage is thin, and not 2 because the keywords present are domain-relevant rather than generic.

3 / 5

Distinctiveness Conflict Risk

"report the markers of your skills" is a highly distinctive niche trigger unlikely to overlap with any other skill's description. This matches the anchor 'Clear niche with distinct triggers; minimal conflict risk' with no plausible overlap risk.

5 / 5

Total

14

/

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