CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ad

Active Directory exploitation — BloodHound analysis, Kerberoasting, AS-REP Roasting, AD CS abuse, DCSync, Golden Ticket, Constrained Delegation.

Quality

76%

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/standard/exploit/ad/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 highly actionable command reference with lean explanations, correct tooling, and a clean section structure including detection signatures and a decision gate. The main weaknesses are significant content duplication (Quick Reference vs. sections, body vs. attack-paths.md) and missing validation checkpoints for batch operations like DCSync.

Suggestions

Remove the 'Quick Reference' section's duplicated commands — either keep only the Quick Reference and drop the repeated commands from each section, or drop the Quick Reference and let each section stand alone.

Deduplicate against references/attack-paths.md: keep SKILL.md as a lean overview (one representative command per technique plus the decision gate) and move the full command matrices and BloodHound query sets to the reference file.

Add explicit validation checkpoints to the technique chains, e.g. `hashcat -m 13100 ... --show` to confirm cracks before pivoting, and verifying obtained credentials with a low-impact authentication before using them for DCSync or lateral movement.

DimensionReasoningScore

Conciseness

Explanations are lean one-liners that assume Claude's competence (no concept over-teaching), but the "Quick Reference" block duplicates commands repeated verbatim in sections 1–5, and much of the body (BloodHound queries, hashcat modes, ESC1, DCSync, Golden Ticket, delegation commands) is duplicated again in references/attack-paths.md. This matches the score-3 anchor ('mostly efficient but could be tightened') rather than 4, where duplication would be minor.

3 / 5

Actionability

Fully executable, copy-paste-ready commands throughout with exact flags, placeholders, and correct hashcat modes (13100, 18200, 19700), covering the common cases per tool on both Linux and Windows. Matches the score-5 anchor ('fully executable; copy-paste ready; specific examples cover the common cases').

5 / 5

Workflow Clarity

Sections are logically sequenced (recon → roasting → AD CS → DCSync → ticket forging → delegation) and the Decision Gate gives failure branches, but there are no explicit validation checkpoints for batch operations (e.g., secretsdump -just-dc dumps all hashes) — no step verifies cracked credentials before pivoting and no hashcat --show check. Per the rubric's cap rule for batch operations lacking validation, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Well-sectioned body with a clearly signaled, one-level-deep reference (references/attack-paths.md — a real file — with an explicit 'read when' note), matching the score-4 anchor ('good structure; references mostly clear; minor organization gaps'). It falls short of 5 because content is not appropriately split: the inline command detail largely duplicates the reference file instead of the SKILL.md serving as a lean overview of it.

4 / 5

Total

15

/

20

Passed

Description

75%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 specific, distinctive description that names the domain and seven concrete attack techniques with excellent natural trigger terms. Its main weakness is that the 'when to use' guidance is relegated to a metadata field rather than appearing in the description itself, capping completeness.

Suggestions

Fold trigger guidance into the description itself, e.g. append "Use when the user mentions kerberoasting, AS-REP roasting, DCSync, golden tickets, AD CS, BloodHound, or asks to escalate privileges in Active Directory."

Add tool-name synonyms users naturally say — "impacket", "mimikatz", "certipy", "rubeus", "hashcat" — to the trigger terms so keyword coverage reaches the top anchor.

Consider naming the credential outcome ("extract and crack service-account credentials, forge tickets, achieve domain dominance") so the description states the capability, not just the technique list.

DimensionReasoningScore

Specificity

Names the domain ("Active Directory exploitation") plus seven concrete, named techniques ("BloodHound analysis, Kerberoasting, AS-REP Roasting, AD CS abuse, DCSync, Golden Ticket, Constrained Delegation"), giving comprehensive coverage of the domain's attack surface. It exceeds the score-4 anchor ('several specific actions; minor gaps') because no major AD exploitation technique category is omitted.

5 / 5

Completeness

The description clearly answers 'what' (specific AD exploitation techniques) but contains no "Use when..." clause or equivalent explicit trigger guidance — that guidance lives in a separate metadata.when_to_use field, not the description. Per the rubric guideline, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Contains strong natural trigger terms a practitioner would actually say ("Kerberoasting", "DCSync", "Golden Ticket", "BloodHound", "AS-REP Roasting"). It falls short of the score-5 anchor because common synonyms and tool names users naturally mention ("impacket", "mimikatz", "certipy", "rubeus", "pass-the-hash", "hashcat") are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

A clear niche with distinct named techniques; only another AD-specific skill could plausibly overlap. Matches the score-5 anchor ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/exploit/ad/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.