CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

apt34-oilrig

Adversary-emulation profile for APT34 / OilRig (G0049), an Iranian state-sponsored espionage group, mapping its ATT&CK TTPs to Decepticon tooling for authorized red-team emulation.

Quality

69%

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/apt34-oilrig/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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, factually rich actor profile whose emulation and detection sections include genuinely concrete commands, registry keys, and CVEs. Its weaknesses are the absence of validation checkpoints in a workflow built around risky operations (capping workflow clarity at 3), and a monolithic single-file structure that inlines encyclopedic detail instead of offloading it to reference files.

Suggestions

Add explicit validation checkpoints to the emulation workflow — e.g. re-confirm scope/RoE before credential access or persistence phases, and verify with the blue cell that detections fired (DNS-tunneling alerts, password-filter registry changes) before proceeding.

Split the encyclopedic detail (campaign histories, signature-tooling catalog, full per-tactic TTP mapping, detection guidance) into references/ files (e.g. campaigns.md, tooling.md, detection.md) and keep SKILL.md as a lean overview with clearly signaled one-level-deep links.

Trim the 'Attribution & motivation' and 'Notable campaigns' prose and remove the duplication between the frontmatter mitre_attack list and the body's technique-by-technique enumeration to reduce token cost without losing operational value.

DimensionReasoningScore

Conciseness

The body is dense and largely free of fluff, but it restates the entire ATT&CK G0049 catalog — attribution narrative, multi-paragraph campaign histories, and ~75 techniques already enumerated in the frontmatter mitre_attack list — which is encyclopedic knowledge Claude already has. This matches anchor 3 (mostly efficient but includes content that could be tightened or trimmed), and is not 4 because whole sections ("Attribution & motivation", "Notable campaigns") add background rather than operational value.

3 / 5

Actionability

Concrete, executable specifics appear where they matter: the exact LOLBin recon sequence ("whoami, net user/net group, ipconfig /all, netstat -an, net accounts, sc query"), precise registry paths ("HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages"), CVE identifiers, and per-tactic tool mappings. It sits between anchors 3 and 4: guidance is mostly concrete, but emulation steps like "use the phishing/social-engineering skill" and "Configure your C2/Sliver profile" lack paths, commands, or examples — noticeable but minor gaps.

4 / 5

Workflow Clarity

The tactic-ordered emulation guidance and the illustrative chain ("phish → loader → DNS/HTTP C2 → discovery → credential access → escalation → lateral access → staging → mail/DNS transfer") provide a rough sequence, but there are no validation checkpoints (no scope re-verification, no per-phase verification, no detection-confirmation steps). Because the operations are destructive/exploitative (credential dumping, kernel exploits, persistence), the guideline capping workflow clarity at 3 applies; the sequence itself keeps it above anchor 2.

3 / 5

Progressive Disclosure

The file is well-sectioned with clear ## headers, but it is a single ~19KB monolith with no bundle files at all — campaign histories, the signature-tooling catalog, per-tactic TTP detail, and detection guidance are all inlined where reference files would keep the SKILL.md an overview. This matches anchor 3 (some structure, but content that should be separate is inline with no references to signal).

3 / 5

Total

13

/

20

Passed

Description

70%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 is highly specific and distinctive, correctly identifying the actor, ATT&CK group ID, and purpose with natural trigger terms. Its main weakness is completeness: it lacks an explicit 'Use when…' clause, leaving the trigger context only weakly implied and relying on metadata.when_to_use rather than the description itself.

Suggestions

Add an explicit trigger clause to the description, e.g. "Use when emulating APT34/OilRig, Iranian espionage actors, or DNS-tunneling C2 tradecraft in an authorized red-team engagement."

Surface 2–3 natural synonyms (e.g. "Helix Kitten", "Iranian APT", "DNS tunneling") inside the description itself rather than only in metadata.when_to_use, so trigger matching works from the description alone.

DimensionReasoningScore

Specificity

The description names the domain precisely ("APT34 / OilRig (G0049), an Iranian state-sponsored espionage group") and gives concrete actions — "mapping its ATT&CK TTPs to Decepticon tooling for authorized red-team emulation" — matching the anchor for several specific actions with minor gaps. It is above anchor 3 (only 1–2 actions) because actor, ATT&CK ID, toolchain, and purpose are all explicit, but below anchor 5 because it omits capabilities the body actually provides (detection guidance, tooling catalog).

4 / 5

Completeness

The 'what' is clear (an emulation profile mapping the group's TTPs to specific tooling), but the 'when' is only weakly implied by "for authorized red-team emulation" — there is no explicit "Use when…" clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is concrete, and not 4 because 'when' is absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"APT34", "OilRig", "red-team emulation", "ATT&CK TTPs", and "adversary-emulation" are phrases a user would naturally say when needing this skill. It falls between anchor 3 and 5: good keyword coverage, but common synonyms users might type ("Helix Kitten", "Iranian APT", "DNS tunneling") appear only in metadata.when_to_use, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

"APT34 / OilRig (G0049)" names a single specific threat actor with distinct triggers ("Iranian state-sponsored espionage", "authorized red-team emulation"), giving it a clear niche with minimal conflict risk against other skills — matching anchor 5.

5 / 5

Total

16

/

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/apt34-oilrig/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.