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.
62
73%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Critical
Do not install without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-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 clearly carve out a distinct niche around Active Directory offensive security. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over others. Adding trigger guidance would elevate this from good to excellent.
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 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
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 broad range of AD attack techniques. Its main weaknesses are the length (could benefit from better progressive disclosure into sub-files) and the lack of explicit validation/verification steps between attack phases. The content is well-organized but borders on being a monolithic reference rather than a guided workflow.
Suggestions
Add explicit validation checkpoints between attack steps (e.g., 'Verify ticket was obtained: klist' or 'Confirm access: whoami /groups') to improve workflow clarity.
Split the large content into sub-files (e.g., kerberos-attacks.md, credential-attacks.md, relay-attacks.md) and keep SKILL.md as a concise overview with references, improving progressive disclosure.
Remove redundancy between the Essential Tools table and the Quick Reference table, and trim the boilerplate 'When to Use' section and the 'Purpose' section that duplicates the frontmatter description.
| 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 tool table and quick reference table are somewhat redundant with each other. | 2 / 3 |
Actionability | 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, and the constraints section is more of a checklist than integrated validation. The ZeroLogon section notably includes a restore step, but most attack sequences lack verification/feedback loops. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical grouping, and references an 'advanced-attacks.md' file for additional techniques. However, the main file is quite long (~300 lines of dense content) and could benefit from splitting credential attacks, Kerberos attacks, and NTLM relay into separate referenced files. The bundle has no supporting files, so the reference to 'references/advanced-attacks.md' is unverifiable. | 2 / 3 |
Total | 9 / 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
- boisenoise/skills-collections
- Commit
e41e34a
- 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.