CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adversary-emulation

Actor-profile taxonomy, ATT&CK technique fidelity, technical prerequisites and detection interpretation for authorized adversary emulation.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/shared/adversary-emulation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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.

The body is a well-organized catalog with real safety constraints (RoE intersection, non-destructive proofs, forbidden-destination checks), but it front-loads conceptual explanation Claude already knows, never sequences the emulation workflow with explicit validation checkpoints, and — most significantly — completely fails to link its own two reference files, leaving the IOC and CVE-APT mapping content undiscoverable.

Suggestions

Add a "References" section linking the bundle files, e.g., "**IOC lookup**: See [references/anyrun-free-iocs.md](references/anyrun-free-iocs.md)" and "**CVE-to-actor mapping**: See [references/cve-apt-mapping.md](references/cve-apt-mapping.md)", so the existing reference material is discoverable.

Replace the conceptual opening (definition of emulation vs. simulation) with a numbered workflow: select profile → intersect techniques with RoE → substitute non-destructive proofs for Impact techniques → execute with forbidden-destination checks → classify detection evidence, with an explicit validation gate before any destructive-adjacent step.

Trim the introductory paragraph and the "When to use this" section (which duplicates the frontmatter when_to_use) to the one or two sentences that add non-obvious information.

DimensionReasoningScore

Conciseness

The opening paragraph spends ~10 lines defining adversary emulation and distinguishing it from pentesting and simulation — concepts Claude already knows — and the "When to use this" section duplicates the frontmatter when_to_use field. This is more than the 'minor instances of over-explanation' of level 4, but the rest (catalog table, interpretation rules) is dense and earns above level 2.

3 / 5

Actionability

There is concrete guidance — the `load_skill <slug>` catalog, non-destructive proof substitutions ("a benign canary file, a dry-run"), "Intersect each selected technique with approved RoE", and the ATT&CK groups verification URL — but no complete executable procedure for building or running an emulation plan. This sits between level 2's high-level-only hints and level 4's mostly-executable guidance.

3 / 5

Workflow Clarity

Profile selection → RoE intersection → execution → detection evidence is only loosely implied, never sequenced, and validation checkpoints ("Out-of-scope techniques remain forbidden", "Forbidden-destination checks still apply at tool time") are implicit rather than explicit steps. Because the subject matter includes destructive-capable techniques emulated without an explicit validate-before-proceeding workflow, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

The bundle contains two substantial reference files (references/anyrun-free-iocs.md, references/cve-apt-mapping.md) that are never mentioned, linked, or signaled anywhere in the SKILL.md body — they are undiscoverable from the index, which matches level 2's 'references are buried' condition. The body's own section structure is reasonable, keeping it above level 1, but the orphaned bundle references prevent level 3+.

2 / 5

Total

11

/

20

Passed

Description

58%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.

The description clearly names a distinct niche and lists several concrete capability areas, but it omits any 'Use when...' trigger guidance and relies on jargon-heavy noun phrases instead of natural user keywords. The strong trigger vocabulary that exists in the metadata.when_to_use field (actor names, "purple team", "TTP replay") is not surfaced in the description itself.

Suggestions

Append a trigger clause to the description, e.g., "Use when the operator asks to emulate a named threat actor (e.g., APT29, Lazarus), run a purple-team or ATT&CK evaluation, or replay a threat actor's TTPs."

Fold a few of the natural trigger phrases from metadata.when_to_use ("emulate APT", "purple team", "threat-informed", "TTP replay") into the description itself so the description field carries the trigger terms.

Rewrite the capability list as concrete actions (e.g., "Selects actor profiles, maps TTPs to ATT&CK techniques, checks RoE scope, interprets detection results") to strengthen specificity toward level 5.

DimensionReasoningScore

Specificity

The description enumerates several concrete capability areas — "Actor-profile taxonomy, ATT&CK technique fidelity, technical prerequisites and detection interpretation" — which is several specific items, though phrased as topical nouns rather than actions. It is above level 3 (which expects only 1-2 concrete actions) but below level 5 because coverage is not comprehensive (e.g., no mention of planning, reporting, or measurement) and the items are domains rather than executable actions.

4 / 5

Completeness

The 'what' is clear (taxonomy, technique fidelity, prerequisites, detection interpretation for adversary emulation), but there is no 'Use when...' clause or equivalent explicit trigger guidance in the description, which caps completeness at 3 per the judging guidelines. It is not level 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords include "adversary emulation", "ATT&CK", and "authorized adversary emulation", but common natural phrases users would say — "emulate APT", "purple team", "threat actor", "TTP replay" — are missing from the description field itself (they appear only in the separate metadata.when_to_use field, not the description). This matches the anchor 'some relevant keywords but missing common variations or synonyms' rather than level 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The niche is clear — authorized adversary emulation with actor profiles and ATT&CK fidelity is well-distinguished from generic pentesting or document skills — but "technical prerequisites and detection interpretation" carries minor overlap risk with adjacent threat-intel, purple-team, and detection-engineering skills. Not level 5 because the description contains no distinct trigger phrases that would fully disambiguate it from those closely related skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/shared/adversary-emulation/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.