[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EPHB02816H97S2VVCY8B6F":3,"skill-same:01M7EPHB02816H97S2VVCY8B6F":50},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7EPHB02816H97S2VVCY8B6F","pentest-checklist",null,"Provide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fpentest-checklist\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: pentest-checklist\ndescription: \"Provide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.\"\nrisk: offensive\nsource: community\nauthor: zebbern\ndate_added: \"2026-02-27\"\n---\n\n> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n> AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments.\n\n# Pentest Checklist\n\n## Purpose\n\nProvide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.\n\n## Inputs\u002FPrerequisites\n\n- Clear business objectives for testing\n- Target environment information\n- Budget and timeline constraints\n- Stakeholder contacts and authorization\n- Legal agreements and scope documents\n\n## Outputs\u002FDeliverables\n\n- Defined pentest scope and objectives\n- Prepared testing environment\n- Security monitoring data\n- Vulnerability findings report\n- Remediation plan and verification\n\n## Core Workflow\n\n### Phase 1: Scope Definition\n\n#### Define Objectives\n\n- [ ] **Clarify testing purpose** - Determine goals (find vulnerabilities, compliance, customer assurance)\n- [ ] **Validate pentest necessity** - Ensure penetration test is the right solution\n- [ ] **Align outcomes with objectives** - Define success criteria\n\n**Reference Questions:**\n- Why are you doing this pentest?\n- What specific outcomes do you expect?\n- What will you do with the findings?\n\n#### Know Your Test Types\n\n| Type | Purpose | Scope |\n|------|---------|-------|\n| External Pentest | Assess external attack surface | Public-facing systems |\n| Internal Pentest | Assess insider threat risk | Internal network |\n| Web Application | Find application vulnerabilities | Specific applications |\n| Social Engineering | Test human security | Employees, processes |\n| Red Team | Full adversary simulation | Entire organization |\n\n#### Enumerate Likely Threats\n\n- [ ] **Identify high-risk areas** - Where could damage occur?\n- [ ] **Assess data sensitivity** - What data could be compromised?\n- [ ] **Review legacy systems** - Old systems often have vulnerabilities\n- [ ] **Map critical assets** - Prioritize testing targets\n\n#### Define Scope\n\n- [ ] **List in-scope systems** - IPs, domains, applications\n- [ ] **Define out-of-scope items** - Systems to avoid\n- [ ] **Set testing boundaries** - What techniques are allowed?\n- [ ] **Document exclusions** - Third-party systems, production data\n\n#### Budget Planning\n\n| Factor | Consideration |\n|--------|---------------|\n| Asset Value | Higher value = higher investment |\n| Complexity | More systems = more time |\n| Depth Required | Thorough testing costs more |\n| Reputation Value | Brand-name firms cost more |\n\n**Budget Reality Check:**\n- Cheap pentests often produce poor results\n- Align budget with asset criticality\n- Consider ongoing vs. one-time testing\n\n### Phase 2: Environment Preparation\n\n#### Prepare Test Environment\n\n- [ ] **Production vs. staging decision** - Determine where to test\n- [ ] **Set testing limits** - No DoS on production\n- [ ] **Schedule testing window** - Minimize business impact\n- [ ] **Create test accounts** - Provide appropriate access levels\n\n**Environment Options:**\n```\nProduction  - Realistic but risky\nStaging     - Safer but may differ from production\nClone       - Ideal but resource-intensive\n```\n\n#### Run Preliminary Scans\n\n- [ ] **Execute vulnerability scanners** - Find known issues first\n- [ ] **Fix obvious vulnerabilities** - Don't waste pentest time\n- [ ] **Document existing issues** - Share with testers\n\n**Common Pre-Scan Tools:**\n```bash\n# Network vulnerability scan\nnmap -sV --script vuln TARGET\n\n# Web vulnerability scan\nnikto -h http:\u002F\u002FTARGET\n```\n\n#### Review Security Policy\n\n- [ ] **Verify compliance requirements** - GDPR, PCI-DSS, HIPAA\n- [ ] **Document data handling rules** - Sensitive data procedures\n- [ ] **Confirm legal authorization** - Get written permission\n\n#### Notify Hosting Provider\n\n- [ ] **Check provider policies** - What testing is allowed?\n- [ ] **Submit authorization requests** - AWS, Azure, GCP requirements\n- [ ] **Document approvals** - Keep records\n\n**Cloud Provider Policies:**\n- AWS: https:\u002F\u002Faws.amazon.com\u002Fsecurity\u002Fpenetration-testing\u002F\n- Azure: https:\u002F\u002Fdocs.microsoft.com\u002Fsecurity\u002Fpentest\n- GCP: https:\u002F\u002Fcloud.google.com\u002Fsecurity\u002Foverview\n\n#### Freeze Developments\n\n- [ ] **Stop deployments during testing** - Maintain consistent environment\n- [ ] **Document current versions** - Record system states\n- [ ] **Avoid critical patches** - Unless security emergency\n\n### Phase 3: Expertise Selection\n\n#### Find Qualified Pentesters\n\n- [ ] **Seek recommendations** - Ask trusted sources\n- [ ] **Verify credentials** - OSCP, GPEN, CEH, CREST\n- [ ] **Check references** - Talk to previous clients\n- [ ] **Match expertise to scope** - Web, network, mobile specialists\n\n**Evaluation Criteria:**\n\n| Factor | Questions to Ask |\n|--------|------------------|\n| Experience | Years in field, similar projects |\n| Methodology | OWASP, PTES, custom approach |\n| Reporting | Sample reports, detail level |\n| Communication | Availability, update frequency |\n\n#### Define Methodology\n\n- [ ] **Select testing standard** - PTES, OWASP, NIST\n- [ ] **Determine access level** - Black box, gray box, white box\n- [ ] **Agree on techniques** - Manual vs. automated testing\n- [ ] **Set communication schedule** - Updates and escalation\n\n**Testing Approaches:**\n\n| Type | Access Level | Simulates |\n|------|-------------|-----------|\n| Black Box | No information | External attacker |\n| Gray Box | Partial access | Insider with limited access |\n| White Box | Full access | Insider\u002Fdetailed audit |\n\n#### Define Report Format\n\n- [ ] **Review sample reports** - Ensure quality meets needs\n- [ ] **Specify required sections** - Executive summary, technical details\n- [ ] **Request machine-readable output** - CSV, XML for tracking\n- [ ] **Agree on risk ratings** - CVSS, custom scale\n\n**Report Should Include:**\n- Executive summary for management\n- Technical findings with evidence\n- Risk ratings and prioritization\n- Remediation recommendations\n- Retesting guidance\n\n### Phase 4: Monitoring\n\n#### Implement Security Monitoring\n\n- [ ] **Deploy IDS\u002FIPS** - Intrusion detection systems\n- [ ] **Enable logging** - Comprehensive audit trails\n- [ ] **Configure SIEM** - Centralized log analysis\n- [ ] **Set up alerting** - Real-time notifications\n\n**Monitoring Tools:**\n```bash\n# Check security logs\ntail -f \u002Fvar\u002Flog\u002Fauth.log\ntail -f \u002Fvar\u002Flog\u002Fapache2\u002Faccess.log\n\n# Monitor network\ntcpdump -i eth0 -w capture.pcap\n```\n\n#### Configure Logging\n\n- [ ] **Centralize logs** - Aggregate from all systems\n- [ ] **Set retention periods** - Keep logs for analysis\n- [ ] **Enable detailed logging** - Application and system level\n- [ ] **Test log collection** - Verify all sources working\n\n**Key Logs to Monitor:**\n- Authentication events\n- Application errors\n- Network connections\n- File access\n- System changes\n\n#### Monitor Exception Tools\n\n- [ ] **Track error rates** - Unusual spikes indicate testing\n- [ ] **Brief operations team** - Distinguish testing from attacks\n- [ ] **Document baseline** - Normal vs. pentest activity\n\n#### Watch Security Tools\n\n- [ ] **Review IDS alerts** - Separate pentest from real attacks\n- [ ] **Monitor WAF logs** - Track blocked attempts\n- [ ] **Check endpoint protection** - Antivirus detections\n\n### Phase 5: Remediation\n\n#### Ensure Backups\n\n- [ ] **Verify backup integrity** - Test restoration\n- [ ] **Document recovery procedures** - Know how to restore\n- [ ] **Separate backup access** - Protect from testing\n\n#### Reserve Remediation Time\n\n- [ ] **Allocate team availability** - Post-pentest analysis\n- [ ] **Schedule fix implementation** - Address findings\n- [ ] **Plan verification testing** - Confirm fixes work\n\n#### Patch During Testing Policy\n\n- [ ] **Generally avoid patching** - Maintain consistent environment\n- [ ] **Exception for critical issues** - Security emergencies only\n- [ ] **Communicate changes** - Inform pentesters of any changes\n\n#### Cleanup Procedure\n\n- [ ] **Remove test artifacts** - Backdoors, scripts, files\n- [ ] **Delete test accounts** - Remove pentester access\n- [ ] **Restore configurations** - Return to original state\n- [ ] **Verify cleanup complete** - Audit all changes\n\n#### Schedule Next Pentest\n\n- [ ] **Determine frequency** - Annual, quarterly, after changes\n- [ ] **Consider continuous testing** - Bug bounty, ongoing assessments\n- [ ] **Budget for future tests** - Plan ahead\n\n**Testing Frequency Factors:**\n- Release frequency\n- Regulatory requirements\n- Risk tolerance\n- Past findings severity\n\n## Quick Reference\n\n### Pre-Pentest Checklist\n\n```\n□ Scope defined and documented\n□ Authorization obtained\n□ Environment prepared\n□ Hosting provider notified\n□ Team briefed\n□ Monitoring enabled\n□ Backups verified\n```\n\n### Post-Pentest Checklist\n\n```\n□ Report received and reviewed\n□ Findings prioritized\n□ Remediation assigned\n□ Fixes implemented\n□ Verification testing scheduled\n□ Environment cleaned up\n□ Next test scheduled\n```\n\n## Constraints\n\n- Production testing carries inherent risks\n- Budget limitations affect thoroughness\n- Time constraints may limit coverage\n- Tester expertise varies significantly\n- Findings become stale quickly\n\n## Examples\n\n### Example 1: Quick Scope Definition\n\n```markdown\n**Target:** Corporate web application (app.company.com)\n**Type:** Gray box web application pentest\n**Duration:** 5 business days\n**Excluded:** DoS testing, production database access\n**Access:** Standard user account provided\n```\n\n### Example 2: Monitoring Setup\n\n```bash\n# Enable comprehensive logging\nsudo systemctl restart rsyslog\nsudo systemctl restart auditd\n\n# Start packet capture\ntcpdump -i eth0 -w \u002Ftmp\u002Fpentest_capture.pcap &\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Scope creep | Document and require change approval |\n| Testing impacts production | Schedule off-hours, use staging |\n| Findings disputed | Provide detailed evidence, retest |\n| Remediation delayed | Prioritize by risk, set deadlines |\n| Budget exceeded | Define clear scope, fixed-price contracts |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","> **⚠️ AUTHORIZED USE ONLY**\n> This skill is for educational purposes or authorized security assessments only.\n> You must have explicit, written permission from the system owner before using this tool.\n> Misuse of this tool is illegal and strictly prohibited.\n\n> **Mandatory confirmation gate**\n> Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:\n> 1. Ask the user to state the exact target URL, IP, account, or resource.\n> 2. Ask the user to confirm written authorization and the permitted scope.\n> 3. Show the exact command(s) and explain their expected effect.\n> 4. Wait for explicit confirmation in the current conversation.\n>\n> Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.\n\n> AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments.\n\n# Pentest Checklist\n\n## Purpose\n\nProvide a comprehensive checklist for planning, executing, and following up on penetration tests. Ensure thorough preparation, proper scoping, and effective remediation of discovered vulnerabilities.\n\n## Inputs\u002FPrerequisites\n\n- Clear business objectives for testing\n- Target environment information\n- Budget and timeline constraints\n- Stakeholder contacts and authorization\n- Legal agreements and scope documents\n\n## Outputs\u002FDeliverables\n\n- Defined pentest scope and objectives\n- Prepared testing environment\n- Security monitoring data\n- Vulnerability findings report\n- Remediation plan and verification\n\n## Core Workflow\n\n### Phase 1: Scope Definition\n\n#### Define Objectives\n\n- [ ] **Clarify testing purpose** - Determine goals (find vulnerabilities, compliance, customer assurance)\n- [ ] **Validate pentest necessity** - Ensure penetration test is the right solution\n- [ ] **Align outcomes with objectives** - Define success criteria\n\n**Reference Questions:**\n- Why are you doing this pentest?\n- What specific outcomes do you expect?\n- What will you do with the findings?\n\n#### Know Your Test Types\n\n| Type | Purpose | Scope |\n|------|---------|-------|\n| External Pentest | Assess external attack surface | Public-facing systems |\n| Internal Pentest | Assess insider threat risk | Internal network |\n| Web Application | Find application vulnerabilities | Specific applications |\n| Social Engineering | Test human security | Employees, processes |\n| Red Team | Full adversary simulation | Entire organization |\n\n#### Enumerate Likely Threats\n\n- [ ] **Identify high-risk areas** - Where could damage occur?\n- [ ] **Assess data sensitivity** - What data could be compromised?\n- [ ] **Review legacy systems** - Old systems often have vulnerabilities\n- [ ] **Map critical assets** - Prioritize testing targets\n\n#### Define Scope\n\n- [ ] **List in-scope systems** - IPs, domains, applications\n- [ ] **Define out-of-scope items** - Systems to avoid\n- [ ] **Set testing boundaries** - What techniques are allowed?\n- [ ] **Document exclusions** - Third-party systems, production data\n\n#### Budget Planning\n\n| Factor | Consideration |\n|--------|---------------|\n| Asset Value | Higher value = higher investment |\n| Complexity | More systems = more time |\n| Depth Required | Thorough testing costs more |\n| Reputation Value | Brand-name firms cost more |\n\n**Budget Reality Check:**\n- Cheap pentests often produce poor results\n- Align budget with asset criticality\n- Consider ongoing vs. one-time testing\n\n### Phase 2: Environment Preparation\n\n#### Prepare Test Environment\n\n- [ ] **Production vs. staging decision** - Determine where to test\n- [ ] **Set testing limits** - No DoS on production\n- [ ] **Schedule testing window** - Minimize business impact\n- [ ] **Create test accounts** - Provide appropriate access levels\n\n**Environment Options:**\n```\nProduction  - Realistic but risky\nStaging     - Safer but may differ from production\nClone       - Ideal but resource-intensive\n```\n\n#### Run Preliminary Scans\n\n- [ ] **Execute vulnerability scanners** - Find known issues first\n- [ ] **Fix obvious vulnerabilities** - Don't waste pentest time\n- [ ] **Document existing issues** - Share with testers\n\n**Common Pre-Scan Tools:**\n```bash\n# Network vulnerability scan\nnmap -sV --script vuln TARGET\n\n# Web vulnerability scan\nnikto -h http:\u002F\u002FTARGET\n```\n\n#### Review Security Policy\n\n- [ ] **Verify compliance requirements** - GDPR, PCI-DSS, HIPAA\n- [ ] **Document data handling rules** - Sensitive data procedures\n- [ ] **Confirm legal authorization** - Get written permission\n\n#### Notify Hosting Provider\n\n- [ ] **Check provider policies** - What testing is allowed?\n- [ ] **Submit authorization requests** - AWS, Azure, GCP requirements\n- [ ] **Document approvals** - Keep records\n\n**Cloud Provider Policies:**\n- AWS: https:\u002F\u002Faws.amazon.com\u002Fsecurity\u002Fpenetration-testing\u002F\n- Azure: https:\u002F\u002Fdocs.microsoft.com\u002Fsecurity\u002Fpentest\n- GCP: https:\u002F\u002Fcloud.google.com\u002Fsecurity\u002Foverview\n\n#### Freeze Developments\n\n- [ ] **Stop deployments during testing** - Maintain consistent environment\n- [ ] **Document current versions** - Record system states\n- [ ] **Avoid critical patches** - Unless security emergency\n\n### Phase 3: Expertise Selection\n\n#### Find Qualified Pentesters\n\n- [ ] **Seek recommendations** - Ask trusted sources\n- [ ] **Verify credentials** - OSCP, GPEN, CEH, CREST\n- [ ] **Check references** - Talk to previous clients\n- [ ] **Match expertise to scope** - Web, network, mobile specialists\n\n**Evaluation Criteria:**\n\n| Factor | Questions to Ask |\n|--------|------------------|\n| Experience | Years in field, similar projects |\n| Methodology | OWASP, PTES, custom approach |\n| Reporting | Sample reports, detail level |\n| Communication | Availability, update frequency |\n\n#### Define Methodology\n\n- [ ] **Select testing standard** - PTES, OWASP, NIST\n- [ ] **Determine access level** - Black box, gray box, white box\n- [ ] **Agree on techniques** - Manual vs. automated testing\n- [ ] **Set communication schedule** - Updates and escalation\n\n**Testing Approaches:**\n\n| Type | Access Level | Simulates |\n|------|-------------|-----------|\n| Black Box | No information | External attacker |\n| Gray Box | Partial access | Insider with limited access |\n| White Box | Full access | Insider\u002Fdetailed audit |\n\n#### Define Report Format\n\n- [ ] **Review sample reports** - Ensure quality meets needs\n- [ ] **Specify required sections** - Executive summary, technical details\n- [ ] **Request machine-readable output** - CSV, XML for tracking\n- [ ] **Agree on risk ratings** - CVSS, custom scale\n\n**Report Should Include:**\n- Executive summary for management\n- Technical findings with evidence\n- Risk ratings and prioritization\n- Remediation recommendations\n- Retesting guidance\n\n### Phase 4: Monitoring\n\n#### Implement Security Monitoring\n\n- [ ] **Deploy IDS\u002FIPS** - Intrusion detection systems\n- [ ] **Enable logging** - Comprehensive audit trails\n- [ ] **Configure SIEM** - Centralized log analysis\n- [ ] **Set up alerting** - Real-time notifications\n\n**Monitoring Tools:**\n```bash\n# Check security logs\ntail -f \u002Fvar\u002Flog\u002Fauth.log\ntail -f \u002Fvar\u002Flog\u002Fapache2\u002Faccess.log\n\n# Monitor network\ntcpdump -i eth0 -w capture.pcap\n```\n\n#### Configure Logging\n\n- [ ] **Centralize logs** - Aggregate from all systems\n- [ ] **Set retention periods** - Keep logs for analysis\n- [ ] **Enable detailed logging** - Application and system level\n- [ ] **Test log collection** - Verify all sources working\n\n**Key Logs to Monitor:**\n- Authentication events\n- Application errors\n- Network connections\n- File access\n- System changes\n\n#### Monitor Exception Tools\n\n- [ ] **Track error rates** - Unusual spikes indicate testing\n- [ ] **Brief operations team** - Distinguish testing from attacks\n- [ ] **Document baseline** - Normal vs. pentest activity\n\n#### Watch Security Tools\n\n- [ ] **Review IDS alerts** - Separate pentest from real attacks\n- [ ] **Monitor WAF logs** - Track blocked attempts\n- [ ] **Check endpoint protection** - Antivirus detections\n\n### Phase 5: Remediation\n\n#### Ensure Backups\n\n- [ ] **Verify backup integrity** - Test restoration\n- [ ] **Document recovery procedures** - Know how to restore\n- [ ] **Separate backup access** - Protect from testing\n\n#### Reserve Remediation Time\n\n- [ ] **Allocate team availability** - Post-pentest analysis\n- [ ] **Schedule fix implementation** - Address findings\n- [ ] **Plan verification testing** - Confirm fixes work\n\n#### Patch During Testing Policy\n\n- [ ] **Generally avoid patching** - Maintain consistent environment\n- [ ] **Exception for critical issues** - Security emergencies only\n- [ ] **Communicate changes** - Inform pentesters of any changes\n\n#### Cleanup Procedure\n\n- [ ] **Remove test artifacts** - Backdoors, scripts, files\n- [ ] **Delete test accounts** - Remove pentester access\n- [ ] **Restore configurations** - Return to original state\n- [ ] **Verify cleanup complete** - Audit all changes\n\n#### Schedule Next Pentest\n\n- [ ] **Determine frequency** - Annual, quarterly, after changes\n- [ ] **Consider continuous testing** - Bug bounty, ongoing assessments\n- [ ] **Budget for future tests** - Plan ahead\n\n**Testing Frequency Factors:**\n- Release frequency\n- Regulatory requirements\n- Risk tolerance\n- Past findings severity\n\n## Quick Reference\n\n### Pre-Pentest Checklist\n\n```\n□ Scope defined and documented\n□ Authorization obtained\n□ Environment prepared\n□ Hosting provider notified\n□ Team briefed\n□ Monitoring enabled\n□ Backups verified\n```\n\n### Post-Pentest Checklist\n\n```\n□ Report received and reviewed\n□ Findings prioritized\n□ Remediation assigned\n□ Fixes implemented\n□ Verification testing scheduled\n□ Environment cleaned up\n□ Next test scheduled\n```\n\n## Constraints\n\n- Production testing carries inherent risks\n- Budget limitations affect thoroughness\n- Time constraints may limit coverage\n- Tester expertise varies significantly\n- Findings become stale quickly\n\n## Examples\n\n### Example 1: Quick Scope Definition\n\n```markdown\n**Target:** Corporate web application (app.company.com)\n**Type:** Gray box web application pentest\n**Duration:** 5 business days\n**Excluded:** DoS testing, production database access\n**Access:** Standard user account provided\n```\n\n### Example 2: Monitoring Setup\n\n```bash\n# Enable comprehensive logging\nsudo systemctl restart rsyslog\nsudo systemctl restart auditd\n\n# Start packet capture\ntcpdump -i eth0 -w \u002Ftmp\u002Fpentest_capture.pcap &\n```\n\n## Troubleshooting\n\n| Issue | Solution |\n|-------|----------|\n| Scope creep | Document and require change approval |\n| Testing impacts production | Schedule off-hours, use staging |\n| Findings disputed | Provide detailed evidence, retest |\n| Remediation delayed | Prioritize by risk, set deadlines |\n| Budget exceeded | Define clear scope, fixed-price contracts |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"author":25,"source":26,"date_added":27,"description":7},"offensive","zebbern","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","04-安全渗透\u002Fpentest-checklist",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill pentest-checklist",{"tool":42,"command":43},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill pentest-checklist",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill pentest-checklist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F04-安全渗透\u002Fpentest-checklist\u002FSKILL.md",true,[],[51,59,64,71,78,85],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":58},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":60,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":58},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":58},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":58},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":58},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":58},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]