CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

body-500-lines

Body with exactly 500 lines, at the no-warn boundary.

20

Quality

26%

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 ./crates/skill-validator-rs/tests/golden-corpus/fixtures/boundary/body-500-lines/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

0%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 consists entirely of placeholder filler ("Line N does a thing.") with no structure, guidance, code, or references — it is untriggerable as a set of instructions. It scores at the floor on every dimension because it contains no instruction content whatsoever.

Suggestions

Replace the filler lines with concise, actionable instructions or executable code covering the skill's actual task.

Add section headers (e.g., a quick-start section) to give the body navigable structure, and move bulk detail to one-level-deep reference files if needed.

If any multi-step or batch operation is involved, sequence the steps explicitly and include validation checkpoints.

DimensionReasoningScore

Conciseness

The body is 500 repetitions of "Line N does a thing." — pure padding with zero information value, the most severely verbose case the anchor describes ('heavily padded', nothing Claude doesn't already know or nothing at all).

1 / 5

Actionability

"Line 0 does a thing." through "Line 499 does a thing." are entirely abstract placeholders; there is no concrete code, command, or specific instruction anywhere, matching the lowest anchor ('only describes rather than instructs' — and here it barely even describes).

1 / 5

Workflow Clarity

There is no sequence, no steps, and no validation of any kind; the numbered lines are filler indices, not a workflow, matching the 'steps missing or incoherent' anchor.

1 / 5

Progressive Disclosure

A 500-line monolithic block with no section headers, no navigation, and no references (no bundle files exist to link to) matches the 'monolithic wall of text with no structure; impossible to navigate' anchor; it is far beyond the 300-line no-headers case at anchor 2.

1 / 5

Total

4

/

20

Passed

Description

17%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 describes the artifact (a 500-line body at a linting boundary) rather than any capability, trigger, or use case. It answers neither 'what does this skill do' nor 'when should Claude use it' in any user-relevant sense.

Suggestions

State the skill's actual capabilities as concrete third-person actions (e.g., what task it performs), not meta-facts about the file's line count.

Add an explicit 'Use when...' clause with natural trigger phrases a user would actually say.

Include domain keywords and synonyms (and file extensions if applicable) so the skill is discoverable and distinguishable from other skills.

DimensionReasoningScore

Specificity

"Body with exactly 500 lines, at the no-warn boundary" states a literal fact about the file but names no task domain and no capability actions; it is not the pure-abstraction anchor (its language is concrete), yet it delivers nothing actionable, matching the 'names the domain but actions are minimal or generic' level.

2 / 5

Completeness

There is a vague 'what' (a line count, which says nothing about what the skill does for a user) and no 'when' clause whatsoever, matching the 'vague what and no when' anchor; it is above anchor 1 only because the 'what' is at least explicitly stated.

2 / 5

Trigger Term Quality

"exactly 500 lines" and "no-warn boundary" are meta/technical jargon that no user would naturally say when needing a skill; there are no natural keywords at all, matching the lowest anchor.

1 / 5

Distinctiveness Conflict Risk

The description avoids overlap with other skills only because it matches nothing a user would ever say; it carves no recognizable capability niche, so it provides no distinct routing identity.

2 / 5

Total

7

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (504 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

pantheon-org/tekhne

Path

crates/skill-validator-rs/tests/golden-corpus/fixtures/boundary/body-500-lines/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.