Agent skill

Beanstalk Deploy

by pr-pm in pr-pm/prpm

Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling

MITAuto-check passedDevOps & Cloud

Install Beanstalk Deploy

skills CLI
$ npx skills add pr-pm/prpm --skill beanstalk-deploy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install pr-pm/prpm beanstalk-deploy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/beanstalk-deploy .claude/skills/beanstalk-deploy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
beanstalk-deploy
GitHub stars
122
Token cost
~1.1k tokens
SKILL.md length
137 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling

  • Works in 6 steps: Always verify infrastructure health… → Never assume resources are ready -… → Handle terminated environments… → …
  • Tasks that involve Deployment
  • SKILL.md covers 🎯 Core Principles, 🏗️ Infrastructure Health Checks and ⏳ Beanstalk Readiness…
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Beanstalk Deploy is an agent skill from pr-pm/prpm. Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering Deployment, Infrastructure as code and CI/CD. It works with Pulumi and GitHub Actions. The repository describes itself as: The universal registry for AI coding tools. The licence is MIT.

When your agent uses it

  • Tasks that involve Deployment
  • Tasks that involve Infrastructure as code
  • Tasks that involve CI/CD

Example prompts

  • “/beanstalk-deploy”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Always verify infrastructure health before deploying
  2. Never assume resources are ready - implement retry logic
  3. Handle terminated environments gracefully with state cleanup
  4. Use concurrency control to prevent deployment conflicts
  5. Pre-install dependencies for faster, more reliable deploys
  6. Implement comprehensive error handling with fallbacks

What it can do on your machine

Read from SKILL.md and the folder at commit 5f993e6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Beanstalk Deploy loads about 1.1k tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 137 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~29
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pr-pm/prpm at commit 5f993e6, republished under its MIT licence (© pr-pm). 137 words, ~1,051 tokens.

Download SKILL.mdSave it as .claude/skills/beanstalk-deploy/SKILL.md (or your agent's skills folder).
name
beanstalk-deploy
description
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling

AWS Elastic Beanstalk Deployment Best Practices

Apply these production-tested patterns when working with Elastic Beanstalk deployments, especially with GitHub Actions and Pulumi infrastructure.

🎯 Core Principles

  1. Always verify infrastructure health before deploying
  2. Never assume resources are ready - implement retry logic
  3. Handle terminated environments gracefully with state cleanup
  4. Use concurrency control to prevent deployment conflicts
  5. Pre-install dependencies for faster, more reliable deploys
  6. Implement comprehensive error handling with fallbacks

🏗️ Infrastructure Health Checks

ALWAYS check infrastructure status before deploying:

yaml
- name: Check infrastructure status
  run: |
    echo "🔍 Checking infrastructure status..."

    # Get environment name from Pulumi state (without deploying)
    EB_ENVIRONMENT_NAME=$(pulumi stack output ebEnvironmentName 2>/dev/null || echo "")

    if [ -z "$EB_ENVIRONMENT_NAME" ]; then
      echo "🔍 No environment found in Pulumi state. Will deploy infrastructure..."
    else
      echo "🔍 Checking environment status: $EB_ENVIRONMENT_NAME"

      # Check if environment exists and is healthy
      EB_ENV_STATUS=$(aws elasticbeanstalk describe-environments \
        --environment-names "$EB_ENVIRONMENT_NAME" \
        --query "Environments[0].Status" --output text 2>/dev/null || echo "NOT_FOUND")

      if [ "$EB_ENV_STATUS" = "Terminated" ] || [ "$EB_ENV_STATUS" = "NOT_FOUND" ]; then
        echo "⚠️  Environment is $EB_ENV_STATUS. Deleting from Pulumi state..."

        # Delete environment from Pulumi state
        EB_URN=$(pulumi stack --show-urns | awk '/aws:elasticbeanstalk\/environment:Environment/ {print $1; exit}')
        if [ -n "$EB_URN" ]; then
          echo "🔧 Deleting: $EB_URN"
          pulumi state delete "$EB_URN" --force
        fi

        echo "🔄 Infrastructure will be recreated..."
      else
        echo "✅ Environment exists: $EB_ENV_STATUS"

        # Check if infrastructure changes needed
        if pulumi preview --diff --expect-no-changes 2>/dev/null; then
          echo "✅ No infrastructure changes needed"
        else
          echo "🔄 Infrastructure changes detected"
        fi
      fi
    fi

Why: Prevents deploying to orphaned resources, automatically recovers from terminated environments, saves money on zombie resources.

⏳ Beanstalk Readiness Verification

ALWAYS wait for environment to be fully ready:

yaml
- name: Verify Elastic Beanstalk environment exists
  run: |
    echo "🔍 Verifying Elastic Beanstalk environment..."
    EB_ENVIRONMENT_NAME="${{ steps.get-resources.outputs.eb_environment_name }}"

    # Wait until environment exists
    echo "⏳ Waiting for environment to exist..."
    aws elasticbeanstalk wait environment-exists \
      --environment-names "$EB_ENVIRONMENT_NAME" || true

    # Wait until environment is Ready (with 30 retries)
    for i in {1..30}; do
      ENV_STATUS=$(aws elasticbeanstalk describe-environments \
        --environment-names "$EB_ENVIRONMENT_NAME" \
        --query "Environments[0].Status" --output text 2>/dev/null || echo "NOT_FOUND")
      ENV_HEALTH=$(aws elasticbeanstalk describe-environments \
        --environment-names "$EB_ENVIRONMENT_NAME" \
        --query "Environments[0].Health" --output text 2>/dev/null || echo "UNKNOWN")

      echo "⏳ EB Status: $ENV_STATUS, Health: $ENV_HEALTH (attempt $i/30)"

      if [ "$ENV_STATUS" = "Ready" ]; then
        echo "✅ Environment is Ready"
        break
      fi
      sleep 20  # Wait 20 seconds between checks (10 minutes total)
    done

    if [ "$ENV_STATUS" != "Ready" ]; then
      echo "⚠️  Environment not Ready after 10 minutes. Continuing with caution..."
    fi

Why: Prevents timing-related failures, ensures environment is provisioned before app deployment, provides visibility into provisioning progress.

See full documentation for complete deployment patterns, Pulumi configuration, monitoring, and production checklist.

© pr-pm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/beanstalk-deploy of pr-pm/prpm.

Open the folder on GitHubat commit 5f993e6

Compare with similar skills

Beanstalk Deploy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Beanstalk Deploy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Beanstalk Deploy this skillpr-pm/prpm122—~1.1kAutomated safety check: PassMIT
Devops EngineerYikai-Liao/symusic1891 repos~1.5kAutomated safety check: PassMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2596 repos~1.1kAutomated safety check: NotesCustom licence
Azure Bicep Skilltimothywarner-org/claude-code224—~2.9kAutomated safety check: PassMIT
APIOps Deployment for Azure APIMthomast1906/github-copilot-agent-skills202—~3.6kAutomated safety check: PassMIT
Devops InfrastructureCloudAI-X/claude-workflow-v21.4k—~2.7kAutomated safety check: NotesMIT

Similar skills

  • Devops Engineer

    Yikai-Liao/symusic

    Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.

    189 GitHub starsUsed in 1 repo~1.5k tokens
    DevOps & CloudAuto-check passed
  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    259 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes
  • Azure Bicep Skill

    timothywarner-org/claude-code

    A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.

    224 GitHub stars~2.9k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • APIOps Deployment for Azure APIM

    thomast1906/github-copilot-agent-skills

    Supplies Bicep and Terraform templates, CI/CD pipeline patterns and phased promotion plans for deploying Azure API Management with APIOps workflows.

    202 GitHub stars~3.6k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Devops Infrastructure

    CloudAI-X/claude-workflow-v2

    Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup.

    1.4k GitHub stars~2.7k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Ops Add New Chain

    boundless-xyz/boundless

    Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.

    193 GitHub stars~3.8k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed

More from pr-pm/prpm

All 35 skills in this repo
  • Reference for writing Claude Code agent files: location, frontmatter fields, validation limits, tool and model choices, and the required content format.

    122 GitHub starsUsed in 3 repos~4k tokens
    Auto-check passed
  • Covers how to build, configure and publish Claude Code hooks: event types, exit codes, JSON I/O, and PRPM packaging.

    122 GitHub starsUsed in 2 repos~3.9k tokens
    Auto-check: notes
  • Shows how to write .claude/rules/ files correctly: paths frontmatter instead of globs, quoted glob patterns, global rules and conversion of Cursor rules.

    122 GitHub starsUsed in 2 repos~551 tokens
    Auto-check passed
  • Reference for writing portable Agent Skills packages, covering SKILL.md frontmatter limits, name rules, directory layout and where Codex CLI, GitHub Copilot and Amp look for skills.

    122 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed
  • A skill your agent uses when building custom Kiro AI agents or when user asks for agent configurations - provides JSON structure, tool configuration, prompt patterns, and security best practices for…

    122 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • A skill your agent uses when creating OpenCode agents - provides markdown format with YAML frontmatter, mode/tools/permission configuration, and best practices for specialized AI assistants

    122 GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

Categories

Questions about Beanstalk Deploy

What does Beanstalk Deploy do?

Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling. Beanstalk Deploy is an agent skill from pr-pm/prpm.

When should I use Beanstalk Deploy?

Beanstalk Deploy fits situations like: tasks that involve Deployment; tasks that involve Infrastructure as code; tasks that involve CI/CD.

How do I install Beanstalk Deploy in Claude Code?

Run `npx skills add pr-pm/prpm --skill beanstalk-deploy -a claude-code`. Or copy the skill folder (.claude/skills/beanstalk-deploy in pr-pm/prpm) into .claude/skills/beanstalk-deploy in your project. Claude Code loads it when a task matches its description.

How do I install Beanstalk Deploy in Codex?

Run `npx skills add pr-pm/prpm --skill beanstalk-deploy -a codex`. Or copy the skill folder (.claude/skills/beanstalk-deploy in pr-pm/prpm) into .agents/skills/beanstalk-deploy in your project. Codex loads it when a task matches its description.

Can I use Beanstalk Deploy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pr-pm/prpm --skill beanstalk-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/beanstalk-deploy, .gemini/skills/beanstalk-deploy, .github/skills/beanstalk-deploy and .opencode/skills/beanstalk-deploy in your project.

What does Beanstalk Deploy need to run?

SKILL.md names no scripts, command-line tools or credentials: Beanstalk Deploy is instructions for the agent only.

Does Beanstalk Deploy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Beanstalk Deploy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Beanstalk Deploy use?

Beanstalk Deploy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Beanstalk Deploy use?

About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Beanstalk Deploy?

Skills that share tags, products or a category with Beanstalk Deploy: Devops Engineer (Yikai-Liao/symusic, 189 stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 259 stars), Azure Bicep Skill (timothywarner-org/claude-code, 224 stars) and APIOps Deployment for Azure APIM (thomast1906/github-copilot-agent-skills, 202 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Beanstalk Deploy?

pr-pm (a GitHub organization) maintains it in pr-pm/prpm, which has 122 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 6, 2026.

Source: pr-pm/prpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.