CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

lazarus

Lazarus Group (Hidden Cobra, DPRK RGB) adversary-emulation playbook — financially-motivated crypto/DeFi theft and supply-chain intrusion: fake-job social engineering, trojanized apps, wallet/key theft, and on-chain DeFi/bridge exploitation (testnet/fork only). Use when emulating DPRK financial actors against a crypto/exchange/DeFi target. Triggers on: 'emulate Lazarus', 'Hidden Cobra', 'DPRK crypto', 'AppleJeus', '3CX supply chain', 'DeFi bridge attack', 'crypto theft'.

Quality

94%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An efficient, highly actionable emulation playbook with a clearly sequenced kill chain, strong safety gates, and clean one-level routing to per-phase skills. The only gap is that validation/abort checkpoints are stated in surrounding sections rather than embedded as explicit steps in the workflow sequence itself.

DimensionReasoningScore

Conciseness

The body is lean CTI-derived guidance — a two-line framing blockquote, a copy-ready JSON seed, an 11-row kill-chain table, and short OPSEC/RoE/fidelity sections — with no explanation of concepts Claude already knows and no padding to trim.

5 / 5

Actionability

Fully concrete guidance: a complete ThreatProfile JSON seed, per-phase routing to exact skill paths, named tools (Sliver, Foundry/Anvil, NetExec, canary wallets), named output files (deconfliction.json, cleanup.json), and a specific EMERGENCY-abort string. As a routing/instruction skill, no code absence penalty applies.

5 / 5

Workflow Clarity

The kill chain is clearly sequenced twice (table rows 1–11 and CONOPS steps 1–5) and risky on-chain operations have safety gates (EMERGENCY abort criterion, canary wallets, RoE), but those checkpoints live in prose rather than being woven into the numbered sequence as explicit verify-before-proceeding steps.

4 / 5

Progressive Disclosure

The body is a well-organized overview that routes detail to separate per-phase skill files via explicit one-level-deep paths, with one clearly signaled external reference; no content is inlined that belongs in a separate file, and the skill bundle itself contains no additional files.

5 / 5

Total

19

/

20

Passed

Description

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

A highly specific, complete description with concrete actions, an explicit use-when clause, and comprehensive natural trigger terms in third-person voice. The only weakness is slight overlap risk from a few broadly applicable trigger phrases.

DimensionReasoningScore

Specificity

The description lists multiple concrete, distinct actions — "fake-job social engineering, trojanized apps, wallet/key theft, and on-chain DeFi/bridge exploitation" plus "supply-chain intrusion" — with comprehensive coverage of the actor's TTP lanes and no gaps relative to the body.

5 / 5

Completeness

Both halves are explicit: "what" ("adversary-emulation playbook — financially-motivated crypto/DeFi theft and supply-chain intrusion...") and "when" ("Use when emulating DPRK financial actors against a crypto/exchange/DeFi target" plus a concrete Triggers-on list).

5 / 5

Trigger Term Quality

Explicit trigger list covers natural user phrasing comprehensively with synonyms and operation names: "'emulate Lazarus', 'Hidden Cobra', 'DPRK crypto', 'AppleJeus', '3CX supply chain', 'DeFi bridge attack', 'crypto theft'".

5 / 5

Distinctiveness Conflict Risk

A named-actor emulation niche with actor-specific triggers is mostly distinct, but generic phrases like "DeFi bridge attack" and "crypto theft" carry minor overlap risk with general contract-exploitation or crypto-security skills.

4 / 5

Total

19

/

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/standard/soundwave/threat-profile/emulation/lazarus/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.