CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

foo

Second foo-tilde skill.

28

Quality

35%

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 ./packages/coding-agent/test/fixtures/skills-collision/tilde-third/foo/SKILL.md

The canonical home for this skill is foo~2 in can1357/oh-my-pi

SKILL.md
Quality
Evals
Security

Quality

Content

37%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 content is an empty stub: a lone heading with no actionable guidance, workflow, or structure. While it wastes no tokens, it delivers no value — Claude reading this skill would learn nothing about how to perform the task. The body needs actual instructions to function as a skill.

Suggestions

Add the core instructions for the skill's single task — concrete commands, code, or specific directive guidance — so the body is actionable rather than a bare title.

If the task involves multiple steps, sequence them explicitly with validation checkpoints before any destructive or batch operation.

Keep the existing leanness: a short, well-organized set of sections (or a brief overview pointing to real bundle files) would satisfy progressive disclosure.

DimensionReasoningScore

Conciseness

The body is a single heading ("# Foo~2 (Second)") with no padding, no explanation of known concepts, and no wasted tokens — lean to the point of being empty. Nothing here could be trimmed, so the conciseness anchors are fully met (the emptiness problem is captured by other dimensions).

5 / 5

Actionability

The body provides no instructions, commands, code, or even a description of what to do — it is a bare title. This falls below even the "only describes rather than instructs" anchor, as there is nothing executable or directive at all.

1 / 5

Workflow Clarity

No steps, sequence, or checkpoints of any kind exist — the body contains only a heading. The anchor-1 fit ("steps missing or incoherent; no sequence") is exact.

1 / 5

Progressive Disclosure

There is no monolithic content, no inlined material that belongs in separate files, and no (bundle) references to mis-nest, but there are also no organized sections or overview — a single bare heading does not constitute the "well-organized sections" required for the simple-skill exception to reach 5.

3 / 5

Total

10

/

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 is a placeholder with no informative content: it names no domain, no actions, no trigger terms, and no use conditions. It matches the bad-overall-example tier ("Helps with documents", "Does stuff with files") and needs a complete rewrite describing concrete capabilities and "Use when..." triggers.

Suggestions

State 2-4 concrete capabilities in third person (e.g., what the skill actually does with foo-tilte inputs), replacing the placeholder "Second foo-tilde skill."

Add an explicit "Use when..." clause listing the natural phrases, file types, or task contexts in which users would invoke this skill.

Include distinguishing trigger terms (synonyms, file extensions, related tools) so the skill is clearly differentiated from similar skills and fires only for the right tasks.

DimensionReasoningScore

Specificity

"Second foo-tilde skill." contains no concrete actions and no real domain — it is pure abstract labeling, matching the "Helps with documents" level of vagueness. Anchor 2 requires at least a named domain with minimal actions, which this does not provide.

1 / 5

Completeness

Neither "what does this do" nor "when should Claude use it" is answered; "foo-tilde skill" conveys no capability information, so both what and when are effectively missing. There is no "Use when..." clause, well below the completeness cap of 3.

1 / 5

Trigger Term Quality

There are no natural keywords or phrases a user would say when needing this skill — "foo-tilde" is a placeholder token, not a task-domain term. Even the anchor-2 level of one or two generic keywords is absent.

1 / 5

Distinctiveness Conflict Risk

The description provides zero capability information, making it indistinguishable from any other skill and useless for routing decisions. It would not reliably trigger for any task, which is the worst case for conflict/distinctiveness.

1 / 5

Total

4

/

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

can1357/oh-my-pi

Path

packages/coding-agent/test/fixtures/skills-collision/tilde-third/foo/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.