CtrlK
BlogDocsLog inGet started
Tessl Logo

aatmf-t10-confidentiality-breach

AATMF T10 — Integrity & Confidentiality Breach. System prompt extraction, training-data extraction, model-weight leakage, private-key recovery.

56

Quality

65%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/plugins/llm-redteam/t10-confidentiality-breach/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

The body is a strong, actionable red-team reference: dense, copy-paste-ready attack strings and a runnable probe config with no padding. Its main gaps are the absence of an explicit run-detect-validate workflow and any progressive disclosure into separate reference files.

Suggestions

Add a short numbered workflow with validation checkpoints, e.g. 1) run the probe config, 2) scan outputs against the Detection signals, 3) rate via the Severity table, 4) re-run with the next strategy only if prior signals are negative.

Consider splitting the seven technique details into a references/ file (e.g. TECHNIQUES.md) and keeping SKILL.md as an overview pointing to it, to improve progressive disclosure for this longer skill.

Add an explicit feedback loop for the batch probe step (e.g., 'if a detection signal fires, confirm with a second probe strategy before classifying severity').

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — it never explains basics like what a system prompt is — and each example earns its place (e.g., the 10 extraction prompts 'in order of subtlety'), matching the lean-and-efficient anchor.

3 / 3

Actionability

It supplies literal copy-paste attack strings and a ready-to-run YAML probe config with concrete plugin ids and strategy names, meeting the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

A loose ordering exists ('try in order of subtlety'; Techniques → Probe → Detection → Severity → Defender) but there are no explicit validation checkpoints or feedback loops for the batch probe operation, which the scoring notes cap at 2.

2 / 3

Progressive Disclosure

The skill is a single self-contained file with well-organized sections, but at ~115 lines with seven full techniques inline and no external references, the under-50-line 'well-organized sections → 3' carve-out does not apply; content that could be split stays inline.

2 / 3

Total

10

/

12

Passed

Description

50%

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 conveys a specific niche and several concrete capabilities but leans on internal taxonomy jargon and omits any explicit 'Use when...' trigger guidance. It is functional but not yet user-facing in tone.

Suggestions

Rewrite the description in third-person verb voice with concrete actions (e.g., 'Extracts system prompts, training data, and embedded credentials from an LLM...') and drop or de-emphasize the 'AATMF T10' jargon prefix.

Add an explicit trigger clause, e.g. 'Use when red-teaming an LLM for confidentiality leaks — system prompt extraction, training-data extraction, model-weight leakage, or private-key recovery.'

Include natural user phrasings such as 'system prompt leak', 'training data extraction', and 'secret extraction' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Phrases like 'system prompt extraction, training-data extraction, model-weight leakage, private-key recovery' name the domain and several concrete actions, but they are terse noun-phrases prefixed by internal taxonomy jargon ('AATMF T10') rather than a comprehensive verb-led action list.

2 / 3

Completeness

The description states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric guidelines cap at 2.

2 / 3

Trigger Term Quality

Semi-natural terms appear ('system prompt', 'training data', 'private key') but they are embedded in jargon ('AATMF T10 — Integrity & Confidentiality Breach') and lack common user-facing variations; not anchor 1 because relevant keywords exist, not anchor 3 because natural-term coverage is thin.

2 / 3

Distinctiveness Conflict Risk

It is niche within the AATMF taxonomy, but the internal naming prefix and overlap with sibling tactics (T1, T7, T11 per the body's cross-references) mean it could still overlap with similar skills.

2 / 3

Total

8

/

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.