[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AAPEYTPQDMNXSBKF0K6P1T":3,"skill-same:01M7AAPEYTPQDMNXSBKF0K6P1T":82},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7AAPEYTPQDMNXSBKF0K6P1T","prisma-database-setup",null,"Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on \"configure postgres\", \"connect to mysql\", \"setup mongodb\", \"sqlite setup\".","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\u002Fprisma-database-setup\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\ndescription: \"Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on \\\"configure postgres\\\", \\\"connect to mysql\\\", \\\"setup mongodb\\\", \\\"sqlite setup\\\".\"\nlicense: \"MIT\"\nmetadata: {\"author\":\"prisma\",\"version\":\"7.6.0\"}\n---\n# Prisma Database Setup\n\nComprehensive guides for configuring Prisma ORM with various database providers.\n\n## When to Apply\n\nReference this skill when:\n- Initializing a new Prisma project\n- Switching database providers\n- Configuring connection strings and environment variables\n- Troubleshooting database connection issues\n- Setting up database-specific features\n- Generating and instantiating Prisma Client\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Provider Guides | CRITICAL | provider names |\n| 2 | Prisma Postgres | HIGH | `prisma-postgres` |\n| 3 | Client Setup | CRITICAL | `prisma-client-setup` |\n\n## System Prerequisites\n\n- **Node.js 20.19.0+**\n- **TypeScript 5.4.0+**\n\n## Bun Runtime\n\nIf you're using Bun, run Prisma CLI commands with `bunx --bun prisma ...` so Prisma uses the Bun runtime instead of falling back to Node.js.\n\n## Supported Databases\n\n| Database | Provider String | Notes |\n|----------|-----------------|-------|\n| PostgreSQL | `postgresql` | Default, full feature support |\n| MySQL | `mysql` | Widespread support, some JSON diffs |\n| SQLite | `sqlite` | Local file-based, no enum\u002Fscalar lists |\n| MongoDB | `mongodb` | Mongo-specific workflow; do not apply SQL driver-adapter guidance |\n| SQL Server | `sqlserver` | Microsoft ecosystem |\n| CockroachDB | `cockroachdb` | Distributed SQL, Postgres-compatible |\n| Prisma Postgres | `postgresql` | Managed serverless database |\n\n## Configuration Files\n\nYour configuration shape depends on the provider and Prisma major version:\n\n1. **All providers** use **`prisma\u002Fschema.prisma`**.\n2. **Prisma 7 SQL setups** typically use **`prisma.config.ts`** for datasource URLs.\n3. **MongoDB projects should stay on Prisma 6.x**, keep `url = env(\"DATABASE_URL\")` in the schema, and continue using the classic MongoDB setup.\n\n## Driver Adapters\n\nThe standard SQL workflow uses a driver adapter. Choose the adapter and driver for your database and pass the adapter to `PrismaClient`.\n\n| Database | Adapter | JS Driver |\n|----------|---------|-----------|\n| PostgreSQL | `@prisma\u002Fadapter-pg` | `pg` |\n| CockroachDB | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (Node.js) | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (edge\u002Fserverless) | `@prisma\u002Fadapter-ppg` | `@prisma\u002Fppg` |\n| MySQL \u002F MariaDB | `@prisma\u002Fadapter-mariadb` | `mariadb` |\n| SQLite | `@prisma\u002Fadapter-better-sqlite3` | `better-sqlite3` |\n| SQLite (Turso\u002FLibSQL) | `@prisma\u002Fadapter-libsql` | `@libsql\u002Fclient` |\n| SQL Server | `@prisma\u002Fadapter-mssql` | `node-mssql` |\n\nMongoDB should not follow the Prisma 7 SQL adapter workflow. Use the latest Prisma 6.x release for MongoDB projects and do not install a SQL `@prisma\u002Fadapter-*` package for it.\n\nExample (PostgreSQL):\n\n```ts\nimport 'dotenv\u002Fconfig'\nimport { PrismaClient } from '..\u002Fgenerated\u002Fclient'\nimport { PrismaPg } from '@prisma\u002Fadapter-pg'\n\nconst adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\nconst prisma = new PrismaClient({ adapter })\n```\n\n## Prisma Client Setup (Required)\n\nPrisma Client must be installed and generated for any database.\n\n1. Install Prisma CLI and Prisma Client:\n   ```bash\n   npm install prisma --save-dev\n   npm install @prisma\u002Fclient\n   ```\n\n1. Add a generator block (`prisma-client` requires an explicit output path):\n   ```prisma\n   generator client {\n     provider = \"prisma-client\"\n     output   = \"..\u002Fgenerated\"\n   }\n   ```\n\n1. Generate Prisma Client:\n   ```bash\n   npx prisma generate\n   ```\n\n1. For SQL providers, instantiate Prisma Client with the database-specific driver adapter:\n   ```typescript\n   import { PrismaClient } from '..\u002Fgenerated\u002Fclient'\n   import { PrismaPg } from '@prisma\u002Fadapter-pg'\n\n   const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\n   const prisma = new PrismaClient({ adapter })\n   ```\n\n1. Re-run `prisma generate` after every schema change.\n\n## Quick Reference\n\n### PostgreSQL\n```prisma\ndatasource db {\n  provider = \"postgresql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MySQL\n```prisma\ndatasource db {\n  provider = \"mysql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### SQLite\n```prisma\ndatasource db {\n  provider = \"sqlite\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MongoDB\n```prisma\ndatasource db {\n  provider = \"mongodb\"\n  url      = env(\"DATABASE_URL\")\n}\n\ngenerator client {\n  provider = \"prisma-client-js\"\n}\n```\n\nFor MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup. If a MongoDB project asks about upgrading Prisma versions, route to the `prisma-mongodb-upgrade` skill (stay-on-v6 vs Prisma Next is the real decision; Prisma 7 is not an option).\n\n## Rule Files\n\nSee individual rule files for detailed setup instructions:\n\n```\nreferences\u002Fpostgresql.md\nreferences\u002Fmysql.md\nreferences\u002Fsqlite.md\nreferences\u002Fmongodb.md\nreferences\u002Fsqlserver.md\nreferences\u002Fcockroachdb.md\nreferences\u002Fprisma-postgres.md\nreferences\u002Fprisma-client-setup.md\n```\n\n## How to Use\n\nChoose the provider reference file for your database, then apply `references\u002Fprisma-client-setup.md` to complete client generation and adapter setup. For MongoDB, use `references\u002Fmongodb.md` instead of copying the SQL adapter examples or Prisma 7 config pattern.\n","# Prisma Database Setup\n\nComprehensive guides for configuring Prisma ORM with various database providers.\n\n## When to Apply\n\nReference this skill when:\n- Initializing a new Prisma project\n- Switching database providers\n- Configuring connection strings and environment variables\n- Troubleshooting database connection issues\n- Setting up database-specific features\n- Generating and instantiating Prisma Client\n\n## Rule Categories by Priority\n\n| Priority | Category | Impact | Prefix |\n|----------|----------|--------|--------|\n| 1 | Provider Guides | CRITICAL | provider names |\n| 2 | Prisma Postgres | HIGH | `prisma-postgres` |\n| 3 | Client Setup | CRITICAL | `prisma-client-setup` |\n\n## System Prerequisites\n\n- **Node.js 20.19.0+**\n- **TypeScript 5.4.0+**\n\n## Bun Runtime\n\nIf you're using Bun, run Prisma CLI commands with `bunx --bun prisma ...` so Prisma uses the Bun runtime instead of falling back to Node.js.\n\n## Supported Databases\n\n| Database | Provider String | Notes |\n|----------|-----------------|-------|\n| PostgreSQL | `postgresql` | Default, full feature support |\n| MySQL | `mysql` | Widespread support, some JSON diffs |\n| SQLite | `sqlite` | Local file-based, no enum\u002Fscalar lists |\n| MongoDB | `mongodb` | Mongo-specific workflow; do not apply SQL driver-adapter guidance |\n| SQL Server | `sqlserver` | Microsoft ecosystem |\n| CockroachDB | `cockroachdb` | Distributed SQL, Postgres-compatible |\n| Prisma Postgres | `postgresql` | Managed serverless database |\n\n## Configuration Files\n\nYour configuration shape depends on the provider and Prisma major version:\n\n1. **All providers** use **`prisma\u002Fschema.prisma`**.\n2. **Prisma 7 SQL setups** typically use **`prisma.config.ts`** for datasource URLs.\n3. **MongoDB projects should stay on Prisma 6.x**, keep `url = env(\"DATABASE_URL\")` in the schema, and continue using the classic MongoDB setup.\n\n## Driver Adapters\n\nThe standard SQL workflow uses a driver adapter. Choose the adapter and driver for your database and pass the adapter to `PrismaClient`.\n\n| Database | Adapter | JS Driver |\n|----------|---------|-----------|\n| PostgreSQL | `@prisma\u002Fadapter-pg` | `pg` |\n| CockroachDB | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (Node.js) | `@prisma\u002Fadapter-pg` | `pg` |\n| Prisma Postgres (edge\u002Fserverless) | `@prisma\u002Fadapter-ppg` | `@prisma\u002Fppg` |\n| MySQL \u002F MariaDB | `@prisma\u002Fadapter-mariadb` | `mariadb` |\n| SQLite | `@prisma\u002Fadapter-better-sqlite3` | `better-sqlite3` |\n| SQLite (Turso\u002FLibSQL) | `@prisma\u002Fadapter-libsql` | `@libsql\u002Fclient` |\n| SQL Server | `@prisma\u002Fadapter-mssql` | `node-mssql` |\n\nMongoDB should not follow the Prisma 7 SQL adapter workflow. Use the latest Prisma 6.x release for MongoDB projects and do not install a SQL `@prisma\u002Fadapter-*` package for it.\n\nExample (PostgreSQL):\n\n```ts\nimport 'dotenv\u002Fconfig'\nimport { PrismaClient } from '..\u002Fgenerated\u002Fclient'\nimport { PrismaPg } from '@prisma\u002Fadapter-pg'\n\nconst adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\nconst prisma = new PrismaClient({ adapter })\n```\n\n## Prisma Client Setup (Required)\n\nPrisma Client must be installed and generated for any database.\n\n1. Install Prisma CLI and Prisma Client:\n   ```bash\n   npm install prisma --save-dev\n   npm install @prisma\u002Fclient\n   ```\n\n1. Add a generator block (`prisma-client` requires an explicit output path):\n   ```prisma\n   generator client {\n     provider = \"prisma-client\"\n     output   = \"..\u002Fgenerated\"\n   }\n   ```\n\n1. Generate Prisma Client:\n   ```bash\n   npx prisma generate\n   ```\n\n1. For SQL providers, instantiate Prisma Client with the database-specific driver adapter:\n   ```typescript\n   import { PrismaClient } from '..\u002Fgenerated\u002Fclient'\n   import { PrismaPg } from '@prisma\u002Fadapter-pg'\n\n   const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL })\n   const prisma = new PrismaClient({ adapter })\n   ```\n\n1. Re-run `prisma generate` after every schema change.\n\n## Quick Reference\n\n### PostgreSQL\n```prisma\ndatasource db {\n  provider = \"postgresql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MySQL\n```prisma\ndatasource db {\n  provider = \"mysql\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### SQLite\n```prisma\ndatasource db {\n  provider = \"sqlite\"\n}\n\ngenerator client {\n  provider = \"prisma-client\"\n  output   = \"..\u002Fgenerated\"\n}\n```\n\n### MongoDB\n```prisma\ndatasource db {\n  provider = \"mongodb\"\n  url      = env(\"DATABASE_URL\")\n}\n\ngenerator client {\n  provider = \"prisma-client-js\"\n}\n```\n\nFor MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup. If a MongoDB project asks about upgrading Prisma versions, route to the `prisma-mongodb-upgrade` skill (stay-on-v6 vs Prisma Next is the real decision; Prisma 7 is not an option).\n\n## Rule Files\n\nSee individual rule files for detailed setup instructions:\n\n```\nreferences\u002Fpostgresql.md\nreferences\u002Fmysql.md\nreferences\u002Fsqlite.md\nreferences\u002Fmongodb.md\nreferences\u002Fsqlserver.md\nreferences\u002Fcockroachdb.md\nreferences\u002Fprisma-postgres.md\nreferences\u002Fprisma-client-setup.md\n```\n\n## How to Use\n\nChoose the provider reference file for your database, then apply `references\u002Fprisma-client-setup.md` to complete client generation and adapter setup. For MongoDB, use `references\u002Fmongodb.md` instead of copying the SQL adapter examples or Prisma 7 config pattern.\n",{"license":15,"metadata":24,"description":7},{"author":25,"version":26},"prisma","7.6.0","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fprisma-database-setup","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add NeelakshSaxena\u002FVayu --skill prisma-database-setup",{"tool":40,"command":41},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill prisma-database-setup",{"tool":43,"command":44},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill prisma-database-setup","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002FSKILL.md",true,[48,54,58,62,66,70,74,78],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fcockroachdb.md","REFERENCE","参考文档",1837,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fcockroachdb.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fmongodb.md",2722,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fmongodb.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmysql.md",2669,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fmysql.md",{"path":63,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fpostgresql.md",1840,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fpostgresql.md",{"path":67,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fprisma-client-setup.md",1325,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fprisma-client-setup.md",{"path":71,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fprisma-postgres.md",3201,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fprisma-postgres.md",{"path":75,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsqlite.md",2210,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fsqlite.md",{"path":79,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fsqlserver.md",2114,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fprisma-database-setup\u002Freferences\u002Fsqlserver.md",[83,91,98,105,112,119],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[]]