CtrlK
BlogDocsLog inGet started
Tessl Logo

asrep-roasting

Request AS-REP for accounts with DONT_REQ_PREAUTH set and crack offline — like kerberoast but no auth required.

60

Quality

72%

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

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The playbook is highly actionable and concise, with executable commands throughout and a clean sectioned structure. Its main gap is the absence of an explicit validation checkpoint between cracking and promoting credentials in a batch operation.

Suggestions

Add an explicit verification step before section 5, e.g. confirm cracked credentials with 'hashcat --show' before promoting them to the graph.

Optionally note how to validate that a requested AS-REP hash was captured (non-empty /tmp/asrep.hashes) before moving to cracking.

DimensionReasoningScore

Conciseness

The body is code-first and lean, assuming Claude's competence; minor editorializing (the 2014 anecdote) is operational color that still earns its place rather than padding, with no generalized concept explanation Claude already knows.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands with real flags (ldapsearch UAC bitmask, GetNPUsers.py, hashcat -m 18200, john, Set-ADAccountControl), matching the 'fully executable' anchor.

3 / 3

Workflow Clarity

Steps are clearly numbered (identify -> request -> crack -> promote), but the batch hash-cracking operation has no explicit verify-cracked-before-promote checkpoint, capping it at 2 per the batch-operations feedback-loop rule.

2 / 3

Progressive Disclosure

A single, well-organized file with clearly labeled sections and no nested references; content is appropriately self-contained for this playbook, so header navigation suffices.

3 / 3

Total

11

/

12

Passed

Description

57%

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 specific and well-differentiated, clearly conveying the technique and its advantage over kerberoasting. It falls short on completeness by lacking an explicit 'Use when...' trigger clause and could use more natural trigger phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when targeting accounts with pre-authentication disabled or when the user mentions AS-REP roasting.'

Soften jargon in the description (e.g. expand 'DONT_REQ_PREAUTH' to 'pre-authentication disabled') so trigger terms match natural user phrasing.

Mention the identification step briefly (e.g. 'identify vulnerable accounts') to make the capability list more comprehensive.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('Request AS-REP' and 'crack offline'), but omits identification of vulnerable users and promotion steps, so it is not comprehensive enough for a 3.

2 / 3

Completeness

Clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant niche terms ('AS-REP', 'kerberoast', 'crack offline') but leans on jargon like 'DONT_REQ_PREAUTH' and misses common phrasings a user might naturally say.

2 / 3

Distinctiveness Conflict Risk

The phrase 'like kerberoast but no auth required' carves out a clear, distinct niche that is unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

12

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.

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