CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ad-overview

Active Directory attack lane — BloodHound ingestion, Kerberoasting, ADCS ESC scanning, DCSync, LAPS extraction.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/ad/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-organized catalog body that excels at token efficiency and routes cleanly to per-technique playbooks with useful engagement-specific guardrails. It falls short on actionability — no executable commands or example queries — and lacks error-recovery guidance in the collection workflow.

Suggestions

Add one or two concrete, copy-ready examples to the prerequisites section, e.g. a sample bounded shortest-path query or the exact collection-upload step against the named tool interfaces.

Add an error-recovery branch for the collection workflow (e.g. 'If upload fails or coverage is partial, re-run collection with the listed collectors before interpreting results').

Make playbook rows self-explanatory — expand 'dontreqpreauth users' to 'AS-REP roast accounts with no pre-auth required' and use resolvable relative links where the sub-skills are available.

DimensionReasoningScore

Conciseness

Lean and efficient: ~20 lines with zero padding and no explanations of concepts Claude already knows; every line adds environment-specific knowledge (e.g. 'bloodhound_mcp_*' vs 'bhce_*' tooling split, 'A discovered hostname alone does not populate BloodHound'). Not 4: there is no over-explanation to trim.

5 / 5

Actionability

Some concrete guidance — named tools ('bloodhound_mcp_*', 'bhce_*'), named BloodHound features ('object profiles, exposure search, and bounded shortest paths') — but no executable commands or examples; 'verify successful completion' and 'Record evidence' lack the how. Not 4: the body contains no code or commands at all, leaving key execution details missing.

3 / 5

Workflow Clarity

The 4-step collection/analysis sequence is clearly ordered with most checkpoints present ('verify successful completion', 'Inspect collection coverage', 'leads until independently validated', evidence boundary in step 4). Not 5: there is no error-recovery/feedback loop (e.g. what to do when the upload fails or coverage is incomplete). Not 3: checkpoints are explicit, not merely implicit.

4 / 5

Progressive Disclosure

Good structure: a Playbooks table that signals each one-level-deep reference with its purpose, plus a short prerequisites section. Not 5: the referenced '/skills/standard/ad/...' paths are external catalog paths rather than resolvable in-bundle files or markdown links, and rows like 'dontreqproauth users' are cryptic; not 3: content is appropriately split for a routing catalog with clear navigation.

4 / 5

Total

16

/

20

Passed

Description

71%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, well-scoped description that names five concrete AD attack techniques with excellent domain vocabulary. Its main weakness is the missing explicit 'when to use' trigger clause in the description itself, and trigger coverage lacks common synonyms.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when operating in an authorized Active Directory lab or engagement covering BloodHound, Kerberoasting, ADCS, DCSync, or LAPS work.'

Add natural synonyms users would say — 'AD', 'domain escalation', 'domain compromise', 'krbtgt' — to broaden trigger-term coverage.

Differentiate the catalog's routing role from the dedicated per-technique sub-skills (e.g. 'overview and routing catalog for...') to reduce overlap-induced conflict risk.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'BloodHound ingestion, Kerberoasting, ADCS ESC scanning, DCSync, LAPS extraction' — giving comprehensive coverage of the AD attack lane in third-person voice. Not 4: coverage of the lane's techniques is comprehensive rather than having minor gaps.

5 / 5

Completeness

Has a clear 'what' (the five named techniques) but no 'Use when...' clause or equivalent explicit trigger guidance in the description — the when_to_use metadata is not part of the description — so completeness is capped at 3. Not 4: the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms practitioners actually say ('Active Directory', 'BloodHound', 'Kerberoasting', 'ADCS', 'DCSync', 'LAPS'). Not 5: common synonyms and variations like 'AD', 'domain compromise', or 'password cracking' are absent from the description field.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinctive technique-level triggers (Kerberoasting, DCSync, LAPS) that are unlikely to fire the wrong skill. Not 5: these same terms overlap with the dedicated per-technique sub-skills this catalog routes to, creating minor conflict risk within the same domain.

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