[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78B3AXY5VDBEAJDMVRJGNXW":3,"skill-same:01M78B3AXY5VDBEAJDMVRJGNXW":49},{"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":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M78B3AXY5VDBEAJDMVRJGNXW","burp-suite-testing",null,"Execute 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.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fburp-suite-testing\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: burp-suite-testing\ndescription: \"Execute 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.\"\nrisk: offensive\nsource: community\nauthor: zebbern\ndate_added: \"2026-02-27\"\n---\n\n> AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments.\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","> AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments.\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\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","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fburp-suite-testing","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill burp-suite-testing",{"tool":41,"command":42},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill burp-suite-testing",{"tool":44,"command":45},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill burp-suite-testing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fburp-suite-testing\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"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":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\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":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\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":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\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":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\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":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]