CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ssti

Hunt server-side template injection across Jinja2/Twig/Freemarker/Velocity/Handlebars and validate progression from expression injection to code execution.

Quality

81%

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

86%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 concise, well-structured SSTI playbook with copy-paste detection probes and a clear escalation sequence. The weaknesses are concentrated in the escalation and validation sections, which rely on high-level gadget-chain direction and an undefined "validate_finding" tool rather than concrete payloads or an inline validation method.

Suggestions

Add at least one concrete escalation payload per major engine (e.g. a Jinja2 object-traversal chain for command execution) so the escalation path is as executable as the detection probes.

Replace or define "validate_finding" — either inline the validation method (how to confirm a positive execution signal and run a benign negative control) or bundle a script, since no validate_finding tool exists in the skill bundle.

DimensionReasoningScore

Conciseness

The body is a lean playbook: bullet-form sinks, per-engine probes, and a numbered escalation path with zero padding and no explanation of concepts Claude already knows. Every line carries actionable information, matching the "every token earns its place" anchor; there is nothing to trim or add.

5 / 5

Actionability

Detection is fully executable — copy-paste probes per engine ("{{7*7}}", "${7*7}", "#set($x=7*7)$x") and concrete sink names ("render_template_string", "Template(...)", "twig->createTemplate"). Not a 5 because the escalation path stops at high-level directions ("Attempt command execution via framework-specific gadget chain") with no example payloads, and "validate_finding" references a tool that is not defined or bundled.

4 / 5

Workflow Clarity

The escalation sequence (detect → enumerate → file read/env leak → command execution) is clearly ordered and a validation step exists ("positive execution signal and a benign negative control"). Not a 5 because there is no feedback loop for failed probes and "validate_finding" is an undefined reference; not a 3 because the sequence and a genuine validation checkpoint are both present.

4 / 5

Progressive Disclosure

This is a short single-purpose skill (~20 lines) with no bundle files, so the simple-skill exception applies: the four well-organized sections (High-signal checks, Fast probes, Escalation path, Validation) are easy to navigate with no content that belongs in a separate file. All referenced items are inline — there are no dangling file references to verify.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific, well-scoped description with strong natural trigger terms and minimal conflict risk. Its main weakness is the missing explicit "Use when..." trigger clause, which caps completeness at 3, and the absence of the widely used "SSTI" acronym in the description itself.

Suggestions

Append an explicit trigger clause to the description, e.g. "Use when auditing web apps that render user input through Jinja2, Twig, Freemarker, Velocity, or Handlebars templates, or when SSTI is suspected."

Include the common acronym "SSTI" and natural variations (e.g. "template injection", "template payload") directly in the description text rather than only in the when_to_use metadata.

DimensionReasoningScore

Specificity

The description lists concrete actions ("Hunt server-side template injection", "validate progression from expression injection to code execution") and precisely scopes the domain across five named engines, matching the "several specific actions; minor gaps" anchor. It falls short of a 5 because coverage is limited to hunting and validating — no detection/reporting detail — and above a 3 because the engine enumeration and two-phase framing go beyond naming a domain with 1-2 generic actions.

4 / 5

Completeness

The "what" is clear and concrete, but the description field contains no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. It is not lower because the "what" side is specific and well-formed.

3 / 5

Trigger Term Quality

It includes the natural phrase users would say ("server-side template injection") plus engine names ("Jinja2/Twig/Freemarker/Velocity/Handlebars") and "expression injection", "code execution" — good keyword coverage. Not a 5 because the most common shorthand "SSTI" and common phrasings like "template payload" are absent from the description field itself.

4 / 5

Distinctiveness Conflict Risk

The SSTI niche with five named template engines is highly distinct from general web-exploitation or injection skills, and the trigger terms are engine-specific. Not a 4 because the engine enumeration leaves essentially no overlap with closely related skills.

5 / 5

Total

16

/

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/ssti/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.