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.

Quality

73%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Critical

Do not install without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/active-directory-attacks/SKILL.md

Quality

Content

64%

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

This is a highly actionable skill with excellent concrete commands and tool-specific syntax covering a comprehensive range of AD attack techniques. Its main weaknesses are the lack of validation checkpoints between attack steps (e.g., confirming credential extraction succeeded before attempting lateral movement) and the monolithic structure that packs extensive content into a single file. Some minor verbosity in boilerplate sections and a duplicative quick reference table slightly reduce token efficiency.

Suggestions

Add explicit validation/verification steps between attack phases (e.g., 'Verify hash extraction: crackmapexec smb target -u user -H hash' before proceeding to lateral movement)

Split detailed attack categories (Kerberos attacks, NTLM relay, AD CS, CVEs) into separate reference files and keep SKILL.md as a concise overview with links

Remove the duplicative Quick Reference table or replace the detailed sections above with just the quick reference plus links to detailed files

Remove boilerplate sections like 'When to Use' and trim 'Inputs/Prerequisites' and 'Outputs/Deliverables' which add little value for Claude

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with concrete commands rather than explanations, but includes some unnecessary sections like the 'Purpose' restating the description, the 'Inputs/Prerequisites' and 'Outputs/Deliverables' sections that are somewhat obvious, and the 'When to Use' boilerplate at the end. The Quick Reference table duplicates commands already shown above. Overall reasonably lean but could be tightened.	2 / 3
Actionability	Excellent actionability throughout — nearly every technique includes fully executable, copy-paste-ready commands with specific tool invocations, flags, and arguments. Multiple tool alternatives are provided for each attack type, and the examples section shows complete end-to-end attack chains with numbered steps.	3 / 3
Workflow Clarity	The core workflow has numbered steps for initial phases (clock sync, recon, enumeration), and the examples show sequenced attack chains. However, validation checkpoints are largely missing — there's no explicit 'verify this worked before proceeding' between steps. The ZeroLogon section notably includes a restore step, but most attack sequences lack verification/feedback loops for confirming success before moving to the next phase.	2 / 3
Progressive Disclosure	The content references 'references/advanced-attacks.md' for advanced techniques, which is good progressive disclosure. However, the main file is quite long (~300+ lines) with substantial inline detail that could be split into separate reference files (e.g., Kerberos attacks, NTLM relay, AD CS attacks). The structure is well-organized with clear headers, but the monolithic nature could benefit from better splitting.	2 / 3
	Total	9 / 12 Passed

Description

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 clearly carve out a distinct niche around Active Directory offensive security. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over others.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about attacking Active Directory, AD exploitation, Kerberoasting, pass-the-hash, DCSync, or red team engagements targeting Windows domains.'

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, concrete categories of activity.	3 / 3
Completeness	Clearly answers 'what does this do' with specific attack categories, but lacks an explicit 'Use when...' clause. The context of red team/pentesting is mentioned but not framed as trigger guidance for when Claude should select this skill.	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 pentester would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Microsoft Active Directory attack techniques for red teaming. 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

Validation

90%

Warnings & errors only

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: d89c349

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.