CtrlK
BlogDocsLog inGet started
Tessl Logo

prompt-guard

Meta's 86M prompt injection and jailbreak detector. Filters malicious prompts and third-party data for LLM apps. 99%+ TPR, <1% FPR. Fast (<2ms GPU). Multilingual (8 languages). Deploy with HuggingFace or batch processing for RAG security.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./07-safety-alignment/prompt-guard/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A highly actionable, code-first skill body with executable examples and clear sectioning. It loses points for repeated inference boilerplate, a missing validation feedback loop in the batch workflow, and the absence of progressive disclosure to separate reference files.

Suggestions

Factor the shared tokenize+softmax inference logic into one helper shown once, then reuse it in the three workflows to remove the repeated boilerplate.

Add an explicit validation/feedback step to the batch workflow (e.g. log blocked items, retry on tokenizer errors, sanity-check score distribution) so batch operations have a validate->fix->retry loop.

Move the threshold-recommendation table, hardware requirements, and common-issues recipes into a references/ file (e.g. REFERENCE.md) and link to it from the body to enable proper progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient code-first content, but the tokenize+softmax inference boilerplate is repeated across three workflows and fabricated example scores (0.9999, 0.9872) pad the guide.

2 / 3

Actionability

Provides fully executable transformers/torch code with a real model ID, concrete thresholds, and copy-paste-ready functions rather than pseudocode.

3 / 3

Workflow Clarity

Workflows are sequenced, but the batch-processing workflow lacks an explicit validate->fix->retry feedback loop; missing validation in batch operations caps clarity at 2.

2 / 3

Progressive Disclosure

Well-sectioned but monolithic: no bundle files or one-level-deep references exist, and detail (full code, threshold table, hardware specs) that could be split out is kept inline.

2 / 3

Total

9

/

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, well-triggered description that names concrete actions and natural keywords in a distinct niche. Its main gap is the absence of an explicit 'Use when...' trigger clause.

Suggestions

Add an explicit 'Use when...' clause (e.g. 'Use when filtering user prompts or third-party/RAG data for prompt injections or jailbreaks') to lift completeness to 3.

Lead with the action verbs in third person and move the performance metrics (99%+ TPR, <1% FPR, <2ms) after the trigger clause so the 'when' is immediately visible.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Filters malicious prompts and third-party data', 'Deploy with HuggingFace or batch processing for RAG security') rather than vague abstractions.

3 / 3

Completeness

Clearly answers 'what' the skill does but lacks an explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes natural terms users would say ('prompt injection', 'jailbreak detector', 'malicious prompts', 'RAG security') with good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The prompt-injection/jailbreak-detection niche is distinct from general content moderation, with specific triggers unlikely to conflict with other skills.

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Orchestra-Research/AI-Research-SKILLs
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.