red-team-tactics

davila7/claude-code-templates · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/davila7/claude-code-templates --skill red-team-tactics
0 commentsdiscussion
summary

Adversary simulation principles based on MITRE ATT&CK framework.

skill.md

Red Team Tactics

Adversary simulation principles based on MITRE ATT&CK framework.


1. MITRE ATT&CK Phases

Attack Lifecycle

RECONNAISSANCE → INITIAL ACCESS → EXECUTION → PERSISTENCE
       ↓              ↓              ↓            ↓
   PRIVILEGE ESC → DEFENSE EVASION → CRED ACCESS → DISCOVERY
       ↓              ↓              ↓            ↓
LATERAL MOVEMENT → COLLECTION → C2 → EXFILTRATION → IMPACT

Phase Objectives

Phase Objective
Recon Map attack surface
Initial Access Get first foothold
Execution Run code on target
Persistence Survive reboots
Privilege Escalation Get admin/root
Defense Evasion Avoid detection
Credential Access Harvest credentials
Discovery Map internal network
Lateral Movement Spread to other systems
Collection Gather target data
C2 Maintain command channel
Exfiltration Extract data

2. Reconnaissance Principles

Passive vs Active

Type Trade-off
Passive No target contact, limited info
Active Direct contact, more detection risk

Information Targets

Category Value
Technology stack Attack vector selection
Employee info Social engineering
Network ranges Scanning scope
Third parties Supply chain attack

3. Initial Access Vectors

Selection Criteria

Vector When to Use
Phishing Human target, email access
Public exploits Vulnerable services exposed
Valid credentials Leaked or cracked
Supply chain Third-party access

4. Privilege Escalation Principles

Windows Targets

Check Opportunity
Unquoted service paths Write to path
Weak service permissions Modify service
Token privileges Abuse SeDebug, etc.
Stored credentials Harvest

Linux Targets

Check Opportunity
SUID binaries Execute as owner
Sudo misconfiguration Command execution
Kernel vulnerabilities Kernel exploits
Cron jobs Writable scripts

5. Defense Evasion Principles

Key Techniques

Technique Purpose
LOLBins Use legitimate tools
Obfuscation Hide malicious code
Timestomping Hide file modifications
Log clearing Remove evidence

Operational Security

  • Work during business hours
  • Mimic legitimate traffic patterns
  • Use encrypted channels
  • Blend with normal behavior

6. Lateral Movement Principles

Credential Types

Type Use
Password Standard auth
Hash Pass-the-hash
Ticket Pass-the-ticket
Certificate Certificate auth

Movement Paths

  • Admin shares
  • Remote services (RDP, SSH, WinRM)
  • Exploitation of internal services

7. Active Directory Attacks

Attack Categories

Attack Target
Kerberoasting Service account passwords
AS-REP Roasting Accounts without pre-auth
DCSync Domain credentials
Golden Ticket Persistent domain access

8. Reporting Principles

Attack Narrative

Document the full attack chain:

  1. How initial access was gained
  2. What techniques were used
  3. What objectives were achieved
  4. Where detection failed

Detection Gaps

For each successful technique:

  • What should have detected it?
  • Why didn't detection work?
  • How to improve detection

9. Ethical Boundaries

Always

  • Stay within scope
  • Minimize impact
  • Report immediately if real threat found
  • Document all actions

Never

  • Destroy production data
  • Cause denial of service (unless scoped)
  • Access beyond proof of concept
  • Retain sensitive data

10. Anti-Patterns

❌ Don't ✅ Do
Rush to exploitation Follow methodology
Cause damage Minimize impact
Skip reporting Document everything
Ignore scope Stay within boundaries

Remember: Red team simulates attackers to improve defenses, not to cause harm.

how to use red-team-tactics

How to use red-team-tactics on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add red-team-tactics
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/davila7/claude-code-templates --skill red-team-tactics

The skills CLI fetches red-team-tactics from GitHub repository davila7/claude-code-templates and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/red-team-tactics

Reload or restart Cursor to activate red-team-tactics. Access the skill through slash commands (e.g., /red-team-tactics) or your agent's skill management interface.

Security & Verification 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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • 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

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.634 reviews
  • Noor Anderson· Dec 20, 2024

    red-team-tactics fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ira Shah· Dec 16, 2024

    We added red-team-tactics from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Maya Singh· Nov 7, 2024

    red-team-tactics reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Maya Harris· Oct 26, 2024

    Registry listing for red-team-tactics matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Oshnikdeep· Sep 25, 2024

    red-team-tactics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Hassan Bhatia· Sep 17, 2024

    Keeps context tight: red-team-tactics is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Ganesh Mohane· Aug 16, 2024

    Keeps context tight: red-team-tactics is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Hassan Anderson· Aug 8, 2024

    red-team-tactics is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Sofia Smith· Jul 27, 2024

    Solid pick for teams standardizing on skills: red-team-tactics is focused, and the summary matches what you get after install.

  • Zaid Gill· Jul 23, 2024

    I recommend red-team-tactics for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 34

1 / 4