CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

multiline-description

This is a multiline description. It spans multiple lines. And should be normalized.

30

Quality

38%

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/multiline-description/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

47%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 concise but provides no actionable guidance — it states a single descriptive fact with no instructions, steps, or examples. As a test fixture it is benign, but as a skill body it cannot be executed against. Structure is trivially clean since there is almost no content.

Suggestions

Add concrete guidance for the single action the skill performs (e.g., the exact normalization rule: join lines with spaces, strip trailing/leading whitespace, escape as needed) so the body instructs rather than describes.

Include a short before/after example of a multiline description and its normalized single-line result to make the expected behavior unambiguous.

State when to apply the normalization (e.g., 'Run on SKILL.md frontmatter before publishing') to give the simple workflow a clear trigger and checkpoint.

DimensionReasoningScore

Conciseness

The body is a single heading and one sentence — 'This skill tests that multiline YAML descriptions are normalized to single lines.' — with zero padding and no explanations of concepts Claude already knows. Every token earns its place, matching anchor 5.

5 / 5

Actionability

The body only describes the skill's purpose ('This skill tests that...') rather than instructing how to do anything; there is no code, command, or concrete step. This matches anchor 1 ('only describes rather than instructs').

1 / 5

Workflow Clarity

No sequence or actionable steps are present at all, though there are no destructive or batch operations that would require validation. This lands between anchor 1 ('steps missing; no sequence') and anchor 2, noticeably below the midpoint.

2 / 5

Progressive Disclosure

At under 50 lines with no external references needed, nothing is inlined that belongs in a separate file — but the body has no organized sections beyond a single heading, leaving it just short of the well-organized-structure bar for a 5.

4 / 5

Total

12

/

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 placeholder/test-fixture text that describes its own formatting rather than any capability. It fails all four dimensions: no concrete actions, no trigger terms, no 'what' or 'when', and no distinctiveness. A complete rewrite is needed.

Suggestions

Replace the meta-text with concrete capability statements in third person (e.g., what the skill actually does, such as 'Normalizes multiline YAML frontmatter descriptions into single-line form').

Add an explicit 'Use when...' clause with natural trigger phrases users would say (e.g., 'Use when a SKILL.md description spans multiple lines and must be flattened to one line').

Include domain-specific keywords and file references (e.g., SKILL.md, YAML frontmatter, description field) so the skill is distinguishable from other skills and triggers reliably.

DimensionReasoningScore

Specificity

The description states only 'This is a multiline description. It spans multiple lines. And should be normalized.' — no concrete actions or working domain are named, matching the 'entirely vague; no concrete actions' anchor. It does not even rise to anchor 2, which requires naming a domain.

1 / 5

Completeness

Neither a 'what' (no capability described) nor a 'when' (no trigger clause) is present; the text is purely self-referential. Per the guidelines, the missing 'Use when...' clause would alone cap completeness at 3.

1 / 5

Trigger Term Quality

It contains no natural keywords or technical terms a user would say when needing this skill — only meta-commentary about its own formatting. This matches anchor 1 ('No natural keywords; only technical jargon or entirely generic language').

1 / 5

Distinctiveness Conflict Risk

'It spans multiple lines. And should be normalized.' is entirely generic meta-text with no distinguishing triggers, so it would conflict with virtually any skill — anchor 1.

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

Kiz8-Team/pi-cwl

Path

packages/coding-agent/test/fixtures/skills/multiline-description/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.