cloud-bootstrap

Bootstrap encrypted GCP, AWS, and Azure credentials for Claude Code repositories.

7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ipeirotis/cloud-bootstrap --skill cloud-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-bootstrap
Source: https://github.com/ipeirotis/cloud-bootstrap/tree/main
Command: npx skills add https://github.com/ipeirotis/cloud-bootstrap --skill cloud-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of preserving cloud authentication across Claude Code sessions by storing provider credentials in encrypted files inside the repository, so access survives restarts without exposing secrets in git history.

Core Features & Use Cases

  • Encrypted credential bootstrap: Creates and commits per-user encrypted credentials for GCP, AWS, or Azure.
  • Automatic session authentication: Uses SessionStart hooks to decrypt credentials and authenticate at the start of each session.
  • Multi-user and multi-provider support: Keeps separate encrypted files per teammate and can manage multiple cloud providers in the same repo.
  • Operational guardrails: Handles setup, onboarding, re-authentication, rotation, permission escalation, and uninstall flows with safety checks and cleanup steps.

Quick Start

Ask Claude to set up cloud credentials for your repository, and it will guide you through provider selection, token creation, encryption, and automatic authentication.

Frequently Asked Questions about cloud-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep cloud credentials alive across Claude Code sessions?

To keep cloud credentials alive across Claude Code sessions, this Skill stores provider tokens in encrypted per-user files inside the repository, using SessionStart hooks to automatically decrypt and authenticate upon each restart without exposing secrets in git history.

Does Claude Code support automatic authentication for AWS and GCP?

Yes, automatic authentication for AWS and GCP is supported by bootstrapping encrypted credential files and utilizing SessionStart hooks that inject provider-specific environment variables to authenticate at the start of each session.

How do I set up encrypted cloud credentials for a team repository?

To set up encrypted cloud credentials for a team repository, the Skill creates per-user encrypted files using OpenSSL AES-256-CBC, allowing multiple teammates to manage separate credentials for GCP, AWS, or Azure within the same environment.

Can I manage multi-provider access for AWS, Azure, and GCP in the same repo?

Yes, you can manage multi-provider access in the same repo because the Skill maintains separate encrypted credential files per teammate and provider, allowing simultaneous authentication for AWS, Azure, and GCP.

What is the best way to rotate cloud credentials stored in a repository?

The best way to rotate cloud credentials stored in a repository is using the built-in rotation and permission recovery workflows, which safely update encrypted credential files and provider-specific environment variables without exposing unencrypted secrets.

How do I safely uninstall cloud credentials from a Claude Code repository?

To safely uninstall cloud credentials from a Claude Code repository, the Skill executes dedicated uninstall workflows that remove encrypted credential files, clean up provider-specific environment variables, and disable SessionStart hooks.