oversized-skill

A skill whose body deliberately exceeds the 500-line recommendation.

Quality

10%

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/oversized-skill/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 purely filler content with no instructional, structural, or navigational value across every dimension. It is the canonical anti-pattern of an oversized, content-free SKILL.md body.

Suggestions

Replace the filler lines with a concise overview of the skill's purpose and the concrete actions it performs.

Move any extended detail into one-level-deep reference files under references/ and link to them with clearly signaled pointers, keeping SKILL.md as a lean overview.

Add executable examples or a sequenced workflow with validation checkpoints appropriate to the skill's task.

Dimension	Reasoning	Score
Conciseness	The body is 550 lines of identical filler ('Line N of filler content.') with no informational value, the most severe form of padding and token waste, matching the 'severely verbose; heavily padded' anchor.	1 / 5
Actionability	There is no concrete guidance, code, or commands anywhere — only repeated placeholder lines — so the content entirely describes/instructs nothing, matching the 'entirely vague or abstract; no concrete code or commands' anchor.	1 / 5
Workflow Clarity	No steps, sequence, or validation checkpoints exist; the body is undifferentiated filler, matching the 'steps missing or incoherent; no sequence; no validation' anchor.	1 / 5
Progressive Disclosure	The body is a monolithic wall of filler text with no structure, section headers (beyond a single H1), or references, and no bundle files exist, matching the 'monolithic wall of text with no structure; impossible to navigate' anchor.	1 / 5
	Total	4 / 20 Passed

Description

21%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 meta commentary about the skill's size rather than a statement of capability, providing no concrete actions, no natural trigger terms, and no usage guidance. It is distinguishable only by its unusual self-referential phrasing, not by a functional niche.

Suggestions

Rewrite the description to state concrete capabilities the skill performs (e.g., specific actions on specific inputs) instead of describing the skill's own line count.

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

Include relevant keywords, synonyms, and file extensions that users would naturally invoke to trigger the skill.

Dimension	Reasoning	Score
Specificity	The description ('A skill whose body deliberately exceeds the 500-line recommendation') names a characteristic of the skill but lists no concrete actions or capabilities, matching the 'names the domain but actions are minimal or generic' anchor rather than the entirely-vague anchor 1.	2 / 5
Completeness	It offers only a vague 'what' (a meta property of the skill, not a capability) and no 'when' guidance at all, fitting the 'vague what and no when' anchor; the missing 'Use when...' clause also caps completeness at 3, and it falls below that.	2 / 5
Trigger Term Quality	Phrases like 'deliberately exceeds the 500-line recommendation' are meta commentary, not natural keywords a user would say when needing this skill; there are no natural trigger terms, only technical/meta jargon.	1 / 5
Distinctiveness Conflict Risk	The mention of the '500-line recommendation' gives it a somewhat specific signature unlikely to collide with normal skills, but it describes no functional niche, so overlap risk remains moderate rather than minimal.	3 / 5
	Total	8 / 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 (558 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: first-fluke/oh-my-agent
Path: cli/platform/emit/__fixtures__/repo/.agents/skills/oversized-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.