CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

threat-profile

Threat actor profiling for adversary emulation — APT group research, sophistication tiers, MITRE ATT&CK mapping, initial access vectors, custom archetypes.

Quality

76%

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/standard/soundwave/threat-profile/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A lean, highly actionable skill body with a well-sequenced workflow, complete schema documentation, and a strong RoE-validation checkpoint. Its main weaknesses are the disconnect between the body's navigation and the actual bundle (missing emulation/ paths, unlinked references files) and the absence of an output-verification feedback loop.

Suggestions

Link the bundled reference files from the relevant steps — e.g., in Step 2 point to references/adversary-archetypes.md for pre-built tier profiles and in Step 5 to references/apt-groups.md for named-actor TTP data — and reconcile the 'emulation/*/SKILL.md' paths with what actually ships in the bundle.

Add an explicit output-validation step after Step 4: verify plan/threat-profile.json against the ThreatProfile schema (e.g., run the validator) and fix-and-retry on failure, rather than only stating the document 'must validate'.

Trim the overlap between Step 2's playbook-loading parenthetical and Step 5, folding the load_skill mechanics into one place.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — tier tables, field lists, RoE constraint tables, and a complete JSON example with no explanations of what APT groups or MITRE ATT&CK are. Minor trimming is possible: the Step 2 parenthetical about loading emulation playbooks and 'Skillogy returns skill bodies, not sibling reference files' overlaps with Step 5's fuller treatment, and the rhetorical opener ('devolves into arbitrary tool usage') is slight padding — this matches 'Efficient; minor instances of over-explanation that could be trimmed' rather than the perfectly lean anchor 5.

4 / 5

Actionability

Fully executable guidance throughout: a complete copy-paste 'plan/threat-profile.json' example with realistic values, exact StrEnum values ('tier-1'..'tier-4'), exact load_skill paths, the legacy embedded-summary shape with which fields to skip, an explicit RoE-to-technique mapping table, and a full field/type/required/allowed-values schema table. Specific examples cover the common cases (standalone and embedded output), matching the top anchor.

5 / 5

Workflow Clarity

A clear 5-step sequence (tier → profile → RoE validation → output → optional kill chain) with an explicit validation checkpoint in Step 3 (profile must be consistent with RoE constraints) and a pruning instruction in Step 5 ('Prune any technique the RoE forbids (Step 3) before writing'). It falls short of anchor 5 because there is no verification of the produced output against the ThreatProfile schema — no validate/fix/retry feedback loop after writing — matching 'most checkpoints present; minor validation gaps'. This is a document-authoring workflow, so the destructive/batch cap at 3 does not apply.

4 / 5

Progressive Disclosure

The body is well-sectioned and points to detail files via load_skill, but scored against the actual bundle: the referenced 'emulation/SKILL.md' and 'emulation/<actor>/SKILL.md' paths do not exist in the bundle, while the two files that do exist (references/apt-groups.md with per-group TTP data and references/adversary-archetypes.md with pre-built tier profiles — exactly the content Steps 2 and 5 need) are never linked or signaled from the body. This orphaned/mismatched reference structure matches 'references present but not clearly signaled; could be better organized' (anchor 3) rather than anchor 4's 'references mostly clear'.

3 / 5

Total

16

/

20

Passed

Description

66%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 domain-specific, keyword-rich description that clearly conveys what the skill does, held back mainly by the absence of any explicit 'Use when...' trigger guidance. Adding a when-clause with natural trigger phrases would lift completeness and trigger coverage simultaneously.

Suggestions

Append an explicit trigger clause, e.g.: 'Use when the user asks about threat actors, APT groups, adversary emulation, who the red team should emulate, or when building a threat profile during engagement planning.'

Add natural synonyms users would actually say — 'red team', 'threat simulation', 'emulate an attacker' — to broaden trigger coverage beyond the current jargon-leaning terms.

DimensionReasoningScore

Specificity

The description names the domain ('Threat actor profiling for adversary emulation') and lists several specific capabilities — 'APT group research', 'sophistication tiers', 'MITRE ATT&CK mapping', 'initial access vectors', 'custom archetypes'. These are mostly topic nouns rather than concrete executable actions and coverage has minor gaps (e.g., no mention of the profile document output), so it sits at anchor 4 rather than the fully comprehensive anchor 5, and clearly above the 1-2-action anchor 3.

4 / 5

Completeness

It has a clear 'what' (threat actor profiling with APT research, tiering, ATT&CK mapping, archetypes) but no 'Use when...' clause or equivalent explicit trigger guidance — 'when' is only weakly implied by 'for adversary emulation'. Per the judging guideline, a missing explicit 'when' caps completeness at 3; it is not a 4 because the when-guidance is absent rather than merely under-specified.

3 / 5

Trigger Term Quality

Includes natural domain terms a user would say — 'threat actor', 'adversary emulation', 'APT group', 'MITRE ATT&CK', 'initial access vectors'. Good coverage but missing common synonyms and variations such as 'red team', 'threat simulation', or 'threat modeling', so it matches 'Good keyword coverage; a few natural terms missing' rather than the comprehensive anchor 5, and is well above the generic-keyword anchors 1-2.

4 / 5

Distinctiveness Conflict Risk

The red-team/adversary-emulation planning niche with distinct triggers (APT groups, MITRE ATT&CK, sophistication tiers) is mostly distinct from other skills, with only minor overlap risk against closely related engagement-planning or ATT&CK-reference skills. It is not a 5 because adjacent planning skills in the same suite could compete for similar 'threat actor' queries.

4 / 5

Total

15

/

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