Tessl • The package manager for agent skills

Blog Docs Log inGet started

SkillPublic

foo

Main foo skill.

Quality

26%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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-main/foo/SKILL.md

Quality

Content

18%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 effectively empty — a single heading with no instructions, examples, workflow, or referenced materials. Invoking this skill would give Claude no guidance whatsoever about what to do. Structure exists in name only; there is no content to be concise, actionable, or well-organized.

Suggestions

Add core instruction content under the heading: concrete steps or executable code/commands for the skill's task.

If the task is multi-step or destructive/batch, sequence the steps explicitly and include validation checkpoints.

State what the skill does at the top so SKILL.md serves as a real overview, and add reference files (clearly signaled, one level deep) only when detail warrants splitting out.

Dimension	Reasoning	Score
Conciseness	The body is only "# Foo (Main)" — zero padding or over-explanation, but this brevity preserves no clarity since no guidance exists at all. The low anchors describe verbosity (absent here) while the top anchor presumes real content delivered efficiently, so it lands mid-scale.	3 / 5
Actionability	No code, commands, or instructions of any kind appear in the body; it matches anchor 1 ("Entirely vague or abstract; no concrete code or commands") — the body doesn't even describe a task, so it cannot reach 2's "high-level hints".	1 / 5
Workflow Clarity	No steps, sequence, or checkpoints exist — a single heading with nothing under it matches anchor 1 ("Steps missing or incoherent; no sequence"). Anchor 2 requires at least a rough sequence, which is absent.	1 / 5
Progressive Disclosure	A bare heading provides minimal structure with no overview content and no references (no references/, scripts/, or assets/ bundle files exist). It matches anchor 2 ("Minimal structure"); it avoids 1 only because nothing is buried or deeply nested, but a lone empty heading is not the "well-organized sections" needed for 3+.	2 / 5
	Total	7 / 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-level failure: it names no domain, no actions, no trigger conditions, and no use cases. It provides no signal for a model to decide when to invoke it and no way to distinguish it from other skills.

Suggestions

State 2-4 concrete capabilities in third person (e.g., "Processes X files, generates Y reports, validates Z").

Add an explicit trigger clause: "Use when the user mentions <domain terms, tasks, or file extensions>." — without one, completeness is capped.

Replace the placeholder "foo" with the real domain name plus natural synonyms and file extensions so the skill is distinct and discoverable.

Dimension	Reasoning	Score
Specificity	"Main foo skill." states no concrete action and no real domain — "foo" is a placeholder — matching anchor 1 ("Entirely vague; no concrete actions; pure abstract language"). It cannot reach 2 because it doesn't even name a genuine domain like "Processes PDF files" does.	1 / 5
Completeness	Both parts fail: the "what" ("Main foo skill.") is so vague it conveys no function, and the "when" is entirely absent — matching anchor 1 ("Missing both what and when, or both are extremely vague"). Anchor 2's pattern of a vague-but-present "what" doesn't apply since "foo" identifies nothing.	1 / 5
Trigger Term Quality	The description contains no natural keywords a user would say; "foo" is a placeholder term, not a real trigger. This matches anchor 1 ("No natural keywords; only technical jargon or entirely generic language") and cannot reach 2 because there isn't even one generic relevant keyword.	1 / 5
Distinctiveness Conflict Risk	"Main foo skill." is entirely generic and distinguishes this skill from nothing; it would conflict with virtually any similarly named skill. This matches anchor 1, and no anchor above fits because no domain or distinctive trigger is named.	1 / 5
	Total	4 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
description_field	'description' is very short (15 chars), consider making it more detailed	Warning

	Total	15 / 16 Passed

Repository: can1357/oh-my-pi
Path: packages/coding-agent/test/fixtures/skills-collision/tilde-main/foo/SKILL.md
Revision: eb74cf8

Reviewed: 11 days ago

Discovery Implementation Validation

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.

foo

Table of Contents

Is this your skill?