[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFRXZMGZMR1WTPD54EV761":3,"skill-same:01M6AFRXZMGZMR1WTPD54EV761":91},{"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":26,"publishedAt":53,"linkOnly":54,"markdownContent":55,"markdownBody":56,"frontMatter":57,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":66,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":69,"updatedAt":70,"install":71,"resources":84},"01M6AFRXZMGZMR1WTPD54EV761","burp-suite-testing",null,"This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp Repeater\", \"analyze HTTP history\", or \"configure proxy for web testing\". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33481,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fburp-suite-testing\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52],"suite","burp suite","burp suite testing","testing","history","when","features","for","traffic","web application security","Security Testing","guidance","scanning","use","user","analyze","configure","vulnerability","proxy","vulnerability scanning","core","http","web","test","security","application security","2026-11-10 10:12:30",false,"---\nname: burp-suite-testing\ndescription: This skill should be used when the user asks to \"intercept HTTP traffic\", \"modify web requests\", \"use Burp Suite for testing\", \"perform web vulnerability scanning\", \"test with Burp Repeater\", \"analyze HTTP history\", or \"configure proxy for web testing\". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.\nmetadata:\n  author: zebbern\n  version: \"1.1\"\n---\n\n# Burp Suite Web Application Testing\n\n## Purpose\n\nExecute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows. This skill enables systematic discovery and exploitation of web application vulnerabilities through proxy-based testing methodology.\n\n## Inputs \u002F Prerequisites\n\n### Required Tools\n- Burp Suite Community or Professional Edition installed\n- Burp's embedded browser or configured external browser\n- Target web application URL\n- Valid credentials for authenticated testing (if applicable)\n\n### Environment Setup\n- Burp Suite launched with temporary or named project\n- Proxy listener active on 127.0.0.1:8080 (default)\n- Browser configured to use Burp proxy (or use Burp's browser)\n- CA certificate installed for HTTPS interception\n\n### Editions Comparison\n| Feature | Community | Professional |\n|---------|-----------|--------------|\n| Proxy | ✓ | ✓ |\n| Repeater | ✓ | ✓ |\n| Intruder | Limited | Full |\n| Scanner | ✗ | ✓ |\n| Extensions | ✓ | ✓ |\n\n## Outputs \u002F Deliverables\n\n### Primary Outputs\n- Intercepted and modified HTTP requests\u002Fresponses\n- Vulnerability scan reports with remediation advice\n- HTTP history and site map documentation\n- Proof-of-concept exploits for identified vulnerabilities\n\n## Core Workflow\n\n### Phase 1: Intercepting HTTP Traffic\n\n#### Launch Burp's Browser\nNavigate to integrated browser for seamless proxy integration:\n\n1. Open Burp Suite and create\u002Fopen project\n2. Go to **Proxy > Intercept** tab\n3. Click **Open Browser** to launch preconfigured browser\n4. Position windows to view both Burp and browser simultaneously\n\n#### Configure Interception\nControl which requests are captured:\n\n```\nProxy > Intercept > Intercept is on\u002Foff toggle\n\nWhen ON: Requests pause for review\u002Fmodification\nWhen OFF: Requests pass through, logged to history\n```\n\n#### Intercept and Forward Requests\nProcess intercepted traffic:\n\n1. Set intercept toggle to **Intercept on**\n2. Navigate to target URL in browser\n3. Observe request held in Proxy > Intercept tab\n4. Review request contents (headers, parameters, body)\n5. Click **Forward** to send request to server\n6. Continue forwarding subsequent requests until page loads\n\n#### View HTTP History\nAccess complete traffic log:\n\n1. Go to **Proxy > HTTP history** tab\n2. Click any entry to view full request\u002Fresponse\n3. Sort by clicking column headers (# for chronological order)\n4. Use filters to focus on relevant traffic\n\n### Phase 2: Modifying Requests\n\n#### Intercept and Modify\nChange request parameters before forwarding:\n\n1. Enable interception: **Intercept on**\n2. Trigger target request in browser\n3. Locate parameter to modify in intercepted request\n4. Edit value directly in request editor\n5. Click **Forward** to send modified request\n\n#### Common Modification Targets\n| Target | Example | Purpose |\n|--------|---------|---------|\n| Price parameters | `price=1` | Test business logic |\n| User IDs | `userId=admin` | Test access control |\n| Quantity values | `qty=-1` | Test input validation |\n| Hidden fields | `isAdmin=true` | Test privilege escalation |\n\n#### Example: Price Manipulation\n\n```http\nPOST \u002Fcart HTTP\u002F1.1\nHost: target.com\nContent-Type: application\u002Fx-www-form-urlencoded\n\nproductId=1&quantity=1&price=100\n\n# Modify to:\nproductId=1&quantity=1&price=1\n```\n\nResult: Item added to cart at modified price.\n\n### Phase 3: Setting Target Scope\n\n#### Define Scope\nFocus testing on specific target:\n\n1. Go to **Target > Site map**\n2. Right-click target host in left panel\n3. Select **Add to scope**\n4. When prompted, click **Yes** to exclude out-of-scope traffic\n\n#### Filter by Scope\nRemove noise from HTTP history:\n\n1. Click display filter above HTTP history\n2. Select **Show only in-scope items**\n3. History now shows only target site traffic\n\n#### Scope Benefits\n- Reduces clutter from third-party requests\n- Prevents accidental testing of out-of-scope sites\n- Improves scanning efficiency\n- Creates cleaner reports\n\n### Phase 4: Using Burp Repeater\n\n#### Send Request to Repeater\nPrepare request for manual testing:\n\n1. Identify interesting request in HTTP history\n2. Right-click request and select **Send to Repeater**\n3. Go to **Repeater** tab to access request\n\n#### Modify and Resend\nTest different inputs efficiently:\n\n```\n1. View request in Repeater tab\n2. Modify parameter values\n3. Click Send to submit request\n4. Review response in right panel\n5. Use navigation arrows to review request history\n```\n\n#### Repeater Testing Workflow\n\n```\nOriginal Request:\nGET \u002Fproduct?productId=1 HTTP\u002F1.1\n\nTest 1: productId=2    → Valid product response\nTest 2: productId=999  → Not Found response  \nTest 3: productId='    → Error\u002Fexception response\nTest 4: productId=1 OR 1=1 → SQL injection test\n```\n\n#### Analyze Responses\nLook for indicators of vulnerabilities:\n\n- Error messages revealing stack traces\n- Framework\u002Fversion information disclosure\n- Different response lengths indicating logic flaws\n- Timing differences suggesting blind injection\n- Unexpected data in responses\n\n### Phase 5: Running Automated Scans\n\n#### Launch New Scan\nInitiate vulnerability scanning (Professional only):\n\n1. Go to **Dashboard** tab\n2. Click **New scan**\n3. Enter target URL in **URLs to scan** field\n4. Configure scan settings\n\n#### Scan Configuration Options\n\n| Mode | Description | Duration |\n|------|-------------|----------|\n| Lightweight | High-level overview | ~15 minutes |\n| Fast | Quick vulnerability check | ~30 minutes |\n| Balanced | Standard comprehensive scan | ~1-2 hours |\n| Deep | Thorough testing | Several hours |\n\n#### Monitor Scan Progress\nTrack scanning activity:\n\n1. View task status in **Dashboard**\n2. Watch **Target > Site map** update in real-time\n3. Check **Issues** tab for discovered vulnerabilities\n\n#### Review Identified Issues\nAnalyze scan findings:\n\n1. Select scan task in Dashboard\n2. Go to **Issues** tab\n3. Click issue to view:\n   - **Advisory**: Description and remediation\n   - **Request**: Triggering HTTP request\n   - **Response**: Server response showing vulnerability\n\n### Phase 6: Intruder Attacks\n\n#### Configure Intruder\nSet up automated attack:\n\n1. Send request to Intruder (right-click > Send to Intruder)\n2. Go to **Intruder** tab\n3. Define payload positions using § markers\n4. Select attack type\n\n#### Attack Types\n\n| Type | Description | Use Case |\n|------|-------------|----------|\n| Sniper | Single position, iterate payloads | Fuzzing one parameter |\n| Battering ram | Same payload all positions | Credential testing |\n| Pitchfork | Parallel payload iteration | Username:password pairs |\n| Cluster bomb | All payload combinations | Full brute force |\n\n#### Configure Payloads\n\n```\nPositions Tab:\nPOST \u002Flogin HTTP\u002F1.1\n...\nusername=§admin§&password=§password§\n\nPayloads Tab:\nSet 1: admin, user, test, guest\nSet 2: password, 123456, admin, letmein\n```\n\n#### Analyze Results\nReview attack output:\n\n- Sort by response length to find anomalies\n- Filter by status code for successful attempts\n- Use grep to search for specific strings\n- Export results for documentation\n\n## Quick Reference\n\n### Keyboard Shortcuts\n| Action | Windows\u002FLinux | macOS |\n|--------|---------------|-------|\n| Forward request | Ctrl+F | Cmd+F |\n| Drop request | Ctrl+D | Cmd+D |\n| Send to Repeater | Ctrl+R | Cmd+R |\n| Send to Intruder | Ctrl+I | Cmd+I |\n| Toggle intercept | Ctrl+T | Cmd+T |\n\n### Common Testing Payloads\n\n```\n# SQL Injection\n' OR '1'='1\n' OR '1'='1'--\n1 UNION SELECT NULL--\n\n# XSS\n\u003Cscript>alert(1)\u003C\u002Fscript>\n\">\u003Cimg src=x onerror=alert(1)>\njavascript:alert(1)\n\n# Path Traversal\n..\u002F..\u002F..\u002Fetc\u002Fpasswd\n..\\..\\..\\..\\windows\\win.ini\n\n# Command Injection\n; ls -la\n| cat \u002Fetc\u002Fpasswd\n`whoami`\n```\n\n### Request Modification Tips\n- Right-click for context menu options\n- Use decoder for encoding\u002Fdecoding\n- Compare requests using Comparer tool\n- Save interesting requests to project\n\n## Constraints and Guardrails\n\n### Operational Boundaries\n- Test only authorized applications\n- Configure scope to prevent accidental out-of-scope testing\n- Rate-limit scans to avoid denial of service\n- Document all findings and actions\n\n### Technical Limitations\n- Community Edition lacks automated scanner\n- Some sites may block proxy traffic\n- HSTS\u002Fcertificate pinning may require additional configuration\n- Heavy scanning may trigger WAF blocks\n\n### Best Practices\n- Always set target scope before extensive testing\n- Use Burp's browser for reliable interception\n- Save project regularly to preserve work\n- Review scan results manually for false positives\n\n## Examples\n\n### Example 1: Business Logic Testing\n\n**Scenario**: E-commerce price manipulation\n\n1. Add item to cart normally, intercept request\n2. Identify `price=9999` parameter in POST body\n3. Modify to `price=1`\n4. Forward request\n5. Complete checkout at manipulated price\n\n**Finding**: Server trusts client-provided price values.\n\n### Example 2: Authentication Bypass\n\n**Scenario**: Testing login form\n\n1. Submit valid credentials, capture request in Repeater\n2. Send to Repeater for testing\n3. Try: `username=admin' OR '1'='1'--`\n4. Observe successful login response\n\n**Finding**: SQL injection in authentication.\n\n### Example 3: Information Disclosure\n\n**Scenario**: Error-based information gathering\n\n1. Navigate to product page, observe `productId` parameter\n2. Send request to Repeater\n3. Change `productId=1` to `productId=test`\n4. Observe verbose error revealing framework version\n\n**Finding**: Apache Struts 2.5.12 disclosed in stack trace.\n\n## Troubleshooting\n\n### Browser Not Connecting Through Proxy\n- Verify proxy listener is active (Proxy > Options)\n- Check browser proxy settings point to 127.0.0.1:8080\n- Ensure no firewall blocking local connections\n- Use Burp's embedded browser for reliable setup\n\n### HTTPS Interception Failing\n- Install Burp CA certificate in browser\u002Fsystem\n- Navigate to http:\u002F\u002Fburp to download certificate\n- Add certificate to trusted roots\n- Restart browser after installation\n\n### Slow Performance\n- Limit scope to reduce processing\n- Disable unnecessary extensions\n- Increase Java heap size in startup options\n- Close unused Burp tabs and features\n\n### Requests Not Being Intercepted\n- Verify \"Intercept on\" is enabled\n- Check intercept rules aren't filtering target\n- Ensure browser is using Burp proxy\n- Verify target isn't using unsupported protocol\n","# Burp Suite Web Application Testing\n\n## Purpose\n\nExecute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows. This skill enables systematic discovery and exploitation of web application vulnerabilities through proxy-based testing methodology.\n\n## Inputs \u002F Prerequisites\n\n### Required Tools\n- Burp Suite Community or Professional Edition installed\n- Burp's embedded browser or configured external browser\n- Target web application URL\n- Valid credentials for authenticated testing (if applicable)\n\n### Environment Setup\n- Burp Suite launched with temporary or named project\n- Proxy listener active on 127.0.0.1:8080 (default)\n- Browser configured to use Burp proxy (or use Burp's browser)\n- CA certificate installed for HTTPS interception\n\n### Editions Comparison\n| Feature | Community | Professional |\n|---------|-----------|--------------|\n| Proxy | ✓ | ✓ |\n| Repeater | ✓ | ✓ |\n| Intruder | Limited | Full |\n| Scanner | ✗ | ✓ |\n| Extensions | ✓ | ✓ |\n\n## Outputs \u002F Deliverables\n\n### Primary Outputs\n- Intercepted and modified HTTP requests\u002Fresponses\n- Vulnerability scan reports with remediation advice\n- HTTP history and site map documentation\n- Proof-of-concept exploits for identified vulnerabilities\n\n## Core Workflow\n\n### Phase 1: Intercepting HTTP Traffic\n\n#### Launch Burp's Browser\nNavigate to integrated browser for seamless proxy integration:\n\n1. Open Burp Suite and create\u002Fopen project\n2. Go to **Proxy > Intercept** tab\n3. Click **Open Browser** to launch preconfigured browser\n4. Position windows to view both Burp and browser simultaneously\n\n#### Configure Interception\nControl which requests are captured:\n\n```\nProxy > Intercept > Intercept is on\u002Foff toggle\n\nWhen ON: Requests pause for review\u002Fmodification\nWhen OFF: Requests pass through, logged to history\n```\n\n#### Intercept and Forward Requests\nProcess intercepted traffic:\n\n1. Set intercept toggle to **Intercept on**\n2. Navigate to target URL in browser\n3. Observe request held in Proxy > Intercept tab\n4. Review request contents (headers, parameters, body)\n5. Click **Forward** to send request to server\n6. Continue forwarding subsequent requests until page loads\n\n#### View HTTP History\nAccess complete traffic log:\n\n1. Go to **Proxy > HTTP history** tab\n2. Click any entry to view full request\u002Fresponse\n3. Sort by clicking column headers (# for chronological order)\n4. Use filters to focus on relevant traffic\n\n### Phase 2: Modifying Requests\n\n#### Intercept and Modify\nChange request parameters before forwarding:\n\n1. Enable interception: **Intercept on**\n2. Trigger target request in browser\n3. Locate parameter to modify in intercepted request\n4. Edit value directly in request editor\n5. Click **Forward** to send modified request\n\n#### Common Modification Targets\n| Target | Example | Purpose |\n|--------|---------|---------|\n| Price parameters | `price=1` | Test business logic |\n| User IDs | `userId=admin` | Test access control |\n| Quantity values | `qty=-1` | Test input validation |\n| Hidden fields | `isAdmin=true` | Test privilege escalation |\n\n#### Example: Price Manipulation\n\n```http\nPOST \u002Fcart HTTP\u002F1.1\nHost: target.com\nContent-Type: application\u002Fx-www-form-urlencoded\n\nproductId=1&quantity=1&price=100\n\n# Modify to:\nproductId=1&quantity=1&price=1\n```\n\nResult: Item added to cart at modified price.\n\n### Phase 3: Setting Target Scope\n\n#### Define Scope\nFocus testing on specific target:\n\n1. Go to **Target > Site map**\n2. Right-click target host in left panel\n3. Select **Add to scope**\n4. When prompted, click **Yes** to exclude out-of-scope traffic\n\n#### Filter by Scope\nRemove noise from HTTP history:\n\n1. Click display filter above HTTP history\n2. Select **Show only in-scope items**\n3. History now shows only target site traffic\n\n#### Scope Benefits\n- Reduces clutter from third-party requests\n- Prevents accidental testing of out-of-scope sites\n- Improves scanning efficiency\n- Creates cleaner reports\n\n### Phase 4: Using Burp Repeater\n\n#### Send Request to Repeater\nPrepare request for manual testing:\n\n1. Identify interesting request in HTTP history\n2. Right-click request and select **Send to Repeater**\n3. Go to **Repeater** tab to access request\n\n#### Modify and Resend\nTest different inputs efficiently:\n\n```\n1. View request in Repeater tab\n2. Modify parameter values\n3. Click Send to submit request\n4. Review response in right panel\n5. Use navigation arrows to review request history\n```\n\n#### Repeater Testing Workflow\n\n```\nOriginal Request:\nGET \u002Fproduct?productId=1 HTTP\u002F1.1\n\nTest 1: productId=2    → Valid product response\nTest 2: productId=999  → Not Found response  \nTest 3: productId='    → Error\u002Fexception response\nTest 4: productId=1 OR 1=1 → SQL injection test\n```\n\n#### Analyze Responses\nLook for indicators of vulnerabilities:\n\n- Error messages revealing stack traces\n- Framework\u002Fversion information disclosure\n- Different response lengths indicating logic flaws\n- Timing differences suggesting blind injection\n- Unexpected data in responses\n\n### Phase 5: Running Automated Scans\n\n#### Launch New Scan\nInitiate vulnerability scanning (Professional only):\n\n1. Go to **Dashboard** tab\n2. Click **New scan**\n3. Enter target URL in **URLs to scan** field\n4. Configure scan settings\n\n#### Scan Configuration Options\n\n| Mode | Description | Duration |\n|------|-------------|----------|\n| Lightweight | High-level overview | ~15 minutes |\n| Fast | Quick vulnerability check | ~30 minutes |\n| Balanced | Standard comprehensive scan | ~1-2 hours |\n| Deep | Thorough testing | Several hours |\n\n#### Monitor Scan Progress\nTrack scanning activity:\n\n1. View task status in **Dashboard**\n2. Watch **Target > Site map** update in real-time\n3. Check **Issues** tab for discovered vulnerabilities\n\n#### Review Identified Issues\nAnalyze scan findings:\n\n1. Select scan task in Dashboard\n2. Go to **Issues** tab\n3. Click issue to view:\n   - **Advisory**: Description and remediation\n   - **Request**: Triggering HTTP request\n   - **Response**: Server response showing vulnerability\n\n### Phase 6: Intruder Attacks\n\n#### Configure Intruder\nSet up automated attack:\n\n1. Send request to Intruder (right-click > Send to Intruder)\n2. Go to **Intruder** tab\n3. Define payload positions using § markers\n4. Select attack type\n\n#### Attack Types\n\n| Type | Description | Use Case |\n|------|-------------|----------|\n| Sniper | Single position, iterate payloads | Fuzzing one parameter |\n| Battering ram | Same payload all positions | Credential testing |\n| Pitchfork | Parallel payload iteration | Username:password pairs |\n| Cluster bomb | All payload combinations | Full brute force |\n\n#### Configure Payloads\n\n```\nPositions Tab:\nPOST \u002Flogin HTTP\u002F1.1\n...\nusername=§admin§&password=§password§\n\nPayloads Tab:\nSet 1: admin, user, test, guest\nSet 2: password, 123456, admin, letmein\n```\n\n#### Analyze Results\nReview attack output:\n\n- Sort by response length to find anomalies\n- Filter by status code for successful attempts\n- Use grep to search for specific strings\n- Export results for documentation\n\n## Quick Reference\n\n### Keyboard Shortcuts\n| Action | Windows\u002FLinux | macOS |\n|--------|---------------|-------|\n| Forward request | Ctrl+F | Cmd+F |\n| Drop request | Ctrl+D | Cmd+D |\n| Send to Repeater | Ctrl+R | Cmd+R |\n| Send to Intruder | Ctrl+I | Cmd+I |\n| Toggle intercept | Ctrl+T | Cmd+T |\n\n### Common Testing Payloads\n\n```\n# SQL Injection\n' OR '1'='1\n' OR '1'='1'--\n1 UNION SELECT NULL--\n\n# XSS\n\u003Cscript>alert(1)\u003C\u002Fscript>\n\">\u003Cimg src=x onerror=alert(1)>\njavascript:alert(1)\n\n# Path Traversal\n..\u002F..\u002F..\u002Fetc\u002Fpasswd\n..\\..\\..\\..\\windows\\win.ini\n\n# Command Injection\n; ls -la\n| cat \u002Fetc\u002Fpasswd\n`whoami`\n```\n\n### Request Modification Tips\n- Right-click for context menu options\n- Use decoder for encoding\u002Fdecoding\n- Compare requests using Comparer tool\n- Save interesting requests to project\n\n## Constraints and Guardrails\n\n### Operational Boundaries\n- Test only authorized applications\n- Configure scope to prevent accidental out-of-scope testing\n- Rate-limit scans to avoid denial of service\n- Document all findings and actions\n\n### Technical Limitations\n- Community Edition lacks automated scanner\n- Some sites may block proxy traffic\n- HSTS\u002Fcertificate pinning may require additional configuration\n- Heavy scanning may trigger WAF blocks\n\n### Best Practices\n- Always set target scope before extensive testing\n- Use Burp's browser for reliable interception\n- Save project regularly to preserve work\n- Review scan results manually for false positives\n\n## Examples\n\n### Example 1: Business Logic Testing\n\n**Scenario**: E-commerce price manipulation\n\n1. Add item to cart normally, intercept request\n2. Identify `price=9999` parameter in POST body\n3. Modify to `price=1`\n4. Forward request\n5. Complete checkout at manipulated price\n\n**Finding**: Server trusts client-provided price values.\n\n### Example 2: Authentication Bypass\n\n**Scenario**: Testing login form\n\n1. Submit valid credentials, capture request in Repeater\n2. Send to Repeater for testing\n3. Try: `username=admin' OR '1'='1'--`\n4. Observe successful login response\n\n**Finding**: SQL injection in authentication.\n\n### Example 3: Information Disclosure\n\n**Scenario**: Error-based information gathering\n\n1. Navigate to product page, observe `productId` parameter\n2. Send request to Repeater\n3. Change `productId=1` to `productId=test`\n4. Observe verbose error revealing framework version\n\n**Finding**: Apache Struts 2.5.12 disclosed in stack trace.\n\n## Troubleshooting\n\n### Browser Not Connecting Through Proxy\n- Verify proxy listener is active (Proxy > Options)\n- Check browser proxy settings point to 127.0.0.1:8080\n- Ensure no firewall blocking local connections\n- Use Burp's embedded browser for reliable setup\n\n### HTTPS Interception Failing\n- Install Burp CA certificate in browser\u002Fsystem\n- Navigate to http:\u002F\u002Fburp to download certificate\n- Add certificate to trusted roots\n- Restart browser after installation\n\n### Slow Performance\n- Limit scope to reduce processing\n- Disable unnecessary extensions\n- Increase Java heap size in startup options\n- Close unused Burp tabs and features\n\n### Requests Not Being Intercepted\n- Verify \"Intercept on\" is enabled\n- Check intercept rules aren't filtering target\n- Ensure browser is using Burp proxy\n- Verify target isn't using unsupported protocol\n",{"name":5,"metadata":58,"description":7},{"author":59,"version":60},"zebbern","1.1","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fburp-suite-testing",3931,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-14 06:14:46",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add davila7\u002Fclaude-code-templates --skill burp-suite-testing",{"tool":77,"command":78},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill burp-suite-testing",{"tool":80,"command":81},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill burp-suite-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fburp-suite-testing\u002FSKILL.md",true,[85],{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"sections","OTHER","其他",50,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fship\u002Fsections",[92,117,144,177,210,231],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":99,"publishedAt":53},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[98],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[100,101,102,103,104,34,105,106,40,32,107,108,109,110,111,112,113,114,115,116],"scoring","pool","wealthville pool scoring","liquidity","which","exit","now","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":124,"publishedAt":53},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[123],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[125,126,127,128,129,130,131,132,133,134,135,32,136,137,138,139,140,141,142,143],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":159,"publishedAt":53},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[150,153,154],{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":155,"categoryName":156,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[160,161,162,163,164,165,166,34,167,168,169,170,171,172,173,40,174,175,32,176],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":181,"licenseFileUrl":182,"sourceHtmlUrl":183,"categories":184,"keywords":188,"publishedAt":53},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[189,49,190,191,192,193,194,195,196,197,198,199,200,201,202,203,204,205,27,206,207,208,34,209],"artifacts builder","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","jsx","html","single-file","ui components",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":181,"licenseFileUrl":214,"sourceHtmlUrl":215,"categories":216,"keywords":219,"publishedAt":53},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[217,218],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":186,"categoryName":187,"taxonomyType":21,"taxonomyTypeDesc":22},[220,30,221,222,223,49,224,198,199,225,226,227,228,34,229,108,230],"webapp testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":181,"licenseFileUrl":235,"sourceHtmlUrl":236,"categories":237,"keywords":245,"publishedAt":53},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[238,241,242],{"categoryNo":239,"categoryName":240,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":243,"categoryName":244,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000036","内容创作者",[246,247,248,249,250,251,252,253,191,254,201,136,255,256,257,258,259,172,260,32,261,262,263,264,265,114,266],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]