[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A8QCY1ZV2QJSXWS9C63F5J":3,"skill-same:01M7A8QCY1ZV2QJSXWS9C63F5J":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},"01M7A8QCY1ZV2QJSXWS9C63F5J","implementing-vulnerability-remediation-sla",null,"Design a vulnerability remediation SLA program covering asset tiering, a severity-based SLA matrix, exception processes, escalation chains, ticketing-system integration, and remediation KPIs\u002Ftrending metrics. Use when defining mandatory patching timeframes by severity and asset criticality, building an SLA policy document, or setting up escalation and KPI tracking for vulnerability remediation.","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\u002Fimplementing-vulnerability-remediation-sla\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-vulnerability-remediation-sla\ndescription: Design a vulnerability remediation SLA program covering asset tiering,\n  a severity-based SLA matrix, exception processes, escalation chains, ticketing-system\n  integration, and remediation KPIs\u002Ftrending metrics. Use when defining mandatory\n  patching timeframes by severity and asset criticality, building an SLA policy document,\n  or setting up escalation and KPI tracking for vulnerability remediation.\ndomain: cybersecurity\nsubdomain: vulnerability-management\ntags:\n- vulnerability-management\n- cve\n- sla\n- remediation\n- patch-management\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# Implementing Vulnerability Remediation SLA\n\n## Overview\nVulnerability remediation SLAs define mandatory timeframes for patching or mitigating identified vulnerabilities based on severity, asset criticality, and exploit availability. Effective SLA programs drive accountability, ensure consistent remediation timelines, and provide measurable KPIs for vulnerability management maturity.\n\n\n## When to Use\n\n- When deploying or configuring implementing vulnerability remediation sla capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability scanning program producing regular findings\n- Asset inventory with criticality classifications\n- Ticketing system (Jira, ServiceNow, etc.) for remediation tracking\n- Executive sponsorship for SLA enforcement\n- Cross-functional agreement from IT operations, development, and security\n\n## Core Concepts\n\n### SLA Framework Components\n1. **Severity Classification**: CVSS base score + threat context (EPSS, KEV)\n2. **Asset Tiering**: Business criticality and exposure level\n3. **Remediation Timeframes**: Maximum days to remediate by category\n4. **Exception Process**: Documented approval for SLA extensions\n5. **Escalation Procedures**: Actions when SLAs are breached\n6. **Metrics and Reporting**: KPIs for compliance tracking\n\n### Recommended SLA Matrix\n| Severity | Tier 1 (Critical) | Tier 2 (Important) | Tier 3 (Standard) |\n|----------|-------------------|--------------------|--------------------|\n| Critical (CVSS 9.0-10.0) | 24-48 hours | 72 hours | 7 days |\n| High (CVSS 7.0-8.9) | 7 days | 14 days | 30 days |\n| Medium (CVSS 4.0-6.9) | 30 days | 45 days | 60 days |\n| Low (CVSS 0.1-3.9) | 90 days | 90 days | 90 days |\n| CISA KEV Listed | 24 hours | 48 hours | 7 days |\n\n### SLA Accelerators (Reduce SLA by 50%)\n- Exploit code publicly available\n- Active exploitation observed in the wild (CISA KEV)\n- Internet-facing asset affected\n- EPSS score > 0.5 (50% exploitation probability)\n- Previous breach via similar vulnerability type\n\n## Workflow\n\n### Step 1: Define Asset Tiers\n```\nTier 1 (Critical Assets):\n- Customer-facing production systems\n- Payment processing infrastructure\n- Domain controllers and identity systems\n- Core network infrastructure (firewalls, routers)\n- Databases containing PII\u002FPHI\u002FPCI data\n\nTier 2 (Important Assets):\n- Internal production applications\n- Email and collaboration systems\n- Development\u002Fstaging environments with production data\n- Backup and recovery infrastructure\n- VPN and remote access gateways\n\nTier 3 (Standard Assets):\n- End-user workstations\n- Development\u002Ftest environments\n- Print servers and peripheral management\n- Non-critical internal tools\n```\n\n### Step 2: Establish SLA Policy Document\nKey sections to include:\n- Purpose and scope\n- Roles and responsibilities (RACI matrix)\n- Severity definitions and calculation method\n- Remediation timeframes by severity and asset tier\n- Exception request process and approval authority\n- Escalation procedures for SLA breaches\n- Metrics, reporting cadence, and governance\n- Policy review and update schedule\n\n### Step 3: Integrate with Ticketing System\n```python\n# ServiceNow \u002F Jira integration for automatic ticket creation\n# See process.py for full implementation\n\n# Key fields for remediation tickets:\n# - Vulnerability ID (CVE\u002FPlugin ID)\n# - Affected host(s)\n# - Severity (CVSS + contextual factors)\n# - Asset tier\n# - SLA deadline (calculated from discovery date)\n# - Assignment group\n# - Remediation instructions\n# - Verification criteria\n```\n\n### Step 4: Configure Escalation Chain\n```\nSLA Status          Action                          Notify\n───────────────────────────────────────────────────────────\n75% elapsed         Warning email                   Asset owner\n100% elapsed        SLA breach notification          Manager + CISO\n100% + 7 days       Executive escalation             VP\u002FCTO\n100% + 30 days      Risk acceptance required          CISO approval\n100% + 90 days      Compensating controls mandatory   Board report\n```\n\n### Step 5: Establish Exception Process\nValid exception reasons:\n- System cannot be patched without major downtime (scheduled maintenance window)\n- No vendor patch available (apply compensating controls)\n- Patch breaks critical functionality (require test results as evidence)\n- End-of-life system pending decommission (document risk acceptance)\n\nException requirements:\n- Written justification with business impact\n- Compensating controls documented and implemented\n- Approved by asset owner AND security leadership\n- Maximum exception duration: 90 days (renewable with re-approval)\n- Tracked in vulnerability management platform\n\n## Key Performance Indicators (KPIs)\n\n### Primary Metrics\n| KPI | Definition | Target |\n|-----|-----------|--------|\n| SLA Compliance Rate | % of vulns remediated within SLA | >90% |\n| Mean Time to Remediate (MTTR) | Average days from discovery to fix | Critical: \u003C3d, High: \u003C10d |\n| Vulnerability Backlog | Open vulnerabilities past SLA | \u003C5% of total |\n| Exception Rate | % of findings with active exceptions | \u003C10% |\n| Recurrence Rate | % of vulns that reappear after remediation | \u003C5% |\n\n### Trending Metrics\n- Month-over-month SLA compliance trend\n- MTTR trend by severity\n- Vulnerability density per asset (vulns\u002Fhost)\n- Patch coverage rate (% of assets scanned and compliant)\n- Time to first response (acknowledgment of finding)\n\n## Best Practices\n1. Start with achievable SLAs and tighten over time as maturity improves\n2. Use automated ticketing to eliminate manual SLA tracking\n3. Provide remediation teams with clear fix instructions, not just CVE numbers\n4. Track SLA compliance at the team\u002Fdepartment level for accountability\n5. Report SLA metrics to executive leadership monthly\n6. Include compensating controls as valid interim remediation\n7. Align SLAs with regulatory requirements (PCI DSS, HIPAA, SOX)\n8. Review and adjust SLAs annually based on threat landscape changes\n\n## Common Pitfalls\n- Setting unrealistic SLAs that teams cannot meet (creates SLA fatigue)\n- No executive enforcement of SLA breaches\n- Treating all assets equally without tiering\n- Not accounting for vulnerability context (EPSS, KEV) in SLA calculation\n- Missing exception management process (leads to untracked risk)\n- Measuring only compliance rate without analyzing root causes of breaches\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-patch-management-workflow\n- implementing-vulnerability-metrics-and-reporting\n- implementing-exception-management-process\n","# Implementing Vulnerability Remediation SLA\n\n## Overview\nVulnerability remediation SLAs define mandatory timeframes for patching or mitigating identified vulnerabilities based on severity, asset criticality, and exploit availability. Effective SLA programs drive accountability, ensure consistent remediation timelines, and provide measurable KPIs for vulnerability management maturity.\n\n\n## When to Use\n\n- When deploying or configuring implementing vulnerability remediation sla capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n- Vulnerability scanning program producing regular findings\n- Asset inventory with criticality classifications\n- Ticketing system (Jira, ServiceNow, etc.) for remediation tracking\n- Executive sponsorship for SLA enforcement\n- Cross-functional agreement from IT operations, development, and security\n\n## Core Concepts\n\n### SLA Framework Components\n1. **Severity Classification**: CVSS base score + threat context (EPSS, KEV)\n2. **Asset Tiering**: Business criticality and exposure level\n3. **Remediation Timeframes**: Maximum days to remediate by category\n4. **Exception Process**: Documented approval for SLA extensions\n5. **Escalation Procedures**: Actions when SLAs are breached\n6. **Metrics and Reporting**: KPIs for compliance tracking\n\n### Recommended SLA Matrix\n| Severity | Tier 1 (Critical) | Tier 2 (Important) | Tier 3 (Standard) |\n|----------|-------------------|--------------------|--------------------|\n| Critical (CVSS 9.0-10.0) | 24-48 hours | 72 hours | 7 days |\n| High (CVSS 7.0-8.9) | 7 days | 14 days | 30 days |\n| Medium (CVSS 4.0-6.9) | 30 days | 45 days | 60 days |\n| Low (CVSS 0.1-3.9) | 90 days | 90 days | 90 days |\n| CISA KEV Listed | 24 hours | 48 hours | 7 days |\n\n### SLA Accelerators (Reduce SLA by 50%)\n- Exploit code publicly available\n- Active exploitation observed in the wild (CISA KEV)\n- Internet-facing asset affected\n- EPSS score > 0.5 (50% exploitation probability)\n- Previous breach via similar vulnerability type\n\n## Workflow\n\n### Step 1: Define Asset Tiers\n```\nTier 1 (Critical Assets):\n- Customer-facing production systems\n- Payment processing infrastructure\n- Domain controllers and identity systems\n- Core network infrastructure (firewalls, routers)\n- Databases containing PII\u002FPHI\u002FPCI data\n\nTier 2 (Important Assets):\n- Internal production applications\n- Email and collaboration systems\n- Development\u002Fstaging environments with production data\n- Backup and recovery infrastructure\n- VPN and remote access gateways\n\nTier 3 (Standard Assets):\n- End-user workstations\n- Development\u002Ftest environments\n- Print servers and peripheral management\n- Non-critical internal tools\n```\n\n### Step 2: Establish SLA Policy Document\nKey sections to include:\n- Purpose and scope\n- Roles and responsibilities (RACI matrix)\n- Severity definitions and calculation method\n- Remediation timeframes by severity and asset tier\n- Exception request process and approval authority\n- Escalation procedures for SLA breaches\n- Metrics, reporting cadence, and governance\n- Policy review and update schedule\n\n### Step 3: Integrate with Ticketing System\n```python\n# ServiceNow \u002F Jira integration for automatic ticket creation\n# See process.py for full implementation\n\n# Key fields for remediation tickets:\n# - Vulnerability ID (CVE\u002FPlugin ID)\n# - Affected host(s)\n# - Severity (CVSS + contextual factors)\n# - Asset tier\n# - SLA deadline (calculated from discovery date)\n# - Assignment group\n# - Remediation instructions\n# - Verification criteria\n```\n\n### Step 4: Configure Escalation Chain\n```\nSLA Status          Action                          Notify\n───────────────────────────────────────────────────────────\n75% elapsed         Warning email                   Asset owner\n100% elapsed        SLA breach notification          Manager + CISO\n100% + 7 days       Executive escalation             VP\u002FCTO\n100% + 30 days      Risk acceptance required          CISO approval\n100% + 90 days      Compensating controls mandatory   Board report\n```\n\n### Step 5: Establish Exception Process\nValid exception reasons:\n- System cannot be patched without major downtime (scheduled maintenance window)\n- No vendor patch available (apply compensating controls)\n- Patch breaks critical functionality (require test results as evidence)\n- End-of-life system pending decommission (document risk acceptance)\n\nException requirements:\n- Written justification with business impact\n- Compensating controls documented and implemented\n- Approved by asset owner AND security leadership\n- Maximum exception duration: 90 days (renewable with re-approval)\n- Tracked in vulnerability management platform\n\n## Key Performance Indicators (KPIs)\n\n### Primary Metrics\n| KPI | Definition | Target |\n|-----|-----------|--------|\n| SLA Compliance Rate | % of vulns remediated within SLA | >90% |\n| Mean Time to Remediate (MTTR) | Average days from discovery to fix | Critical: \u003C3d, High: \u003C10d |\n| Vulnerability Backlog | Open vulnerabilities past SLA | \u003C5% of total |\n| Exception Rate | % of findings with active exceptions | \u003C10% |\n| Recurrence Rate | % of vulns that reappear after remediation | \u003C5% |\n\n### Trending Metrics\n- Month-over-month SLA compliance trend\n- MTTR trend by severity\n- Vulnerability density per asset (vulns\u002Fhost)\n- Patch coverage rate (% of assets scanned and compliant)\n- Time to first response (acknowledgment of finding)\n\n## Best Practices\n1. Start with achievable SLAs and tighten over time as maturity improves\n2. Use automated ticketing to eliminate manual SLA tracking\n3. Provide remediation teams with clear fix instructions, not just CVE numbers\n4. Track SLA compliance at the team\u002Fdepartment level for accountability\n5. Report SLA metrics to executive leadership monthly\n6. Include compensating controls as valid interim remediation\n7. Align SLAs with regulatory requirements (PCI DSS, HIPAA, SOX)\n8. Review and adjust SLAs annually based on threat landscape changes\n\n## Common Pitfalls\n- Setting unrealistic SLAs that teams cannot meet (creates SLA fatigue)\n- No executive enforcement of SLA breaches\n- Treating all assets equally without tiering\n- Not accounting for vulnerability context (EPSS, KEV) in SLA calculation\n- Missing exception management process (leads to untracked risk)\n- Measuring only compliance rate without analyzing root causes of breaches\n\n## Related Skills\n- prioritizing-vulnerabilities-with-cvss-scoring\n- implementing-patch-management-workflow\n- implementing-vulnerability-metrics-and-reporting\n- implementing-exception-management-process\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","sla","remediation","patch-management","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\u002Fimplementing-vulnerability-remediation-sla","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 implementing-vulnerability-remediation-sla",{"tool":57,"command":58},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-vulnerability-remediation-sla",{"tool":60,"command":61},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-vulnerability-remediation-sla","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\u002FSKILL.md",true,[65,71,75,81,85,89,95],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"assets\u002Ftemplate.md","ASSET","资产文件",1187,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\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","参考文档",4825,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\u002Freferences\u002Fapi-reference.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fstandards.md",1158,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\u002Freferences\u002Fstandards.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fworkflows.md",1526,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\u002Freferences\u002Fworkflows.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fagent.py","SCRIPT","脚本",8796,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\u002Fscripts\u002Fagent.py",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fprocess.py",11013,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-vulnerability-remediation-sla\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",[],[]]