[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A786RYSTC86KSW85QDDF6S":3,"skill-same:01M7A786RYSTC86KSW85QDDF6S":84},{"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":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M7A786RYSTC86KSW85QDDF6S","generating-threat-intelligence-reports",null,"Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.","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\u002Fgenerating-threat-intelligence-reports\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-threat-intelligence-reports\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: generating-threat-intelligence-reports\ndescription: 'Generates structured cyber threat intelligence reports at strategic,\n  operational, and tactical levels tailored to specific audiences including executives,\n  security operations teams, and technical analysts. Use when producing finished intelligence\n  products from raw collection data, creating sector threat briefings, or delivering\n  post-incident intelligence assessments. Activates for requests involving CTI report\n  writing, threat briefings, intelligence products, finished intelligence, or executive\n  security reporting.\n\n  '\ndomain: cybersecurity\nsubdomain: threat-intelligence\ntags:\n- CTI\n- threat-intelligence\n- intelligence-products\n- TLP\n- PIR\n- report-writing\n- NIST-CSF\nversion: 1.0.0\nauthor: team-cybersecurity\nlicense: Apache-2.0\nnist_csf:\n- ID.RA-01\n- ID.RA-05\n- DE.CM-01\n- DE.AE-02\nmitre_attack:\n- T1591\n- T1592\n- T1593\n- T1589\n---\n# Generating Threat Intelligence Reports\n\n## When to Use\n\nUse this skill when:\n- Producing weekly, monthly, or quarterly threat intelligence summaries for security leadership\n- Creating a rapid intelligence assessment in response to a breaking threat (e.g., new zero-day, active ransomware campaign)\n- Generating sector-specific threat briefings for executive decision-making on security investments\n\n**Do not use** this skill for raw IOC distribution — use TIP\u002FMISP for automated IOC sharing and reserve report generation for analyzed, finished intelligence.\n\n## Prerequisites\n\n- Completed analysis from collection and processing phase (PIRs partially or fully answered)\n- Audience profile: technical level, decision-making authority, information classification clearance\n- TLP classification decision for the product\n- Organization-specific reporting template aligned to audience expectations\n\n## Workflow\n\n### Step 1: Determine Report Type and Audience\n\nSelect the appropriate intelligence product type:\n\n**Strategic Intelligence Report**: For C-suite, board, risk committee\n- Content: Threat landscape trends, adversary intent vs. capability, risk to business objectives\n- Format: 1–3 pages, minimal jargon, business impact language, recommended decisions\n- Frequency: Monthly\u002FQuarterly\n\n**Operational Intelligence Report**: For CISO, security directors, IR leads\n- Content: Active campaigns, adversary TTPs, defensive recommendations, sector peer incidents\n- Format: 3–8 pages, moderate technical detail, mitigation priority list\n- Frequency: Weekly\n\n**Tactical Intelligence Bulletin**: For SOC analysts, threat hunters, vulnerability management\n- Content: Specific IOCs, YARA rules, Sigma detections, CVEs, patching guidance\n- Format: Structured tables, code blocks, 1–2 pages\n- Frequency: Daily or as-needed\n\n**Flash Report**: Urgent notification for imminent or active threats\n- Content: What is happening, immediate risk, what to do right now\n- Format: 1 page maximum, distributed within 2 hours of threat identification\n- Frequency: As-needed (zero-day, active campaign targeting sector)\n\n### Step 2: Structure Report Using Intelligence Standards\n\nApply intelligence writing standards from government and professional practice:\n\n**Headline\u002FKey Judgment**: Lead with the most important finding in plain language.\n- Bad: \"This report examines threat actor TTPs associated with Cl0p ransomware\"\n- Good: \"Cl0p ransomware group is actively exploiting CVE-2024-20353 in Cisco ASA devices to gain initial access; organizations using unpatched ASA appliances face imminent ransomware risk\"\n\n**Confidence Qualifiers** (use language from DNI ICD 203):\n- High confidence: \"assess with high confidence\" — strong evidence, few assumptions\n- Medium confidence: \"assess\" — credible sources but analytical assumptions required\n- Low confidence: \"suggests\" — limited sources, significant uncertainty\n\n**Evidence Attribution**: Cite sources using reference numbers [1], [2]; maintain source anonymization in TLP:AMBER\u002FRED products.\n\n### Step 3: Write Report Body\n\nUse structured format:\n\n**Executive Summary** (3–5 bullet points): Key findings, immediate business risk, top recommended action\n\n**Threat Overview**: Who is the adversary? What is their objective? Why does this matter to us?\n\n**Technical Analysis**: TTPs with ATT&CK technique IDs, IOCs, observed campaign behavior\n\n**Impact Assessment**: Potential operational, financial, reputational impact if attack succeeds\n\n**Recommended Actions**: Prioritized, time-bound defensive measures with owner assignment\n\n**Appendices**: Full IOC lists, YARA rules, Sigma detections, raw source references\n\n### Step 4: Apply TLP and Distribution Controls\n\nSelect TLP based on source sensitivity and sharing agreements:\n- **TLP:RED**: Named recipients only; cannot be shared outside briefing room\n- **TLP:AMBER+STRICT**: Organization only; no sharing with subsidiaries or partners\n- **TLP:AMBER**: Organization and trusted partners with need-to-know\n- **TLP:GREEN**: Community-wide sharing (ISAC members, sector peers)\n- **TLP:WHITE\u002FCLEAR**: Public distribution; no restrictions\n\nInclude TLP watermark on every page header and footer.\n\n### Step 5: Review and Quality Control\n\nBefore dissemination, apply these checks:\n- **Accuracy**: Are all facts sourced and cited? No unsubstantiated claims.\n- **Clarity**: Can the target audience understand this without additional context?\n- **Actionability**: Does every report section drive a decision or action?\n- **Classification**: Is TLP correctly applied? No source identification in AMBER\u002FRED products?\n- **Timeliness**: Is this intelligence still current? Events older than 48 hours require freshness assessment.\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Finished Intelligence** | Analyzed, contextualized intelligence product ready for consumption by decision-makers; distinct from raw collected data |\n| **Key Judgment** | Primary analytical conclusion of a report; clearly stated in opening paragraph |\n| **TLP** | Traffic Light Protocol — FIRST-standard classification system for controlling intelligence sharing scope |\n| **ICD 203** | Intelligence Community Directive 203 — US government standard for analytic standards including confidence language |\n| **Flash Report** | Urgent, time-sensitive intelligence notification for imminent threats; prioritizes speed over depth |\n| **Intelligence Gap** | Area where collection is insufficient to answer a PIR; should be explicitly documented in reports |\n\n## Tools & Systems\n\n- **ThreatConnect Reports**: Built-in report templates with ATT&CK mapping, IOC tables, and stakeholder distribution controls\n- **Recorded Future**: Pre-built intelligence report templates with automated sourcing from proprietary datasets\n- **OpenCTI Reports**: STIX-based report objects with linked entities for structured finished intelligence\n- **Microsoft Word\u002FConfluence**: Common report delivery formats; use organization-approved templates with TLP headers\n\n## Common Pitfalls\n\n- **Writing for analysts instead of the audience**: Technical detail appropriate for SOC analysts overwhelms executives. Maintain strict audience segmentation.\n- **Omitting confidence levels**: Statements presented without confidence qualifiers appear as established facts when they may be low-confidence assessments.\n- **Intelligence without recommendations**: Reports that describe threats without prescribing actions leave stakeholders without direction.\n- **Stale intelligence**: Publishing a report on a threat campaign that was resolved 2 weeks ago creates alarm without utility. Include freshness dating on all claims.\n- **Over-classification**: Applying TLP:RED to information that could be TLP:GREEN impedes community sharing and limits defensive value across the sector.\n","# Generating Threat Intelligence Reports\n\n## When to Use\n\nUse this skill when:\n- Producing weekly, monthly, or quarterly threat intelligence summaries for security leadership\n- Creating a rapid intelligence assessment in response to a breaking threat (e.g., new zero-day, active ransomware campaign)\n- Generating sector-specific threat briefings for executive decision-making on security investments\n\n**Do not use** this skill for raw IOC distribution — use TIP\u002FMISP for automated IOC sharing and reserve report generation for analyzed, finished intelligence.\n\n## Prerequisites\n\n- Completed analysis from collection and processing phase (PIRs partially or fully answered)\n- Audience profile: technical level, decision-making authority, information classification clearance\n- TLP classification decision for the product\n- Organization-specific reporting template aligned to audience expectations\n\n## Workflow\n\n### Step 1: Determine Report Type and Audience\n\nSelect the appropriate intelligence product type:\n\n**Strategic Intelligence Report**: For C-suite, board, risk committee\n- Content: Threat landscape trends, adversary intent vs. capability, risk to business objectives\n- Format: 1–3 pages, minimal jargon, business impact language, recommended decisions\n- Frequency: Monthly\u002FQuarterly\n\n**Operational Intelligence Report**: For CISO, security directors, IR leads\n- Content: Active campaigns, adversary TTPs, defensive recommendations, sector peer incidents\n- Format: 3–8 pages, moderate technical detail, mitigation priority list\n- Frequency: Weekly\n\n**Tactical Intelligence Bulletin**: For SOC analysts, threat hunters, vulnerability management\n- Content: Specific IOCs, YARA rules, Sigma detections, CVEs, patching guidance\n- Format: Structured tables, code blocks, 1–2 pages\n- Frequency: Daily or as-needed\n\n**Flash Report**: Urgent notification for imminent or active threats\n- Content: What is happening, immediate risk, what to do right now\n- Format: 1 page maximum, distributed within 2 hours of threat identification\n- Frequency: As-needed (zero-day, active campaign targeting sector)\n\n### Step 2: Structure Report Using Intelligence Standards\n\nApply intelligence writing standards from government and professional practice:\n\n**Headline\u002FKey Judgment**: Lead with the most important finding in plain language.\n- Bad: \"This report examines threat actor TTPs associated with Cl0p ransomware\"\n- Good: \"Cl0p ransomware group is actively exploiting CVE-2024-20353 in Cisco ASA devices to gain initial access; organizations using unpatched ASA appliances face imminent ransomware risk\"\n\n**Confidence Qualifiers** (use language from DNI ICD 203):\n- High confidence: \"assess with high confidence\" — strong evidence, few assumptions\n- Medium confidence: \"assess\" — credible sources but analytical assumptions required\n- Low confidence: \"suggests\" — limited sources, significant uncertainty\n\n**Evidence Attribution**: Cite sources using reference numbers [1], [2]; maintain source anonymization in TLP:AMBER\u002FRED products.\n\n### Step 3: Write Report Body\n\nUse structured format:\n\n**Executive Summary** (3–5 bullet points): Key findings, immediate business risk, top recommended action\n\n**Threat Overview**: Who is the adversary? What is their objective? Why does this matter to us?\n\n**Technical Analysis**: TTPs with ATT&CK technique IDs, IOCs, observed campaign behavior\n\n**Impact Assessment**: Potential operational, financial, reputational impact if attack succeeds\n\n**Recommended Actions**: Prioritized, time-bound defensive measures with owner assignment\n\n**Appendices**: Full IOC lists, YARA rules, Sigma detections, raw source references\n\n### Step 4: Apply TLP and Distribution Controls\n\nSelect TLP based on source sensitivity and sharing agreements:\n- **TLP:RED**: Named recipients only; cannot be shared outside briefing room\n- **TLP:AMBER+STRICT**: Organization only; no sharing with subsidiaries or partners\n- **TLP:AMBER**: Organization and trusted partners with need-to-know\n- **TLP:GREEN**: Community-wide sharing (ISAC members, sector peers)\n- **TLP:WHITE\u002FCLEAR**: Public distribution; no restrictions\n\nInclude TLP watermark on every page header and footer.\n\n### Step 5: Review and Quality Control\n\nBefore dissemination, apply these checks:\n- **Accuracy**: Are all facts sourced and cited? No unsubstantiated claims.\n- **Clarity**: Can the target audience understand this without additional context?\n- **Actionability**: Does every report section drive a decision or action?\n- **Classification**: Is TLP correctly applied? No source identification in AMBER\u002FRED products?\n- **Timeliness**: Is this intelligence still current? Events older than 48 hours require freshness assessment.\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Finished Intelligence** | Analyzed, contextualized intelligence product ready for consumption by decision-makers; distinct from raw collected data |\n| **Key Judgment** | Primary analytical conclusion of a report; clearly stated in opening paragraph |\n| **TLP** | Traffic Light Protocol — FIRST-standard classification system for controlling intelligence sharing scope |\n| **ICD 203** | Intelligence Community Directive 203 — US government standard for analytic standards including confidence language |\n| **Flash Report** | Urgent, time-sensitive intelligence notification for imminent threats; prioritizes speed over depth |\n| **Intelligence Gap** | Area where collection is insufficient to answer a PIR; should be explicitly documented in reports |\n\n## Tools & Systems\n\n- **ThreatConnect Reports**: Built-in report templates with ATT&CK mapping, IOC tables, and stakeholder distribution controls\n- **Recorded Future**: Pre-built intelligence report templates with automated sourcing from proprietary datasets\n- **OpenCTI Reports**: STIX-based report objects with linked entities for structured finished intelligence\n- **Microsoft Word\u002FConfluence**: Common report delivery formats; use organization-approved templates with TLP headers\n\n## Common Pitfalls\n\n- **Writing for analysts instead of the audience**: Technical detail appropriate for SOC analysts overwhelms executives. Maintain strict audience segmentation.\n- **Omitting confidence levels**: Statements presented without confidence qualifiers appear as established facts when they may be low-confidence assessments.\n- **Intelligence without recommendations**: Reports that describe threats without prescribing actions leave stakeholders without direction.\n- **Stale intelligence**: Publishing a report on a threat campaign that was resolved 2 weeks ago creates alarm without utility. Include freshness dating on all claims.\n- **Over-classification**: Applying TLP:RED to information that could be TLP:GREEN impedes community sharing and limits defensive value across the sector.\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":27,"description":41,"mitre_attack":42},[26,27,28,29,30,31,32],"CTI","threat-intelligence","intelligence-products","TLP","PIR","report-writing","NIST-CSF","team-cybersecurity","cybersecurity","1.0.0",[37,38,39,40],"ID.RA-01","ID.RA-05","DE.CM-01","DE.AE-02","Generates structured cyber threat intelligence reports at strategic, operational, and tactical levels tailored to specific audiences including executives, security operations teams, and technical analysts. Use when producing finished intelligence products from raw collection data, creating sector threat briefings, or delivering post-incident intelligence assessments. Activates for requests involving CTI report writing, threat briefings, intelligence products, finished intelligence, or executive security reporting.\n",[43,44,45,46],"T1591","T1592","T1593","T1589","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fgenerating-threat-intelligence-reports","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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add NeelakshSaxena\u002FVayu --skill generating-threat-intelligence-reports",{"tool":60,"command":61},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill generating-threat-intelligence-reports",{"tool":63,"command":64},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill generating-threat-intelligence-reports","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-threat-intelligence-reports\u002FSKILL.md",true,[68,72,78],{"path":69,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fapi-reference.md","REFERENCE","参考文档",2865,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-threat-intelligence-reports\u002Freferences\u002Fapi-reference.md",{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"scripts\u002Fagent.py","SCRIPT","脚本",8897,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgenerating-threat-intelligence-reports\u002Fscripts\u002Fagent.py",[85,92,99,106,113,120],{"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":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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"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",[],[]]