folded-desc-skill

A fixture whose description uses a YAML folded scalar, which parses with an embedded trailing newline unless normalized before use in Markdown tables.

Quality

30%

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 ./cli/platform/emit/__fixtures__/repo/.agents/skills/folded-desc-skill/SKILL.md

Quality

Content

26%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 body is essentially empty — just a title — so it is token-efficient but provides no actionable guidance, workflow, or navigable structure. As a fixture this is intentional, but against the rubric it scores at the floor on actionability and workflow clarity.

Suggestions

Add a brief body section stating the single action the skill performs (e.g. how to normalize a folded-scalar description), with one concrete code or command example, to lift actionability above 1.

If the skill is genuinely single-purpose, include a one-step workflow with an explicit validation checkpoint (e.g. assert no trailing newline remains) so workflow clarity reflects a real process.

Either organize the minimal content under clear section headers or, if detail is needed, add a one-level-deep reference file with a signaled link, to give the body navigable structure.

Dimension	Reasoning	Score
Conciseness	The body is a single heading with no padding, unnecessary explanation, or restatement of concepts Claude already knows, so it is efficient. It is not a 5 because a near-empty body provides no lean, useful content — it is merely absent rather than meaningfully efficient.	4 / 5
Actionability	The body contains only '# Folded Description Skill' with no concrete code, commands, or executable guidance, matching the 'entirely vague or abstract; no concrete code or commands' anchor. There is nothing below this level.	1 / 5
Workflow Clarity	There are no steps, sequence, or validation checkpoints whatsoever — the 'steps missing or incoherent; no sequence' anchor. No destructive or batch operation is present, so the cap does not apply, but the absence of any process leaves it at the floor.	1 / 5
Progressive Disclosure	No bundle directories exist and the body has only a heading with no sections, structure, or references, fitting 'minimal structure'. It is above score 1 (not a monolithic wall of text or nested references) but well below the organized-sections standard expected even for a simple skill.	2 / 5
	Total	8 / 20 Passed

Description

33%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.

This is a fixture description focused on its own YAML mechanics rather than user-facing capability; it has a clear 'what' but no trigger guidance and only technical jargon. It scores moderately on distinctiveness and completeness but low on trigger-term quality and specificity.

Suggestions

Rewrite the description in third person around a concrete capability (e.g. 'Normalizes YAML folded-scalar descriptions before inserting them into Markdown tables') so it states actions a user would invoke.

Add a 'Use when...' clause with natural trigger phrases users actually say, such as 'Use when rendering skill descriptions in Markdown tables or normalizing folded-scalar frontmatter'.

Replace technical-only terms with user-facing synonyms (e.g. add 'description field', 'frontmatter', 'table cell') so the description surfaces on natural requests, not just YAML jargon.

Dimension	Reasoning	Score
Specificity	The description names a domain ('YAML folded scalar', 'embedded trailing newline', 'Markdown tables') but lists no concrete actions a user would invoke, reading as a statement about the fixture rather than capabilities. It is not entirely vague (score 1) but offers only minimal, generic action content.	2 / 5
Completeness	It states a clear 'what' (the fixture uses a folded scalar that embeds a trailing newline) but provides no 'Use when...' or equivalent trigger guidance, so per the rubric a missing 'when' clause caps completeness at 3. It is above score 2 because the 'what' is explicit, and not at 4 because no 'when' is present at all.	3 / 5
Trigger Term Quality	The only terms present ('YAML folded scalar', 'trailing newline', 'normalized', 'Markdown tables') are technical jargon; none are natural phrases a user would say when they need this skill. It matches the 'only technical jargon' anchor and is below the 'one or two generic keywords' level of score 2.	1 / 5
Distinctiveness Conflict Risk	The description targets a narrow, meta-level niche (folded-scalar newline handling in Markdown tables) and would rarely collide with other skills. It is not a score 5 because it lacks concrete distinct trigger phrases, but it is clearly more distinct than the broad-overlap examples at score 3.	4 / 5
	Total	10 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: first-fluke/oh-my-agent
Path: cli/platform/emit/__fixtures__/repo/.agents/skills/folded-desc-skill/SKILL.md
Commit: ce19702

Reviewed: 4 days ago

Table of Contents

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.