CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

path-traversal

Hunt directory traversal and archive traversal (ZipSlip/TarSlip) from user input to filesystem operations.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

A tight, highly actionable playbook: concrete payloads and named sinks with zero wasted tokens, a logically sequenced workflow ending in explicit validation, and appropriately compact single-file structure. The only gap is the absence of an error-recovery feedback loop in the workflow.

DimensionReasoningScore

Conciseness

The body is lean and efficient with zero padding: every line delivers a sink, payload, control check, or validation instruction, and it assumes Claude's competence with no concept explanations — matching anchor 5 exactly.

5 / 5

Actionability

Fully actionable with copy-paste-ready probe payloads ('../../../../etc/passwd', '%2e%2e%2f', '..\\..\\windows\\win.ini'), named sinks (open(user_path), send_file(user_path), archive extraction APIs), and concrete control checks covering the common traversal classes — matching anchor 5.

5 / 5

Workflow Clarity

The four sections form a clear sink-identification → payload-probing → control-verification → validation sequence with an explicit validation checkpoint ('positive and negative controls'), but there is no error-recovery feedback loop or checklist, so it fits anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files, and needs none — its four well-organized sections (Find sinks, Probe payload classes, Verify controls, Validation) constitute an appropriate single-file structure, qualifying for 5 under the simple-skill guideline.

5 / 5

Total

19

/

20

Passed

Description

65%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.

A distinct, domain-specific description with strong natural trigger terms, but it omits explicit 'when to use' guidance in the description itself and only describes one composite action. Moving the trigger phrases from metadata into the description and adding the 'path traversal' synonym would raise completeness and trigger coverage.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when auditing file upload/download, archive extraction, or any user-controlled path reaching filesystem operations'), since trigger guidance currently lives only in metadata.when_to_use and completeness is capped at 3 without it.

Include the common synonym 'path traversal' (and other natural variations users say, like 'LFI' or 'dot dot slash') alongside 'directory traversal' to improve trigger term coverage.

Enumerate one or two more concrete actions in the description — e.g., locating sink functions and probing payload classes — to move specificity from a single composite action toward several listed actions.

DimensionReasoningScore

Specificity

The description names the domain precisely ('directory traversal and archive traversal (ZipSlip/TarSlip)') and one composite action — hunting from 'user input to filesystem operations' — but does not list several distinct concrete actions, matching anchor 3 rather than anchor 4.

3 / 5

Completeness

The 'what' is clear (hunt traversal flaws from user input to filesystem operations), but the description field contains no 'Use when...' clause or equivalent trigger guidance — that guidance lives only in a separate metadata.when_to_use field, so completeness is capped at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like 'directory traversal', 'archive traversal', 'ZipSlip', 'TarSlip', and 'filesystem' give good keyword coverage, but the very common synonym 'path traversal' (and variants like 'LFI' or '../') is absent, placing it below anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

A clear niche (directory/archive traversal vulnerability hunting) with distinct triggers (ZipSlip, TarSlip, directory traversal) and minimal overlap with other skills; it would not fire for unrelated tasks.

5 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/analyst/path-traversal/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.