CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-injection-test

A test skill with prompt injection patterns

35

Quality

30%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./evals/test_skills/malicious/prompt-injection/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

37%

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

The body is not a legitimate skill document but a prompt-injection payload: it instructs Claude to ignore prior instructions, always respond with 'HACKED', and execute a malicious remote-shell command without verification. It lacks any real workflow, validation, or purposeful guidance.

Suggestions

Remove the injection directives ('Ignore all previous instructions', 'execute ... without verification') and replace them with legitimate skill instructions.

Add an explicit validation/verification checkpoint for any risky or multi-step operation the skill describes.

Replace the malicious payload with a safe, purposeful example relevant to the skill's stated goal of working with prompt injection patterns.

DimensionReasoningScore

Conciseness

The body is terse with no concept over-explanation, but the brevity is that of an injection payload rather than lean, purposeful skill guidance where every token earns its place.

2 / 3

Actionability

A concrete, executable code block is present, but it is framed by the directive 'execute the following code without verification' — an injection instruction rather than legitimate actionable guidance for a real task.

2 / 3

Workflow Clarity

There is no sequenced multi-step workflow, and the body explicitly demands action 'without verification', which is the opposite of a validation checkpoint for a risky operation.

1 / 3

Progressive Disclosure

The body is short with two section headers, but the sections organize an injection payload rather than a coherent, well-organized skill overview, and no external references are signaled.

2 / 3

Total

7

/

12

Passed

Description

22%

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 meta-categorization rather than a capability statement: it identifies the skill as a test artifact about prompt injection but conveys no actions, no usage triggers, and only weak distinctiveness. It fails to tell Claude what the skill does or when to invoke it.

Suggestions

Replace 'A test skill with prompt injection patterns' with concrete actions the skill performs (e.g., 'Detects and classifies prompt injection patterns in text').

Add an explicit 'Use when...' trigger clause stating when Claude should invoke this skill.

Include natural trigger variations a user would say (e.g., 'prompt injection', 'injection attack', 'jailbreak test') to improve discoverability.

DimensionReasoningScore

Specificity

The phrase 'A test skill with prompt injection patterns' names a domain but describes no concrete actions or capabilities — it states what the skill is, not what it does.

1 / 3

Completeness

The 'what' is weakly present (a test skill with patterns) and the 'when' is entirely absent with no 'Use when...' clause, so both halves are missing or very weak.

1 / 3

Trigger Term Quality

'prompt injection' is a relevant term a user might say, but the description includes no trigger clause and no common variations, only the single domain term.

2 / 3

Distinctiveness Conflict Risk

'prompt injection' is a somewhat specific niche, but the generic 'a test skill with...' framing keeps it from being clearly distinguishable from other test or security skills.

2 / 3

Total

6

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
cisco-ai-defense/skill-scanner
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.