[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A73889D6XR7WS33HVB73R2":3,"skill-same:01M7A73889D6XR7WS33HVB73R2":73},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7A73889D6XR7WS33HVB73R2","expo-ui",null,"Framework (OSS). Build native UI with the @expo\u002Fui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo\u002Fui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom\u002Fbottom-sheet, or RN built-in Picker\u002FSwitch; use @expo\u002Fui instead. Fall back to RN built-ins only when @expo\u002Fui is missing the component. NOTE: @expo\u002Fui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList\u002FFlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI\u002FJetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"MIT","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Framework (OSS). Build native UI with the @expo\u002Fui package: real SwiftUI on iOS and Jetpack Compose on Android. Default to @expo\u002Fui for sheets (BottomSheet), pickers, sliders, toggles, menus, and grouped-form sections — do NOT reach for Reanimated, @gorhom\u002Fbottom-sheet, or RN built-in Picker\u002FSwitch; use @expo\u002Fui instead. Fall back to RN built-ins only when @expo\u002Fui is missing the component. NOTE: @expo\u002Fui List renders native grouped rows like an iOS Settings screen — it is NOT a virtualized list; use FlatList\u002FFlashList for large datasets. Covers universal components (Host, Column, Row, Button, Text, List, BottomSheet, FieldGroup, Switch, Slider, Picker, Menu), drop-in replacements for RN community libraries, and platform-specific SwiftUI\u002FJetpack Compose trees. Not for Expo Router navigation, Reanimated, or data fetching.\"\nlicense: \"MIT\"\n---\n# Expo UI (`@expo\u002Fui`)\n\n`@expo\u002Fui` renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. It also ships drop-in replacements for migrating off RN community UI libraries.\n\n> These instructions track the latest Expo SDK. The **universal** layer requires **SDK 56+** and works in Expo Go — no custom build needed. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.\n\n## Installation\n\n```bash\nnpx expo install @expo\u002Fui\n```\n\nEvery `@expo\u002Fui` tree — universal or platform-specific — must be wrapped in `Host`.\n\n## Use @expo\u002Fui by default — don't reach for RN alternatives first\n\n**Before using Reanimated, `@gorhom\u002Fbottom-sheet`, React Native's built-in `Switch`\u002F`Picker`, or any community UI library for the items below, use `@expo\u002Fui` instead.** Only fall back to RN built-ins when `@expo\u002Fui` is missing the component.\n\n| Need | Use |\n|------|-----|\n| Slide-up sheet \u002F bottom sheet | `BottomSheet` from `@expo\u002Fui` — **not** Reanimated or `@gorhom\u002Fbottom-sheet` |\n| Grouped native list rows (settings\u002Fform-style) | `List` + `ListItem` from `@expo\u002Fui` — **not** `FlatList` (see note below) |\n| Toggle | `Switch` from `@expo\u002Fui` |\n| Slider | `Slider` from `@expo\u002Fui` |\n| Date\u002Ftime picker | `@expo\u002Fui\u002Fcommunity\u002Fdatetimepicker` |\n| Menu | `Menu` from `@expo\u002Fui` |\n| Form section with label | `FieldGroup` from `@expo\u002Fui` |\n| Collapsible section | `Collapsible` from `@expo\u002Fui` |\n\n> **`List` is NOT a virtualized scrolling list.** It renders native grouped table rows — the visual look of an iOS Settings screen or a form section, with disclosure indicators and native row styling. Each `ListItem` is a native node on the JS thread; rows are not recycled. For any list with large or unknown-length data (feeds, search results, catalogs), use **`FlatList`** or **`FlashList`** instead. `List` is the right choice for short, fixed-length groups: a settings screen, a detail panel's rows, a fixed menu.\n\n**`BottomSheet` example** (use this for map pin details, action sheets, detail panels — not Reanimated):\n\n```tsx\nimport { Host, BottomSheet, Column, Text } from '@expo\u002Fui';\nimport { useState } from 'react';\n\nexport default function MapScreen() {\n  const [isOpen, setIsOpen] = useState(false);\n\n  return (\n    \u003CView style={{ flex: 1 }}>\n      \u003CMapView onMarkerPress={() => setIsOpen(true)} \u002F>\n      \u003CHost>\n        \u003CBottomSheet\n          isPresented={isOpen}\n          onDismiss={() => setIsOpen(false)}\n          snapPoints={['half', 'full']}\n        >\n          \u003CColumn>\n            \u003CText>Café name\u003C\u002FText>\n            \u003CText>Address\u003C\u002FText>\n          \u003C\u002FColumn>\n        \u003C\u002FBottomSheet>\n      \u003C\u002FHost>\n    \u003C\u002FView>\n  );\n}\n```\n\n`BottomSheet` uses `isPresented`\u002F`onDismiss` — **not** `isOpened`, `isOpen`, `onIsOpenedChange`, or `onChange` (those are `@gorhom\u002Fbottom-sheet` props and will silently do nothing). `snapPoints` accepts `'half'`, `'full'`, `{ fraction: 0.5 }`, or `{ height: 400 }` and is optional (auto-sizes to content when omitted).\n\n## Choosing an approach\n\nWork down this list and stop at the first layer that meets the need:\n\n1. **Universal components — start here.** Import from the `@expo\u002Fui` root. One component tree runs unmodified on iOS, Android, and web from a single source (Compose on Android, SwiftUI on iOS, `react-native-web`\u002F`react-dom` on web). No platform file splits. → `.\u002Freferences\u002Funiversal.md`\n\n2. **Platform-specific (SwiftUI \u002F Jetpack Compose).** Import from `@expo\u002Fui\u002Fswift-ui` or `@expo\u002Fui\u002Fjetpack-compose`. Use **only** when the universal layer is missing a component or modifier you need, or when you need platform-specific behavior or optimization. **Downside:** you write two trees and split them into `.ios.tsx` \u002F `.android.tsx` files (or branch on `Platform.OS`) — more code to maintain.\n\n   > **`@expo\u002Fui\u002Fswift-ui` is iOS-only. `@expo\u002Fui\u002Fjetpack-compose` is Android-only.** Importing either in a file that runs on the other platform will crash at runtime with \"Unable to get view config\" errors. Isolate platform-specific trees in `.ios.tsx` \u002F `.android.tsx` files placed in `components\u002F` (never inside `app\u002F` — Expo Router does not support platform extensions for route files), or guard with `Platform.OS` in a regular route file. `Host` must always be imported from `@expo\u002Fui` (the universal package root), not from the platform-specific sub-packages. → `.\u002Freferences\u002Fswift-ui.md` and `.\u002Freferences\u002Fjetpack-compose.md`\n\n**Already using an RN community UI library?** `@expo\u002Fui` also ships **drop-in replacements** — API-compatible swaps for popular libraries (`@gorhom\u002Fbottom-sheet`, `@react-native-community\u002Fdatetimepicker`, and more), imported from `@expo\u002Fui\u002Fcommunity\u002F\u003Cname>`. This is a migration side-path for replacing an existing dependency, not a step in the universal-vs-platform decision above. → `.\u002Freferences\u002Fdrop-in-replacements.md`\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  universal.md             Universal @expo\u002Fui components and when to use them (SDK 56+)\n  drop-in-replacements.md  API-compatible replacements for RN community UI libraries\n  swift-ui.md              Platform-specific iOS UI: @expo\u002Fui\u002Fswift-ui components, modifiers, RNHostView, useNativeState\n  jetpack-compose.md       Platform-specific Android UI: @expo\u002Fui\u002Fjetpack-compose components, modifiers, LazyColumn caveat, icons, useNativeState\n```\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-ui\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n","# Expo UI (`@expo\u002Fui`)\n\n`@expo\u002Fui` renders real native UI from React: SwiftUI on iOS, Jetpack Compose on Android. It also ships drop-in replacements for migrating off RN community UI libraries.\n\n> These instructions track the latest Expo SDK. The **universal** layer requires **SDK 56+** and works in Expo Go — no custom build needed. Drop-in replacements and the platform-specific layers also exist on SDK 55. For component details on a specific SDK, refer to the Expo UI docs for that version.\n\n## Installation\n\n```bash\nnpx expo install @expo\u002Fui\n```\n\nEvery `@expo\u002Fui` tree — universal or platform-specific — must be wrapped in `Host`.\n\n## Use @expo\u002Fui by default — don't reach for RN alternatives first\n\n**Before using Reanimated, `@gorhom\u002Fbottom-sheet`, React Native's built-in `Switch`\u002F`Picker`, or any community UI library for the items below, use `@expo\u002Fui` instead.** Only fall back to RN built-ins when `@expo\u002Fui` is missing the component.\n\n| Need | Use |\n|------|-----|\n| Slide-up sheet \u002F bottom sheet | `BottomSheet` from `@expo\u002Fui` — **not** Reanimated or `@gorhom\u002Fbottom-sheet` |\n| Grouped native list rows (settings\u002Fform-style) | `List` + `ListItem` from `@expo\u002Fui` — **not** `FlatList` (see note below) |\n| Toggle | `Switch` from `@expo\u002Fui` |\n| Slider | `Slider` from `@expo\u002Fui` |\n| Date\u002Ftime picker | `@expo\u002Fui\u002Fcommunity\u002Fdatetimepicker` |\n| Menu | `Menu` from `@expo\u002Fui` |\n| Form section with label | `FieldGroup` from `@expo\u002Fui` |\n| Collapsible section | `Collapsible` from `@expo\u002Fui` |\n\n> **`List` is NOT a virtualized scrolling list.** It renders native grouped table rows — the visual look of an iOS Settings screen or a form section, with disclosure indicators and native row styling. Each `ListItem` is a native node on the JS thread; rows are not recycled. For any list with large or unknown-length data (feeds, search results, catalogs), use **`FlatList`** or **`FlashList`** instead. `List` is the right choice for short, fixed-length groups: a settings screen, a detail panel's rows, a fixed menu.\n\n**`BottomSheet` example** (use this for map pin details, action sheets, detail panels — not Reanimated):\n\n```tsx\nimport { Host, BottomSheet, Column, Text } from '@expo\u002Fui';\nimport { useState } from 'react';\n\nexport default function MapScreen() {\n  const [isOpen, setIsOpen] = useState(false);\n\n  return (\n    \u003CView style={{ flex: 1 }}>\n      \u003CMapView onMarkerPress={() => setIsOpen(true)} \u002F>\n      \u003CHost>\n        \u003CBottomSheet\n          isPresented={isOpen}\n          onDismiss={() => setIsOpen(false)}\n          snapPoints={['half', 'full']}\n        >\n          \u003CColumn>\n            \u003CText>Café name\u003C\u002FText>\n            \u003CText>Address\u003C\u002FText>\n          \u003C\u002FColumn>\n        \u003C\u002FBottomSheet>\n      \u003C\u002FHost>\n    \u003C\u002FView>\n  );\n}\n```\n\n`BottomSheet` uses `isPresented`\u002F`onDismiss` — **not** `isOpened`, `isOpen`, `onIsOpenedChange`, or `onChange` (those are `@gorhom\u002Fbottom-sheet` props and will silently do nothing). `snapPoints` accepts `'half'`, `'full'`, `{ fraction: 0.5 }`, or `{ height: 400 }` and is optional (auto-sizes to content when omitted).\n\n## Choosing an approach\n\nWork down this list and stop at the first layer that meets the need:\n\n1. **Universal components — start here.** Import from the `@expo\u002Fui` root. One component tree runs unmodified on iOS, Android, and web from a single source (Compose on Android, SwiftUI on iOS, `react-native-web`\u002F`react-dom` on web). No platform file splits. → `.\u002Freferences\u002Funiversal.md`\n\n2. **Platform-specific (SwiftUI \u002F Jetpack Compose).** Import from `@expo\u002Fui\u002Fswift-ui` or `@expo\u002Fui\u002Fjetpack-compose`. Use **only** when the universal layer is missing a component or modifier you need, or when you need platform-specific behavior or optimization. **Downside:** you write two trees and split them into `.ios.tsx` \u002F `.android.tsx` files (or branch on `Platform.OS`) — more code to maintain.\n\n   > **`@expo\u002Fui\u002Fswift-ui` is iOS-only. `@expo\u002Fui\u002Fjetpack-compose` is Android-only.** Importing either in a file that runs on the other platform will crash at runtime with \"Unable to get view config\" errors. Isolate platform-specific trees in `.ios.tsx` \u002F `.android.tsx` files placed in `components\u002F` (never inside `app\u002F` — Expo Router does not support platform extensions for route files), or guard with `Platform.OS` in a regular route file. `Host` must always be imported from `@expo\u002Fui` (the universal package root), not from the platform-specific sub-packages. → `.\u002Freferences\u002Fswift-ui.md` and `.\u002Freferences\u002Fjetpack-compose.md`\n\n**Already using an RN community UI library?** `@expo\u002Fui` also ships **drop-in replacements** — API-compatible swaps for popular libraries (`@gorhom\u002Fbottom-sheet`, `@react-native-community\u002Fdatetimepicker`, and more), imported from `@expo\u002Fui\u002Fcommunity\u002F\u003Cname>`. This is a migration side-path for replacing an existing dependency, not a step in the universal-vs-platform decision above. → `.\u002Freferences\u002Fdrop-in-replacements.md`\n\n## References\n\nConsult these resources as needed:\n\n```\nreferences\u002F\n  universal.md             Universal @expo\u002Fui components and when to use them (SDK 56+)\n  drop-in-replacements.md  API-compatible replacements for RN community UI libraries\n  swift-ui.md              Platform-specific iOS UI: @expo\u002Fui\u002Fswift-ui components, modifiers, RNHostView, useNativeState\n  jetpack-compose.md       Platform-specific Android UI: @expo\u002Fui\u002Fjetpack-compose components, modifiers, LazyColumn caveat, icons, useNativeState\n```\n\n## Submitting Feedback\nIf you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:\n```bash\nnpx --yes submit-expo-feedback@latest --category skills --subject \"expo-ui\" \"\u003Cactionable feedback>\"\n```\nOnly submit when you have something specific and actionable to report. Include as much relevant context as possible.\nIf an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.\n",{"license":15,"description":7},"main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fexpo-ui","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":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add NeelakshSaxena\u002FVayu --skill expo-ui",{"tool":37,"command":38},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill expo-ui",{"tool":40,"command":41},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill expo-ui","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002FSKILL.md",true,[45,51,55,59,63,67],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",722,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fdrop-in-replacements.md",2085,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Fdrop-in-replacements.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fjetpack-compose.md",5517,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Fjetpack-compose.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fswift-ui.md",4397,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Fswift-ui.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Funiversal.md",4792,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Freferences\u002Funiversal.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Flist-components.js","SCRIPT","脚本",7343,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fexpo-ui\u002Fscripts\u002Flist-components.js",[74,82,89,96,103,110],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"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":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"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",[],[]]