[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A8JB9CZKS8KANHTSTQFQ85":3,"skill-same:01M7A8JB9CZKS8KANHTSTQFQ85":127},{"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":72,"commitSha":73,"skillDirectory":74,"forksCount":14,"repositoryHtmlUrl":75,"repositoryHomepageUrl":6,"ownerHtmlUrl":76,"ownerBlogUrl":6,"ownerDescription":77,"updatedAt":78,"install":79,"resources":92},"01M7A8JB9CZKS8KANHTSTQFQ85","implementing-saml-sso-with-okta",null,"Implement SAML 2.0 Single Sign-On using Okta as the Identity Provider, covering SP-initiated and IdP-initiated flows, attribute mapping, certificate management, SHA-256 signature enforcement, and Single Logout. Use when configuring Okta SAML SSO for an application, hardening SAML certificate rotation and signing, or testing and troubleshooting SAML assertion flows with a tracer tool.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-saml-sso-with-okta\ndescription: Implement SAML 2.0 Single Sign-On using Okta as the Identity Provider,\n  covering SP-initiated and IdP-initiated flows, attribute mapping, certificate management,\n  SHA-256 signature enforcement, and Single Logout. Use when configuring Okta SAML SSO\n  for an application, hardening SAML certificate rotation and signing, or testing and\n  troubleshooting SAML assertion flows with a tracer tool.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- iam\n- identity\n- access-control\n- authentication\n- saml\n- sso\n- okta\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.AA-01\n- PR.AA-02\n- PR.AA-05\n- PR.AA-06\nmitre_attack:\n- T1078\n- T1110\n- T1556\n- T1098\n- T1553\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  - resource-development\n  techniques:\n  - id: T1586\n    name: Compromise Accounts\n    tactic: resource-development\n    source: attack\n  - id: T1539\n    name: Steal Web Session Cookie\n    tactic: positioning\n    source: attack\n  - id: F1004\n    name: Access with Stolen Session Cookie\n    tactic: initial-access\n    source: f3\n  - id: T1550.001\n    name: 'Use Alternate Authentication Material: Application Access Token'\n    tactic: initial-access\n    source: attack\n  - id: F1006.003\n    name: 'Account Takeover: Password Reset'\n    tactic: initial-access\n    source: f3\n---\n# Implementing SAML SSO with Okta\n\n## Overview\nImplement SAML 2.0 Single Sign-On (SSO) using Okta as the Identity Provider (IdP). This skill covers end-to-end configuration of SAML authentication flows, attribute mapping, certificate management, and security hardening for enterprise SSO deployments.\n\n\n## When to Use\n\n- When deploying or configuring implementing saml sso with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Configure Okta as a SAML 2.0 Identity Provider\n- Implement SP-initiated and IdP-initiated SSO flows\n- Map SAML attributes and configure assertion encryption\n- Enforce SHA-256 signatures and secure certificate rotation\n- Test SSO flows with SAML tracer tools\n- Implement Single Logout (SLO) handling\n\n## Key Concepts\n\n### SAML 2.0 Authentication Flow\n1. **SP-Initiated Flow**: User accesses Service Provider -> SP generates AuthnRequest -> Redirect to Okta IdP -> User authenticates -> Okta sends SAML Response -> SP validates assertion -> Access granted\n2. **IdP-Initiated Flow**: User authenticates at Okta -> Selects application -> Okta sends unsolicited SAML Response -> SP validates -> Access granted\n\n### Critical Security Requirements\n- **SHA-256 Signatures**: All SAML assertions must use SHA-256 (not SHA-1) for digital signatures\n- **Assertion Encryption**: Encrypt SAML assertions using AES-256 to protect attribute values in transit\n- **Audience Restriction**: Configure audience URI to prevent assertion replay across different SPs\n- **NotBefore\u002FNotOnOrAfter**: Enforce time validity windows to prevent stale assertion usage\n- **InResponseTo Validation**: Verify assertion corresponds to the original AuthnRequest\n\n### Okta Application Configuration\n- **Single Sign-On URL**: The ACS (Assertion Consumer Service) endpoint on the SP\n- **Audience URI (SP Entity ID)**: Unique identifier for the SP\n- **Name ID Format**: EmailAddress, Persistent, or Transient\n- **Attribute Statements**: Map Okta user profile attributes to SAML assertion attributes\n- **Group Attribute Statements**: Include group membership for RBAC\n\n## Workflow\n\n### Step 1: Create SAML Application in Okta\n1. Navigate to Applications > Create App Integration\n2. Select SAML 2.0 as the sign-on method\n3. Configure General Settings (App Name, Logo)\n4. Set Single Sign-On URL (ACS URL)\n5. Set Audience URI (SP Entity ID)\n6. Configure Name ID Format and Application Username\n\n### Step 2: Configure Attribute Mapping\n- Map `user.email` to `email` attribute\n- Map `user.firstName` and `user.lastName` to name attributes\n- Add group attribute statements for role-based access\n- Configure attribute value formats (Basic, URI Reference, Unspecified)\n\n### Step 3: Download and Install IdP Metadata\n- Download Okta IdP metadata XML\n- Extract IdP SSO URL, IdP Entity ID, and X.509 certificate\n- Install certificate on SP side for signature validation\n- Configure SP metadata with ACS URL and Entity ID\n\n### Step 4: Implement SP-Side SAML Processing\n- Parse and validate SAML Response XML\n- Verify digital signature using IdP certificate\n- Check audience restriction, time conditions, and InResponseTo\n- Extract authenticated user identity and attributes\n- Create application session based on assertion data\n\n### Step 5: Security Hardening\n- Enforce SHA-256 for all signature operations\n- Enable assertion encryption with AES-256-CBC\n- Configure session timeout and re-authentication policies\n- Implement SAML artifact binding for sensitive deployments\n- Set up certificate rotation procedure before expiry\n\n### Step 6: Testing and Validation\n- Use SAML Tracer browser extension for debugging\n- Validate SP-initiated and IdP-initiated flows\n- Test with multiple user accounts and group memberships\n- Verify SLO functionality\n- Test certificate rotation without downtime\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Authentication | IA-2 | Multi-factor authentication through Okta |\n| Session Management | SC-23 | SAML session lifetime controls |\n| Audit Logging | AU-3 | Log all SSO authentication events |\n| Certificate Management | SC-17 | PKI certificate lifecycle management |\n| Access Enforcement | AC-3 | SAML attribute-based access control |\n\n## Common Pitfalls\n- Using SHA-1 instead of SHA-256 for SAML signatures\n- Not validating InResponseTo in SAML responses (replay attacks)\n- Clock skew between IdP and SP causing assertion rejection\n- Failing to restrict audience URI allowing assertion forwarding\n- Not implementing certificate rotation before expiry causes outage\n\n## Verification\n- [ ] SAML SSO login completes successfully via SP-initiated flow\n- [ ] IdP-initiated flow correctly authenticates users\n- [ ] SAML assertions use SHA-256 signatures\n- [ ] Attribute mapping correctly populates user profile\n- [ ] Session timeout forces re-authentication\n- [ ] SLO properly terminates sessions on both IdP and SP\n- [ ] Certificate rotation tested without service interruption\n","# Implementing SAML SSO with Okta\n\n## Overview\nImplement SAML 2.0 Single Sign-On (SSO) using Okta as the Identity Provider (IdP). This skill covers end-to-end configuration of SAML authentication flows, attribute mapping, certificate management, and security hardening for enterprise SSO deployments.\n\n\n## When to Use\n\n- When deploying or configuring implementing saml sso with okta capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Familiarity with identity access management concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testing activities\n\n## Objectives\n- Configure Okta as a SAML 2.0 Identity Provider\n- Implement SP-initiated and IdP-initiated SSO flows\n- Map SAML attributes and configure assertion encryption\n- Enforce SHA-256 signatures and secure certificate rotation\n- Test SSO flows with SAML tracer tools\n- Implement Single Logout (SLO) handling\n\n## Key Concepts\n\n### SAML 2.0 Authentication Flow\n1. **SP-Initiated Flow**: User accesses Service Provider -> SP generates AuthnRequest -> Redirect to Okta IdP -> User authenticates -> Okta sends SAML Response -> SP validates assertion -> Access granted\n2. **IdP-Initiated Flow**: User authenticates at Okta -> Selects application -> Okta sends unsolicited SAML Response -> SP validates -> Access granted\n\n### Critical Security Requirements\n- **SHA-256 Signatures**: All SAML assertions must use SHA-256 (not SHA-1) for digital signatures\n- **Assertion Encryption**: Encrypt SAML assertions using AES-256 to protect attribute values in transit\n- **Audience Restriction**: Configure audience URI to prevent assertion replay across different SPs\n- **NotBefore\u002FNotOnOrAfter**: Enforce time validity windows to prevent stale assertion usage\n- **InResponseTo Validation**: Verify assertion corresponds to the original AuthnRequest\n\n### Okta Application Configuration\n- **Single Sign-On URL**: The ACS (Assertion Consumer Service) endpoint on the SP\n- **Audience URI (SP Entity ID)**: Unique identifier for the SP\n- **Name ID Format**: EmailAddress, Persistent, or Transient\n- **Attribute Statements**: Map Okta user profile attributes to SAML assertion attributes\n- **Group Attribute Statements**: Include group membership for RBAC\n\n## Workflow\n\n### Step 1: Create SAML Application in Okta\n1. Navigate to Applications > Create App Integration\n2. Select SAML 2.0 as the sign-on method\n3. Configure General Settings (App Name, Logo)\n4. Set Single Sign-On URL (ACS URL)\n5. Set Audience URI (SP Entity ID)\n6. Configure Name ID Format and Application Username\n\n### Step 2: Configure Attribute Mapping\n- Map `user.email` to `email` attribute\n- Map `user.firstName` and `user.lastName` to name attributes\n- Add group attribute statements for role-based access\n- Configure attribute value formats (Basic, URI Reference, Unspecified)\n\n### Step 3: Download and Install IdP Metadata\n- Download Okta IdP metadata XML\n- Extract IdP SSO URL, IdP Entity ID, and X.509 certificate\n- Install certificate on SP side for signature validation\n- Configure SP metadata with ACS URL and Entity ID\n\n### Step 4: Implement SP-Side SAML Processing\n- Parse and validate SAML Response XML\n- Verify digital signature using IdP certificate\n- Check audience restriction, time conditions, and InResponseTo\n- Extract authenticated user identity and attributes\n- Create application session based on assertion data\n\n### Step 5: Security Hardening\n- Enforce SHA-256 for all signature operations\n- Enable assertion encryption with AES-256-CBC\n- Configure session timeout and re-authentication policies\n- Implement SAML artifact binding for sensitive deployments\n- Set up certificate rotation procedure before expiry\n\n### Step 6: Testing and Validation\n- Use SAML Tracer browser extension for debugging\n- Validate SP-initiated and IdP-initiated flows\n- Test with multiple user accounts and group memberships\n- Verify SLO functionality\n- Test certificate rotation without downtime\n\n## Security Controls\n| Control | NIST 800-53 | Description |\n|---------|-------------|-------------|\n| Authentication | IA-2 | Multi-factor authentication through Okta |\n| Session Management | SC-23 | SAML session lifetime controls |\n| Audit Logging | AU-3 | Log all SSO authentication events |\n| Certificate Management | SC-17 | PKI certificate lifecycle management |\n| Access Enforcement | AC-3 | SAML attribute-based access control |\n\n## Common Pitfalls\n- Using SHA-1 instead of SHA-256 for SAML signatures\n- Not validating InResponseTo in SAML responses (replay attacks)\n- Clock skew between IdP and SP causing assertion rejection\n- Failing to restrict audience URI allowing assertion forwarding\n- Not implementing certificate rotation before expiry causes outage\n\n## Verification\n- [ ] SAML SSO login completes successfully via SP-initiated flow\n- [ ] IdP-initiated flow correctly authenticates users\n- [ ] SAML assertions use SHA-256 signatures\n- [ ] Attribute mapping correctly populates user profile\n- [ ] Session timeout forces re-authentication\n- [ ] SLO properly terminates sessions on both IdP and SP\n- [ ] Certificate rotation tested without service interruption\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"mitre_f3":36,"nist_csf":60,"subdomain":65,"description":7,"mitre_attack":66},[26,27,28,29,30,31,32],"iam","identity","access-control","authentication","saml","sso","okta","mahipal","cybersecurity","1.0",{"tactics":37,"version":41,"techniques":42},[38,39,40],"initial-access","positioning","resource-development","1.1",[43,47,50,54,57],{"id":44,"name":45,"source":46,"tactic":40},"T1586","Compromise Accounts","attack",{"id":48,"name":49,"source":46,"tactic":39},"T1539","Steal Web Session Cookie",{"id":51,"name":52,"source":53,"tactic":38},"F1004","Access with Stolen Session Cookie","f3",{"id":55,"name":56,"source":46,"tactic":38},"T1550.001","Use Alternate Authentication Material: Application Access Token",{"id":58,"name":59,"source":53,"tactic":38},"F1006.003","Account Takeover: Password Reset",[61,62,63,64],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[67,68,69,70,71],"T1078","T1110","T1556","T1098","T1553","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fimplementing-saml-sso-with-okta","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":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add NeelakshSaxena\u002FVayu --skill implementing-saml-sso-with-okta",{"tool":85,"command":86},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-saml-sso-with-okta",{"tool":88,"command":89},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-saml-sso-with-okta","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002FSKILL.md",true,[93,99,103,109,113,117,123],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Ftemplate.md","ASSET","资产文件",4229,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002Fassets\u002Ftemplate.md",{"path":100,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fapi-reference.md","REFERENCE","参考文档",1663,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002Freferences\u002Fapi-reference.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fstandards.md",2170,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002Freferences\u002Fstandards.md",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fworkflows.md",3516,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002Freferences\u002Fworkflows.md",{"path":118,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fagent.py","SCRIPT","脚本",7789,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002Fscripts\u002Fagent.py",{"path":124,"resourceType":119,"resourceTypeDesc":120,"sizeBytes":125,"sourceHtmlUrl":126},"scripts\u002Fprocess.py",19707,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-saml-sso-with-okta\u002Fscripts\u002Fprocess.py",[128,135,142,149,156,163],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":20},"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":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":148,"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":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":155,"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":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"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":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"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",[],[]]