[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM6CV072YWYKMMACVYSY68":3,"skill-same:01M7CM6CV072YWYKMMACVYSY68":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7CM6CV072YWYKMMACVYSY68","red-team-tactics",null,"Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.","haliltek\u002Fdev.tr","haliltek","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31656259?v=4","01M7CKZCVHYRZ5CFNDBMFT5S7Q","Halil TEK","01M7CKZCWH3RX91D93NHE4DP2J",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fred-team-tactics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: red-team-tactics\ndescription: Red team tactics principles based on MITRE ATT&CK. Attack phases, detection evasion, reporting.\nwhen_to_use: \"When performing penetration testing, red team exercises, or evaluating attack surfaces using MITRE ATT&CK framework.\"\nallowed-tools: Read, Glob, Grep\nversion: 1.0.0\n---\n\n# Red Team Tactics\n\n> Adversary simulation principles based on MITRE ATT&CK framework.\n\n---\n\n## 1. MITRE ATT&CK Phases\n\n### Attack Lifecycle\n\n```\nRECONNAISSANCE → INITIAL ACCESS → EXECUTION → PERSISTENCE\n       ↓              ↓              ↓            ↓\n   PRIVILEGE ESC → DEFENSE EVASION → CRED ACCESS → DISCOVERY\n       ↓              ↓              ↓            ↓\nLATERAL MOVEMENT → COLLECTION → C2 → EXFILTRATION → IMPACT\n```\n\n### Phase Objectives\n\n| Phase | Objective |\n|-------|-----------|\n| **Recon** | Map attack surface |\n| **Initial Access** | Get first foothold |\n| **Execution** | Run code on target |\n| **Persistence** | Survive reboots |\n| **Privilege Escalation** | Get admin\u002Froot |\n| **Defense Evasion** | Avoid detection |\n| **Credential Access** | Harvest credentials |\n| **Discovery** | Map internal network |\n| **Lateral Movement** | Spread to other systems |\n| **Collection** | Gather target data |\n| **C2** | Maintain command channel |\n| **Exfiltration** | Extract data |\n\n---\n\n## 2. Reconnaissance Principles\n\n### Passive vs Active\n\n| Type | Trade-off |\n|------|-----------|\n| **Passive** | No target contact, limited info |\n| **Active** | Direct contact, more detection risk |\n\n### Information Targets\n\n| Category | Value |\n|----------|-------|\n| Technology stack | Attack vector selection |\n| Employee info | Social engineering |\n| Network ranges | Scanning scope |\n| Third parties | Supply chain attack |\n\n---\n\n## 3. Initial Access Vectors\n\n### Selection Criteria\n\n| Vector | When to Use |\n|--------|-------------|\n| **Phishing** | Human target, email access |\n| **Public exploits** | Vulnerable services exposed |\n| **Valid credentials** | Leaked or cracked |\n| **Supply chain** | Third-party access |\n\n---\n\n## 4. Privilege Escalation Principles\n\n### Windows Targets\n\n| Check | Opportunity |\n|-------|-------------|\n| Unquoted service paths | Write to path |\n| Weak service permissions | Modify service |\n| Token privileges | Abuse SeDebug, etc. |\n| Stored credentials | Harvest |\n\n### Linux Targets\n\n| Check | Opportunity |\n|-------|-------------|\n| SUID binaries | Execute as owner |\n| Sudo misconfiguration | Command execution |\n| Kernel vulnerabilities | Kernel exploits |\n| Cron jobs | Writable scripts |\n\n---\n\n## 5. Defense Evasion Principles\n\n### Key Techniques\n\n| Technique | Purpose |\n|-----------|---------|\n| LOLBins | Use legitimate tools |\n| Obfuscation | Hide malicious code |\n| Timestomping | Hide file modifications |\n| Log clearing | Remove evidence |\n\n### Operational Security\n\n- Work during business hours\n- Mimic legitimate traffic patterns\n- Use encrypted channels\n- Blend with normal behavior\n\n---\n\n## 6. Lateral Movement Principles\n\n### Credential Types\n\n| Type | Use |\n|------|-----|\n| Password | Standard auth |\n| Hash | Pass-the-hash |\n| Ticket | Pass-the-ticket |\n| Certificate | Certificate auth |\n\n### Movement Paths\n\n- Admin shares\n- Remote services (RDP, SSH, WinRM)\n- Exploitation of internal services\n\n---\n\n## 7. Active Directory Attacks\n\n### Attack Categories\n\n| Attack | Target |\n|--------|--------|\n| Kerberoasting | Service account passwords |\n| AS-REP Roasting | Accounts without pre-auth |\n| DCSync | Domain credentials |\n| Golden Ticket | Persistent domain access |\n\n---\n\n## 8. Reporting Principles\n\n### Attack Narrative\n\nDocument the full attack chain:\n1. How initial access was gained\n2. What techniques were used\n3. What objectives were achieved\n4. Where detection failed\n\n### Detection Gaps\n\nFor each successful technique:\n- What should have detected it?\n- Why didn't detection work?\n- How to improve detection\n\n---\n\n## 9. Ethical Boundaries\n\n### Always\n\n- Stay within scope\n- Minimize impact\n- Report immediately if real threat found\n- Document all actions\n\n### Never\n\n- Destroy production data\n- Cause denial of service (unless scoped)\n- Access beyond proof of concept\n- Retain sensitive data\n\n---\n\n## 10. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Rush to exploitation | Follow methodology |\n| Cause damage | Minimize impact |\n| Skip reporting | Document everything |\n| Ignore scope | Stay within boundaries |\n\n---\n\n> **Remember:** Red team simulates attackers to improve defenses, not to cause harm.\n","# Red Team Tactics\n\n> Adversary simulation principles based on MITRE ATT&CK framework.\n\n---\n\n## 1. MITRE ATT&CK Phases\n\n### Attack Lifecycle\n\n```\nRECONNAISSANCE → INITIAL ACCESS → EXECUTION → PERSISTENCE\n       ↓              ↓              ↓            ↓\n   PRIVILEGE ESC → DEFENSE EVASION → CRED ACCESS → DISCOVERY\n       ↓              ↓              ↓            ↓\nLATERAL MOVEMENT → COLLECTION → C2 → EXFILTRATION → IMPACT\n```\n\n### Phase Objectives\n\n| Phase | Objective |\n|-------|-----------|\n| **Recon** | Map attack surface |\n| **Initial Access** | Get first foothold |\n| **Execution** | Run code on target |\n| **Persistence** | Survive reboots |\n| **Privilege Escalation** | Get admin\u002Froot |\n| **Defense Evasion** | Avoid detection |\n| **Credential Access** | Harvest credentials |\n| **Discovery** | Map internal network |\n| **Lateral Movement** | Spread to other systems |\n| **Collection** | Gather target data |\n| **C2** | Maintain command channel |\n| **Exfiltration** | Extract data |\n\n---\n\n## 2. Reconnaissance Principles\n\n### Passive vs Active\n\n| Type | Trade-off |\n|------|-----------|\n| **Passive** | No target contact, limited info |\n| **Active** | Direct contact, more detection risk |\n\n### Information Targets\n\n| Category | Value |\n|----------|-------|\n| Technology stack | Attack vector selection |\n| Employee info | Social engineering |\n| Network ranges | Scanning scope |\n| Third parties | Supply chain attack |\n\n---\n\n## 3. Initial Access Vectors\n\n### Selection Criteria\n\n| Vector | When to Use |\n|--------|-------------|\n| **Phishing** | Human target, email access |\n| **Public exploits** | Vulnerable services exposed |\n| **Valid credentials** | Leaked or cracked |\n| **Supply chain** | Third-party access |\n\n---\n\n## 4. Privilege Escalation Principles\n\n### Windows Targets\n\n| Check | Opportunity |\n|-------|-------------|\n| Unquoted service paths | Write to path |\n| Weak service permissions | Modify service |\n| Token privileges | Abuse SeDebug, etc. |\n| Stored credentials | Harvest |\n\n### Linux Targets\n\n| Check | Opportunity |\n|-------|-------------|\n| SUID binaries | Execute as owner |\n| Sudo misconfiguration | Command execution |\n| Kernel vulnerabilities | Kernel exploits |\n| Cron jobs | Writable scripts |\n\n---\n\n## 5. Defense Evasion Principles\n\n### Key Techniques\n\n| Technique | Purpose |\n|-----------|---------|\n| LOLBins | Use legitimate tools |\n| Obfuscation | Hide malicious code |\n| Timestomping | Hide file modifications |\n| Log clearing | Remove evidence |\n\n### Operational Security\n\n- Work during business hours\n- Mimic legitimate traffic patterns\n- Use encrypted channels\n- Blend with normal behavior\n\n---\n\n## 6. Lateral Movement Principles\n\n### Credential Types\n\n| Type | Use |\n|------|-----|\n| Password | Standard auth |\n| Hash | Pass-the-hash |\n| Ticket | Pass-the-ticket |\n| Certificate | Certificate auth |\n\n### Movement Paths\n\n- Admin shares\n- Remote services (RDP, SSH, WinRM)\n- Exploitation of internal services\n\n---\n\n## 7. Active Directory Attacks\n\n### Attack Categories\n\n| Attack | Target |\n|--------|--------|\n| Kerberoasting | Service account passwords |\n| AS-REP Roasting | Accounts without pre-auth |\n| DCSync | Domain credentials |\n| Golden Ticket | Persistent domain access |\n\n---\n\n## 8. Reporting Principles\n\n### Attack Narrative\n\nDocument the full attack chain:\n1. How initial access was gained\n2. What techniques were used\n3. What objectives were achieved\n4. Where detection failed\n\n### Detection Gaps\n\nFor each successful technique:\n- What should have detected it?\n- Why didn't detection work?\n- How to improve detection\n\n---\n\n## 9. Ethical Boundaries\n\n### Always\n\n- Stay within scope\n- Minimize impact\n- Report immediately if real threat found\n- Document all actions\n\n### Never\n\n- Destroy production data\n- Cause denial of service (unless scoped)\n- Access beyond proof of concept\n- Retain sensitive data\n\n---\n\n## 10. Anti-Patterns\n\n| ❌ Don't | ✅ Do |\n|----------|-------|\n| Rush to exploitation | Follow methodology |\n| Cause damage | Minimize impact |\n| Skip reporting | Document everything |\n| Ignore scope | Stay within boundaries |\n\n---\n\n> **Remember:** Red team simulates attackers to improve defenses, not to cause harm.\n",{"name":5,"version":24,"description":7,"when_to_use":25,"allowed-tools":26},"1.0.0","When performing penetration testing, red team exercises, or evaluating attack surfaces using MITRE ATT&CK framework.","Read, Glob, Grep","main","35fc33da79b31d7f8dadfc704083baff1b5672a0",".agents\u002Fskills\u002Fred-team-tactics","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr","https:\u002F\u002Fgithub.com\u002Fhaliltek","2026-11-13 01:38:48",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add haliltek\u002Fdev.tr --skill red-team-tactics",{"tool":39,"command":40},"bunx","bunx skills add haliltek\u002Fdev.tr --skill red-team-tactics",{"tool":42,"command":43},"pnpm","pnpm dlx skills add haliltek\u002Fdev.tr --skill red-team-tactics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fred-team-tactics\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7CM8JAC0X6HVS8VCHH51KPZ","respectfully","Wraps any prompt with a reminder to respect CLAUDE.md files","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frespectfully\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7CM8FPHK4J5EP607Y77XHA4","recruiter","Think like a skeptical technical recruiter when working on the daily.dev Recruiter platform. Use when reviewing UI\u002FUX, features, or code in webapp\u002Fpages\u002Frecruiter.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frecruiter\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7CM8CB9XR2W46XJ3T2X0245","changelog","Generate a daily.dev changelog post for a new feature or update. Use when a team member needs to write a changelog announcement.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7CM88HKHZP4S2H9GYKWCBPB","webapp-testing","Web application testing principles. E2E, Playwright, deep audit strategies.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7CM831R2XYCHFNRGXD6NYS1","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7CM7XTJ13ZQFZ9Y5SRYF8CP","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Fhaliltek\u002Fdev.tr\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fvulnerability-scanner\u002FSKILL.md",[],[]]