[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A84H271KHMZP12QZNKKXJS":3,"skill-same:01M7A84H271KHMZP12QZNKKXJS":123},{"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":68,"commitSha":69,"skillDirectory":70,"forksCount":14,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":73,"updatedAt":74,"install":75,"resources":88},"01M7A84H271KHMZP12QZNKKXJS","implementing-google-workspace-sso-configuration",null,"Configures SAML 2.0 single sign-on for Google Workspace against a third-party identity provider (Okta, Azure AD\u002FEntra ID, ADFS), with Workspace as the Service Provider, to centralize authentication and enable immediate access revocation. Use when setting up or troubleshooting Google Workspace SSO\u002FSAML federation or migrating from native Google passwords to an external IdP.","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-google-workspace-sso-configuration\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: implementing-google-workspace-sso-configuration\ndescription: Configures SAML 2.0 single sign-on for Google Workspace against a third-party\n  identity provider (Okta, Azure AD\u002FEntra ID, ADFS), with Workspace as the Service\n  Provider, to centralize authentication and enable immediate access revocation.\n  Use when setting up or troubleshooting Google Workspace SSO\u002FSAML federation or\n  migrating from native Google passwords to an external IdP.\ndomain: cybersecurity\nsubdomain: identity-access-management\ntags:\n- google-workspace\n- sso\n- saml\n- identity-provider\n- authentication\n- federation\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\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - positioning\n  techniques:\n  - id: T1110\n    name: Brute Force\n    tactic: initial-access\n    source: attack\n  - id: T1110.004\n    name: 'Brute Force:  Credential Stuffing'\n    tactic: initial-access\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: F1006\n    name: Account Takeover\n    tactic: initial-access\n    source: f3\n---\n\n# Implementing Google Workspace SSO Configuration\n\n## Overview\n\nSingle Sign-On (SSO) for Google Workspace allows organizations to authenticate users through their existing identity provider (IdP) such as Okta, Azure AD (Microsoft Entra ID), or ADFS, rather than managing separate Google passwords. This is implemented using SAML 2.0 protocol where Google Workspace acts as the Service Provider (SP) and the organization's IdP handles authentication. SSO centralizes credential management, enforces MFA policies at the IdP, and enables immediate access revocation when users leave the organization.\n\n\n## When to Use\n\n- When deploying or configuring implementing google workspace sso configuration 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- Google Workspace Business, Enterprise, or Education edition\n- Super Admin access to Google Admin Console\n- Identity Provider with SAML 2.0 support (Okta, Azure AD, ADFS, Ping Identity)\n- IdP signing certificate (X.509 PEM format, RSA or DSA)\n- DNS verification for the Google Workspace domain\n\n## Core Concepts\n\n### SAML 2.0 SSO Flow\n\n```\nUser navigates to Google Workspace app (Gmail, Drive, etc.)\n        │\n        ├── Google checks: Is SSO configured for this domain?\n        │\n        ├── YES → Redirect user to IdP Sign-In Page URL\n        │          (SAML AuthnRequest sent via browser redirect)\n        │\n        ├── User authenticates at IdP (credentials + MFA)\n        │\n        ├── IdP generates SAML Response with signed assertion\n        │\n        ├── Browser POSTs SAML Response to Google ACS URL:\n        │   https:\u002F\u002Fwww.google.com\u002Fa\u002F{domain}\u002Facs\n        │\n        ├── Google validates SAML signature against uploaded certificate\n        │\n        └── User is granted access to Google Workspace\n```\n\n### Key SAML Parameters\n\n| Parameter | Value |\n|-----------|-------|\n| ACS URL | `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs` |\n| Entity ID | `google.com\u002Fa\u002F{your-domain}` or `google.com` |\n| NameID Format | `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` |\n| NameID Value | User's primary Google Workspace email |\n| Binding | HTTP-POST (for ACS), HTTP-Redirect (for SSO URL) |\n\n## Workflow\n\n### Step 1: Prepare the Identity Provider\n\n**For Okta:**\n1. Navigate to Applications > Add Application > Search \"Google Workspace\"\n2. Configure the Google Workspace app with your domain\n3. Assign users\u002Fgroups to the application\n4. Download the IdP metadata or note: SSO URL, Entity ID, Certificate\n\n**For Azure AD (Microsoft Entra ID):**\n1. Navigate to Enterprise Applications > New Application > Google Cloud\u002FWorkspace\n2. Configure Single sign-on > SAML\n3. Set Basic SAML Configuration:\n   - Identifier (Entity ID): `google.com`\n   - Reply URL (ACS): `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs`\n   - Sign on URL: `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002FServiceLogin`\n4. Download Federation Metadata XML or Certificate (Base64)\n\n**For ADFS:**\n1. Add Relying Party Trust using federation metadata\n2. Configure claim rules to pass NameID as email address\n3. Export the token-signing certificate\n\n### Step 2: Configure Google Workspace SSO\n\n1. Sign in to Google Admin Console (admin.google.com) as Super Admin\n2. Navigate to Security > Authentication > SSO with third-party IdP\n3. Click \"Add SSO profile\" or configure the default profile\n\n**Third-Party SSO Profile Settings:**\n\n| Setting | Value |\n|---------|-------|\n| Set up SSO with third-party IdP | Enabled |\n| Sign-in page URL | IdP's SAML SSO endpoint (e.g., `https:\u002F\u002Fidp.example.com\u002Fsso\u002Fsaml`) |\n| Sign-out page URL | IdP's logout URL (e.g., `https:\u002F\u002Fidp.example.com\u002Fslo`) |\n| Change password URL | IdP's password change URL |\n| Verification certificate | Upload IdP's X.509 signing certificate |\n| Use a domain-specific issuer | Enabled (uses `google.com\u002Fa\u002F{domain}` as entity ID) |\n\n### Step 3: Assign SSO Profile to Users\n\nSSO profiles can be applied at different scopes:\n\n```\nOrganization-wide (all users)\n    │\n    ├── Org Unit level (specific departments)\n    │   ├── Engineering OU → SSO via Okta\n    │   ├── Marketing OU → SSO via Azure AD\n    │   └── Contractors OU → SSO via specific IdP\n    │\n    └── Group level (specific security groups)\n        └── VPN Users → SSO with additional MFA\n```\n\n1. Navigate to Security > Authentication > SSO with third-party IdP\n2. Select the SSO profile to assign\n3. Choose organizational units or groups\n4. Save and wait for propagation (up to 24 hours, typically minutes)\n\n### Step 4: Configure Network Masks (Optional)\n\nNetwork masks control when SSO is enforced based on the user's IP:\n\n- If the user's IP matches a network mask, they use Google's sign-in page\n- If the user's IP does NOT match, they are redirected to the IdP\n\nThis is useful for allowing direct Google login from corporate network while enforcing SSO for external access.\n\n### Step 5: Test SSO\n\n1. Open an incognito browser window\n2. Navigate to `https:\u002F\u002Fmail.google.com\u002Fa\u002F{your-domain}`\n3. Verify redirect to IdP sign-in page\n4. Authenticate at the IdP\n5. Verify successful redirect back to Google Workspace\n6. Test sign-out flow redirects to IdP logout page\n7. Test with user not assigned in IdP (should fail)\n\n## Validation Checklist\n\n- [ ] IdP SAML application configured with correct ACS URL and Entity ID\n- [ ] IdP signing certificate uploaded to Google Admin Console\n- [ ] SSO profile assigned to target organizational units\u002Fgroups\n- [ ] SAML assertion includes correct NameID (email format)\n- [ ] MFA enforced at IdP for all Google Workspace users\n- [ ] Sign-out URL configured to terminate IdP session\n- [ ] Network masks configured if internal\u002Fexternal access differs\n- [ ] Break-glass Super Admin accounts bypass SSO (use Google auth)\n- [ ] SSO tested with multiple user types (admin, standard, contractor)\n- [ ] SAML response signature validated successfully\n- [ ] Error handling tested (expired cert, invalid user, clock skew)\n\n## References\n\n- [Google Workspace SSO Configuration Guide](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F12032922)\n- [Set Up Custom SAML App - Google](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F6087519)\n- [Okta Google Workspace SAML Guide](https:\u002F\u002Fsaml-doc.okta.com\u002FSAML_Docs\u002FHow-to-Enable-SAML-2.0-in-Google-Apps.html)\n- [SAML 2.0 Technical Overview - OASIS](https:\u002F\u002Fdocs.oasis-open.org\u002Fsecurity\u002Fsaml\u002FPost2.0\u002Fsstc-saml-tech-overview-2.0.html)\n","# Implementing Google Workspace SSO Configuration\n\n## Overview\n\nSingle Sign-On (SSO) for Google Workspace allows organizations to authenticate users through their existing identity provider (IdP) such as Okta, Azure AD (Microsoft Entra ID), or ADFS, rather than managing separate Google passwords. This is implemented using SAML 2.0 protocol where Google Workspace acts as the Service Provider (SP) and the organization's IdP handles authentication. SSO centralizes credential management, enforces MFA policies at the IdP, and enables immediate access revocation when users leave the organization.\n\n\n## When to Use\n\n- When deploying or configuring implementing google workspace sso configuration 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- Google Workspace Business, Enterprise, or Education edition\n- Super Admin access to Google Admin Console\n- Identity Provider with SAML 2.0 support (Okta, Azure AD, ADFS, Ping Identity)\n- IdP signing certificate (X.509 PEM format, RSA or DSA)\n- DNS verification for the Google Workspace domain\n\n## Core Concepts\n\n### SAML 2.0 SSO Flow\n\n```\nUser navigates to Google Workspace app (Gmail, Drive, etc.)\n        │\n        ├── Google checks: Is SSO configured for this domain?\n        │\n        ├── YES → Redirect user to IdP Sign-In Page URL\n        │          (SAML AuthnRequest sent via browser redirect)\n        │\n        ├── User authenticates at IdP (credentials + MFA)\n        │\n        ├── IdP generates SAML Response with signed assertion\n        │\n        ├── Browser POSTs SAML Response to Google ACS URL:\n        │   https:\u002F\u002Fwww.google.com\u002Fa\u002F{domain}\u002Facs\n        │\n        ├── Google validates SAML signature against uploaded certificate\n        │\n        └── User is granted access to Google Workspace\n```\n\n### Key SAML Parameters\n\n| Parameter | Value |\n|-----------|-------|\n| ACS URL | `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs` |\n| Entity ID | `google.com\u002Fa\u002F{your-domain}` or `google.com` |\n| NameID Format | `urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress` |\n| NameID Value | User's primary Google Workspace email |\n| Binding | HTTP-POST (for ACS), HTTP-Redirect (for SSO URL) |\n\n## Workflow\n\n### Step 1: Prepare the Identity Provider\n\n**For Okta:**\n1. Navigate to Applications > Add Application > Search \"Google Workspace\"\n2. Configure the Google Workspace app with your domain\n3. Assign users\u002Fgroups to the application\n4. Download the IdP metadata or note: SSO URL, Entity ID, Certificate\n\n**For Azure AD (Microsoft Entra ID):**\n1. Navigate to Enterprise Applications > New Application > Google Cloud\u002FWorkspace\n2. Configure Single sign-on > SAML\n3. Set Basic SAML Configuration:\n   - Identifier (Entity ID): `google.com`\n   - Reply URL (ACS): `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002Facs`\n   - Sign on URL: `https:\u002F\u002Fwww.google.com\u002Fa\u002F{your-domain}\u002FServiceLogin`\n4. Download Federation Metadata XML or Certificate (Base64)\n\n**For ADFS:**\n1. Add Relying Party Trust using federation metadata\n2. Configure claim rules to pass NameID as email address\n3. Export the token-signing certificate\n\n### Step 2: Configure Google Workspace SSO\n\n1. Sign in to Google Admin Console (admin.google.com) as Super Admin\n2. Navigate to Security > Authentication > SSO with third-party IdP\n3. Click \"Add SSO profile\" or configure the default profile\n\n**Third-Party SSO Profile Settings:**\n\n| Setting | Value |\n|---------|-------|\n| Set up SSO with third-party IdP | Enabled |\n| Sign-in page URL | IdP's SAML SSO endpoint (e.g., `https:\u002F\u002Fidp.example.com\u002Fsso\u002Fsaml`) |\n| Sign-out page URL | IdP's logout URL (e.g., `https:\u002F\u002Fidp.example.com\u002Fslo`) |\n| Change password URL | IdP's password change URL |\n| Verification certificate | Upload IdP's X.509 signing certificate |\n| Use a domain-specific issuer | Enabled (uses `google.com\u002Fa\u002F{domain}` as entity ID) |\n\n### Step 3: Assign SSO Profile to Users\n\nSSO profiles can be applied at different scopes:\n\n```\nOrganization-wide (all users)\n    │\n    ├── Org Unit level (specific departments)\n    │   ├── Engineering OU → SSO via Okta\n    │   ├── Marketing OU → SSO via Azure AD\n    │   └── Contractors OU → SSO via specific IdP\n    │\n    └── Group level (specific security groups)\n        └── VPN Users → SSO with additional MFA\n```\n\n1. Navigate to Security > Authentication > SSO with third-party IdP\n2. Select the SSO profile to assign\n3. Choose organizational units or groups\n4. Save and wait for propagation (up to 24 hours, typically minutes)\n\n### Step 4: Configure Network Masks (Optional)\n\nNetwork masks control when SSO is enforced based on the user's IP:\n\n- If the user's IP matches a network mask, they use Google's sign-in page\n- If the user's IP does NOT match, they are redirected to the IdP\n\nThis is useful for allowing direct Google login from corporate network while enforcing SSO for external access.\n\n### Step 5: Test SSO\n\n1. Open an incognito browser window\n2. Navigate to `https:\u002F\u002Fmail.google.com\u002Fa\u002F{your-domain}`\n3. Verify redirect to IdP sign-in page\n4. Authenticate at the IdP\n5. Verify successful redirect back to Google Workspace\n6. Test sign-out flow redirects to IdP logout page\n7. Test with user not assigned in IdP (should fail)\n\n## Validation Checklist\n\n- [ ] IdP SAML application configured with correct ACS URL and Entity ID\n- [ ] IdP signing certificate uploaded to Google Admin Console\n- [ ] SSO profile assigned to target organizational units\u002Fgroups\n- [ ] SAML assertion includes correct NameID (email format)\n- [ ] MFA enforced at IdP for all Google Workspace users\n- [ ] Sign-out URL configured to terminate IdP session\n- [ ] Network masks configured if internal\u002Fexternal access differs\n- [ ] Break-glass Super Admin accounts bypass SSO (use Google auth)\n- [ ] SSO tested with multiple user types (admin, standard, contractor)\n- [ ] SAML response signature validated successfully\n- [ ] Error handling tested (expired cert, invalid user, clock skew)\n\n## References\n\n- [Google Workspace SSO Configuration Guide](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F12032922)\n- [Set Up Custom SAML App - Google](https:\u002F\u002Fsupport.google.com\u002Fa\u002Fanswer\u002F6087519)\n- [Okta Google Workspace SAML Guide](https:\u002F\u002Fsaml-doc.okta.com\u002FSAML_Docs\u002FHow-to-Enable-SAML-2.0-in-Google-Apps.html)\n- [SAML 2.0 Technical Overview - OASIS](https:\u002F\u002Fdocs.oasis-open.org\u002Fsecurity\u002Fsaml\u002FPost2.0\u002Fsstc-saml-tech-overview-2.0.html)\n",{"name":5,"tags":25,"author":32,"domain":33,"license":15,"version":34,"mitre_f3":35,"nist_csf":58,"subdomain":63,"description":7,"mitre_attack":64},[26,27,28,29,30,31],"google-workspace","sso","saml","identity-provider","authentication","federation","mahipal","cybersecurity","1.0",{"tactics":36,"version":39,"techniques":40},[37,38],"initial-access","positioning","1.1",[41,45,48,51,55],{"id":42,"name":43,"source":44,"tactic":37},"T1110","Brute Force","attack",{"id":46,"name":47,"source":44,"tactic":37},"T1110.004","Brute Force:  Credential Stuffing",{"id":49,"name":50,"source":44,"tactic":38},"T1539","Steal Web Session Cookie",{"id":52,"name":53,"source":54,"tactic":37},"F1004","Access with Stolen Session Cookie","f3",{"id":56,"name":57,"source":54,"tactic":37},"F1006","Account Takeover",[59,60,61,62],"PR.AA-01","PR.AA-02","PR.AA-05","PR.AA-06","identity-access-management",[65,42,66,67],"T1078","T1556","T1098","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration","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":76,"prompt":86,"zipAvailable":87},[77,80,83],{"tool":78,"command":79},"npx","npx skills add NeelakshSaxena\u002FVayu --skill implementing-google-workspace-sso-configuration",{"tool":81,"command":82},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill implementing-google-workspace-sso-configuration",{"tool":84,"command":85},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill implementing-google-workspace-sso-configuration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002FSKILL.md",true,[89,95,99,105,109,113,119],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"assets\u002Ftemplate.md","ASSET","资产文件",1320,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Fassets\u002Ftemplate.md",{"path":96,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fapi-reference.md","REFERENCE","参考文档",1858,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Freferences\u002Fapi-reference.md",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fstandards.md",1421,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Freferences\u002Fstandards.md",{"path":110,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fworkflows.md",3935,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Freferences\u002Fworkflows.md",{"path":114,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":117,"sourceHtmlUrl":118},"scripts\u002Fagent.py","SCRIPT","脚本",7022,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Fscripts\u002Fagent.py",{"path":120,"resourceType":115,"resourceTypeDesc":116,"sizeBytes":121,"sourceHtmlUrl":122},"scripts\u002Fprocess.py",8282,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fimplementing-google-workspace-sso-configuration\u002Fscripts\u002Fprocess.py",[124,131,138,145,152,159],{"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},"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":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},"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":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},"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":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":151,"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":153,"name":154,"nameZh":6,"description":155,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":156,"categories":157,"keywords":158,"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":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"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",[],[]]