CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

asrep-roasting

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

Quality

73%

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/ad/asrep-roasting/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, operationally complete playbook: every phase from identification through cracking to promotion and defender remediation is backed by concrete, executable commands with correct technical details (hashcat mode 18200, UAC bit filter, event 4768 detection tells). The only notable gaps are the non-executable kg_add_node notation for the promote step and the absence of explicit validation feedback loops, both minor.

Suggestions

Make the promote step executable by showing how kg_add_node is actually invoked (tool call syntax or script), matching the concreteness of the preceding sections.

Add a brief verification step after the hashcat run (e.g., check /tmp/asrep.hashes for cracked entries or run hashcat --show) to close the workflow with an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is command-dense and lean with almost no explanation of concepts Claude already knows, but minor editorializing could be trimmed ("sysadmin set DONT_REQ_PREAUTH to 'fix' a ticket issue in 2014, never reverted", "more powerful than kerberoast in some engagements"). This fits anchor 4 — efficient with minor over-explanation — rather than anchor 5 where every token earns its place.

4 / 5

Actionability

Nearly all guidance is copy-paste ready: the ldapsearch command includes the exact UAC bitwise filter (1.2.840.113556.1.4.803:=4194304), both GetNPUsers.py variants have full flags, and hashcat -m 18200 includes the rule file. The one gap is the promote step, where kg_add_node(...) is call-signature notation rather than an executable command, fitting anchor 4 (minor gaps) instead of 5.

4 / 5

Workflow Clarity

The numbered sections 1-5 give a clear identify → request → crack → promote sequence with alternative paths (hosted vs standalone tooling, zero-auth vs credentialed) and OPSEC considerations that function as decision checkpoints. There is no explicit validate/verify feedback loop, but the operations are non-destructive, so anchor 4 applies rather than the destructive-operation cap or anchor 5's explicit validation loops.

4 / 5

Progressive Disclosure

There are no bundle files (references/, scripts/, assets/ are absent) and the body is a self-contained ~94-line playbook with clean numbered sections and no nested references. The size exceeds the under-50-line simple-skill exception, and everything is inline with no external splitting, fitting anchor 4 (good structure, content appropriately placed) rather than anchor 5's well-signaled reference structure.

4 / 5

Total

16

/

20

Passed

Description

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

The description is concise, technically precise, and clearly differentiates the technique from kerberoasting, with decent natural trigger terms. Its main weakness is the absence of an explicit "Use when..." clause in the description itself — trigger guidance lives only in the separate when_to_use metadata — and only two concrete actions are named.

Suggestions

Add an explicit "Use when..." clause to the description, e.g., "Use when enumerating accounts with pre-auth disabled, AS-REP roasting, or when you need kerberoast-style cracking without credentials."

Include natural trigger variations directly in the description (e.g., "AS-REP roasting", "pre-auth disabled", "hashcat 18200") rather than relying solely on the when_to_use metadata.

Name one more concrete capability (e.g., identifying roastable users via LDAP/BloodHound) to lift specificity beyond two actions.

DimensionReasoningScore

Specificity

"Request AS-REP for accounts with DONT_REQ_PREAUTH set and crack offline" names the domain plus exactly two concrete actions (request AS-REP, crack offline), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several specific actions, so it falls below anchor 4.

3 / 5

Completeness

The "what" is clear (request AS-REP for preauth-disabled accounts and crack offline), but the description contains no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The kerberoast comparison only weakly implies when to use it.

3 / 5

Trigger Term Quality

"AS-REP", "kerberoast", "DONT_REQ_PREAUTH", and "crack offline" are natural terms a user would say for this need, giving good keyword coverage. Common variations like "AS-REP roasting" or "pre-auth" are missing from the description itself (they only appear in separate when_to_use metadata), keeping it below anchor 5.

4 / 5

Distinctiveness Conflict Risk

"AS-REP for accounts with DONT_REQ_PREAUTH set" carves out a clear niche with distinct triggers and minimal conflict risk. The explicit "like kerberoast" comparison introduces minor overlap risk with a sibling kerberoasting skill, so it does not reach anchor 5.

4 / 5

Total

14

/

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