link-traversal

Body links outside the skill directory using a parent traversal.

Quality

28%

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/link-traversal/SKILL.md

Quality

Content

33%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 contains no actionable content — just two malformed links, one of which traverses outside the skill directory and both of which point to nonexistent files. It functions as a test fixture rather than usable skill content. No workflow, guidance, or reachable reference material exists.

Suggestions

Add actual executable guidance (commands, code, or concrete instructions) instead of only link references.

Fix the malformed link syntax (remove spaces inside the parentheses) and point references at real files within the skill's bundle; remove the ../ parent traversal that escapes the skill directory.

Replace the generic '# Body' heading with meaningful section headings so any references are clearly signaled.

Dimension	Reasoning	Score
Conciseness	The body is only a heading and two short link lines with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor. Nothing could be trimmed without losing the (already minimal) content.	5 / 5
Actionability	'See [the secret]( ../secret.md ) and [guide](references/guide.md)' provides no code, commands, or concrete guidance — it only refers, matching the 'entirely vague or abstract; only describes rather than instructs' anchor. The referenced files do not even exist in the bundle, so nothing actionable can be reached.	1 / 5
Workflow Clarity	There are no steps or sequence of any kind, and the simple-skill exception does not apply because there is no unambiguous single action to perform — the body is only dangling references. This matches the 'steps missing or incoherent' anchor.	1 / 5
Progressive Disclosure	References are one level deep but buried under a generic '# Body' heading, malformed by spaces inside the link targets, and both target files are missing from the bundle (references/ does not exist and ../secret.md escapes the skill directory), so navigation effectively fails. This falls between the 'impossible to navigate' anchor and the 'references are buried' anchor, noticeably below the midpoint.	2 / 5
	Total	9 / 20 Passed

Description

22%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 a structural statement about the skill's file layout rather than a capability description. It lacks any trigger guidance, natural user keywords, or user-facing 'what', making it effectively unusable for skill triggering. It reads as a test-fixture annotation, not a real skill description.

Suggestions

Replace the structural statement with a functional description of what the skill actually does for the user, stated in third person.

Add an explicit 'Use when...' clause with natural trigger phrases users would actually say; its absence currently caps completeness.

Include natural keywords and synonyms for the skill's domain instead of technical jargon like 'parent traversal'.

Dimension	Reasoning	Score
Specificity	The phrase 'links outside the skill directory using a parent traversal' states one concrete action, matching the anchor for naming a domain and 1-2 concrete actions without comprehensive coverage. It is above score 2 because the action is stated concretely rather than generically, but below score 4 because no list of actual capabilities is provided.	3 / 5
Completeness	The 'what' is a vague structural property of the file rather than a functional capability, and there is no 'when' / 'Use when...' clause at all, matching the anchor for 'vague what and no when'. It cannot score 3 because the stated what conveys no user-facing task the skill performs.	2 / 5
Trigger Term Quality	The description contains only technical jargon ('parent traversal', 'skill directory') and no natural keywords a user would say when needing this skill, matching the anchor for 'only technical jargon or entirely generic language'.	1 / 5
Distinctiveness Conflict Risk	The description describes the skill's file structure rather than any capability, making it indistinguishable from other skills with very broad overlap characteristics. It is not score 1 because the phrase is at least narrowly about links and traversal rather than 'entirely generic'.	2 / 5
	Total	8 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing, 1 suspicious	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: pantheon-org/tekhne
Path: crates/skill-validator-rs/tests/golden-corpus/fixtures/boundary/link-traversal/SKILL.md
Commit: a1083f4

Reviewed: 3 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.