active-directory-attacks
Provide comprehensive techniques for attacking Microsoft Active Directory environments. Covers reconnaissance, credential harvesting, Kerberos attacks, lateral movement, privilege escalation, and domain dominance for red team operations and penetration testing.
81
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/active-directory-attacks/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and domain-relevant trigger terms that a security professional would naturally use. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill. The description is well-scoped to a clear niche with minimal conflict risk.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about attacking Active Directory, AD exploitation, red teaming Windows domains, or pentesting AD environments.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: reconnaissance, credential harvesting, Kerberos attacks, lateral movement, privilege escalation, and domain dominance. These are well-defined, specific categories of activity. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with the list of attack techniques, but lacks an explicit 'Use when...' clause. The context of red team/pentesting is mentioned but not framed as trigger guidance. Per rubric guidelines, missing 'Use when' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Active Directory', 'Kerberos attacks', 'lateral movement', 'privilege escalation', 'credential harvesting', 'red team', 'penetration testing', 'domain dominance', 'reconnaissance'. These cover the terms a security professional would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Microsoft Active Directory attack techniques for red team operations. The combination of AD-specific terminology (Kerberos, domain dominance) and offensive security context makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-organized, highly actionable AD attack reference with executable commands for all major attack vectors. Its main weaknesses are some redundancy (Quick Reference table duplicating earlier content, boilerplate sections) and insufficient validation/verification steps for destructive operations like DCSync, Golden Ticket creation, and CVE exploitation. The progressive disclosure is handled well with a single reference to advanced techniques.
Suggestions
Add explicit validation/verification steps after critical operations (e.g., verify Golden Ticket works with 'klist', confirm DCSync output contains expected hashes, verify relay succeeded before proceeding)
Remove the redundant Quick Reference table and the boilerplate 'When to Use' section to improve conciseness
Consolidate the Inputs/Prerequisites and Outputs/Deliverables into the workflow itself rather than listing them separately as standalone sections
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with concrete commands, but includes some unnecessary sections like the Inputs/Prerequisites and Outputs/Deliverables lists that Claude doesn't need spelled out, the 'When to Use' boilerplate at the end, and the Essential Tools table which largely duplicates information shown in the commands themselves. The Quick Reference table also duplicates commands already shown in detail above. | 2 / 3 |
Actionability | Excellent actionability throughout - nearly every technique includes fully executable, copy-paste ready commands with specific tool invocations, flags, and argument patterns. Multiple tool alternatives are provided for each attack type, and commands include realistic placeholder values that make adaptation straightforward. | 3 / 3 |
Workflow Clarity | The Core Workflow steps 1-3 provide a reasonable sequence, and individual attack examples show multi-step processes. However, validation checkpoints are largely missing - there's no explicit verification after credential extraction, no confirmation steps after ticket forging, and the ZeroLogon section's 'Restore password (important!)' is the only feedback loop. For destructive operations like DCSync and Golden Ticket creation, missing validation caps this at 2. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections (reconnaissance, credential attacks, Kerberos attacks, relay attacks, AD CS, CVEs) and appropriately defers advanced techniques to a single referenced file (references/advanced-attacks.md). The main content covers the most common attack paths while keeping the document navigable with clear headers and tables. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
d739c8b
- 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.