body-501-lines

Body with exactly 501 lines, one over the warn boundary.

Quality

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

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 is a 501-line filler fixture with no instructional content whatsoever: nothing actionable, no workflow, and no organization. Every dimension sits at the floor of the scale.

Suggestions

Replace filler lines with lean, capability-relevant guidance that assumes Claude's competence.

Provide concrete, executable code or commands covering the common cases.

If the skill is multi-step, sequence the steps explicitly with validation checkpoints, and split bulk detail into one-level-deep reference files.

Dimension	Reasoning	Score
Conciseness	The body is 501 near-identical filler lines ("Line N does a thing.") with no informational content, matching the severely verbose / heavily padded anchor; there is no signal to tighten, so it cannot reach anchor 2.	1 / 5
Actionability	"does a thing" is pure abstraction — no code, commands, or specific steps anywhere, exactly the entirely-vague anchor.	1 / 5
Workflow Clarity	No sequence, steps, or validation of any kind exist; the enumerated lines are filler, not a workflow, matching the lowest anchor.	1 / 5
Progressive Disclosure	The body is a monolithic wall of text with no headers, no sections, and no references (no bundle files exist to point to), matching the lowest structure anchor.	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 documents a test fixture's line count rather than a skill's capabilities, offering no actions, no trigger terms, and no use-when guidance. It would never surface for a real user request.

Suggestions

State concrete capabilities in third person (e.g., what task the skill performs), replacing the line-count meta commentary.

Add an explicit "Use when..." clause with natural trigger phrases users would actually say.

Include distinguishing keywords (domain terms, file extensions) so the description is identifiable against other skills.

Dimension	Reasoning	Score
Specificity	"Body with exactly 501 lines, one over the warn boundary" names a concrete meta-fact about file structure but describes no user-facing capability or action, matching the anchor for naming a domain with minimal or generic actions.	2 / 5
Completeness	There is no 'Use when...' clause or equivalent trigger guidance (capping at 3 per guidelines), and the stated 'what' describes the file's line count rather than what the skill does, fitting the vague-'what'/no-'when' anchor.	2 / 5
Trigger Term Quality	No natural keywords a user would say when needing this skill; "warn boundary" is internal jargon and the rest is generic, matching the lowest anchor rather than the one-or-two-generic-keywords anchor.	1 / 5
Distinctiveness Conflict Risk	The description conveys no domain, niche, or distinguishing triggers; it is not anchor 1's would-conflict-with-everything generic, but it is far from anchor 3's "somewhat specific," leaving it at the bottom boundary.	2 / 5
	Total	7 / 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
skill_md_line_count	SKILL.md is long (505 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-501-lines/SKILL.md
Commit: a1083f4

Reviewed: 2 hours 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.