New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Elastic Beanstalk Deployment

by pr-pm in pr-pm/prpm

A skill your agent uses when deploying Node.js applications to AWS Elastic Beanstalk or troubleshooting deployment issues - provides dependency installation strategies, monorepo handling, and…

MITAuto-check passedDevelopment

Install Elastic Beanstalk Deployment

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

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

GitHub CLI
$ gh skill install pr-pm/prpm elastic-beanstalk-deployment --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/elastic-beanstalk-deployment .claude/skills/elastic-beanstalk-deployment && 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
elastic-beanstalk-deployment
GitHub stars
122
Token cost
~2.5k tokens
SKILL.md length
634 words
Files
1
Skills in repo
35
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when deploying Node.js applications to AWS Elastic Beanstalk or troubleshooting deployment issues - provides dependency installation strategies, monorepo handling, and…

  • Works in 5 steps: Always Include package-lock.json → Verify Deployment Package → Test Locally First → …
  • Deploying Node.js applications to AWS Elastic Beanstalk
  • SKILL.md covers Overview, When to Use, Official AWS Documentation and Quick Reference: EB Dependency…, plus 10 more sections
  • Calls npm, node and aws

What it does

Elastic Beanstalk Deployment is an agent skill from pr-pm/prpm. Use when deploying Node.js applications to AWS Elastic Beanstalk or troubleshooting deployment issues - provides dependency installation strategies, monorepo handling, and deployment best practices

Its SKILL.md is about 2.5k 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 Development, covering Deployment and Monorepo tooling. It works with Amazon Web Services, Node.js and npm. The repository describes itself as: The universal registry for AI coding tools. The licence is MIT.

When your agent uses it

  • Deploying Node.js applications to AWS Elastic Beanstalk
  • Troubleshooting deployment issues - provides dependency installation strategies
  • Monorepo handling
  • Deployment best practices

Example prompts

  • “/elastic-beanstalk-deployment”

Requirements

  • Node.js
  • Docker

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Always Include package-lock.json
  2. Verify Deployment Package
  3. Test Locally First
  4. Monitor First Deployment
  5. Keep Deployment Packages

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

    Shell commands in SKILL.md call:

    • npm
    • node
    • aws

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

  • Network

    Links to these hosts (documentation or services it may open):

    • docs.aws.amazon.com
    • docs.npmjs.com

    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

Elastic Beanstalk Deployment loads about 2.5k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 634 words of instructions outside code blocks.

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

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). 634 words, ~2,523 tokens.

Download SKILL.mdSave it as .claude/skills/elastic-beanstalk-deployment/SKILL.md (or your agent's skills folder).
name
elastic-beanstalk-deployment
description
Use when deploying Node.js applications to AWS Elastic Beanstalk or troubleshooting deployment issues - provides dependency installation strategies, monorepo handling, and deployment best practices

Elastic Beanstalk Node.js Deployment

Overview

AWS Elastic Beanstalk automates Node.js application deployment but has specific behaviors around dependency installation that can cause issues, especially with monorepos. Understanding when EB installs dependencies vs when it skips installation is critical for successful deployments.

Core principle: Choose between letting EB install dependencies (smaller packages, slower) or bundling node_modules (larger packages, more reliable).

When to Use

Use when:

  • Deploying Node.js applications to AWS Elastic Beanstalk
  • Encountering "Cannot find package" errors during deployment
  • Working with monorepo workspace packages
  • Need reliable deployments without npm registry dependencies
  • Deploying applications with private packages

Don't use for:

  • Non-AWS deployments
  • Docker-based deployments (different dependency strategy)
  • Simple apps with only public npm packages (standard approach works fine)

Official AWS Documentation

Reference: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/nodejs-platform-dependencies.html

Quick Reference: EB Dependency Installation Behavior

ConditionEB Actionnpm Command
package.json exists, NO node_modules/Installs dependenciesnpm install --omit=dev (npm 7+)
node_modules/ directory presentSkips installationNone - uses bundled modules

Deployment Strategies

Strategy 1: Let EB Install Dependencies (Standard)

Best for: Simple apps, all packages in npm registry, no monorepo

yaml
# GitHub Actions workflow
- name: Build application
  run: npm run build

- name: Create deployment package
  run: |
    zip -r app.zip \
      dist/ \
      package.json \
      package-lock.json \
      .ebextensions/

Pros:

  • Smaller deployment packages (5-10MB typical)
  • Consistent with npm ecosystem
  • Uses platform's npm version

Cons:

  • Slower deployments (installs on every deploy)
  • Requires all packages in npm registry
  • Can fail with network/registry issues

Best for: Monorepos, private packages, reliability requirements

AWS official quote: "Bundle node_modules to bypass potential npm registry installation issues."

yaml
# GitHub Actions workflow
- name: Install production dependencies
  run: npm install --omit=dev

- name: Create deployment package
  run: |
    zip -r app.zip \
      dist/ \
      package.json \
      node_modules/ \
      .ebextensions/

Pros:

  • Bypasses npm registry issues
  • Faster deployments (no install phase)
  • Works with workspace packages
  • Reliable and predictable

Cons:

  • Larger packages (50-100MB typical)
  • Must ensure platform-compatible binaries

Monorepo / Workspace Package Strategy

The Problem

Running npm ci --production inside a monorepo workspace:

  • Creates symlinks to workspace packages (not actual files)
  • Results in incomplete node_modules (~3MB instead of ~50MB)
  • Causes "Cannot find package" errors during EB deployment

Example error:

Error: Cannot find module '@prpm/types'
The Solution: Clean Context Installation

Install dependencies outside the workspace context to get real files instead of symlinks:

yaml
- name: Create standalone package.json
  run: |
    mkdir -p /tmp/clean-install
    cd /tmp/clean-install

    # Copy package.json and replace workspace refs with file paths
    cp $GITHUB_WORKSPACE/packages/app/package.json .
    jq --arg workspace "$GITHUB_WORKSPACE" \
      '.dependencies["@workspace/pkg"] = "file:\($workspace)/packages/pkg"' \
      package.json > package.json.tmp
    mv package.json.tmp package.json

- name: Install dependencies (outside workspace)
  run: |
    cd /tmp/clean-install
    npm install --omit=dev --legacy-peer-deps

    # Verify critical packages (real directories, not symlinks)
    test -d node_modules/pg || exit 1
    test -d node_modules/@workspace/pkg/dist || exit 1

- name: Copy to deployment location
  run: |
    rm -rf packages/app/node_modules
    cp -r /tmp/clean-install/node_modules packages/app/

Key steps:

  1. Install outside workspace context
  2. Convert workspace dependencies to file: references
  3. Verify packages are real directories (not symlinks)
  4. Bundle complete node_modules in deployment

Environment Configuration

Override Production Install Mode

Set in Beanstalk console:

NPM_USE_PRODUCTION=false
Specify Node.js Version

In package.json:

json
{
  "engines": {
    "node": "20.x"
  }
}

Note: Version range feature not available on Amazon Linux 2023

Show full SKILL.md (265 more words)Show less

Container Commands for Migrations

When bundling node_modules, migrations can run immediately:

yaml
# .ebextensions/migrations.config
container_commands:
  01_run_migrations:
    command: npm run migrate
    leader_only: true

Why this works with bundled approach:

  1. EB extracts deployment to /var/app/staging/
  2. node_modules/ already present (bundled)
  3. EB skips npm install step
  4. Migrations run with all dependencies available

Common Issues and Solutions

Issue: "Cannot find package 'X'"

Symptoms:

Error: Cannot find module 'pg'
Error: Cannot find module '@prpm/types'

Cause: Package not installed or symlinked

Solution:

bash
# Verify package exists as real directory
ls -la node_modules/pg
file node_modules/@prpm/types  # Should show "directory", not "symbolic link"

# If symlink, use clean context installation (see above)
Issue: "npm install fails with workspace package not found"

Symptoms:

npm ERR! Could not resolve dependency: @workspace/package

Cause: Workspace package not in npm registry

Solution: Use bundled node_modules approach with clean context installation

Issue: Binary compatibility errors

Symptoms:

Error: The module was compiled against a different Node.js version

Cause: Native modules compiled for macOS/Windows, deployed to Linux

Solution:

  • Install dependencies in Linux environment (Docker, GitHub Actions with ubuntu-latest)
  • Or use --platform=linux flag for specific packages
Issue: Deployment package too large (>500MB)

Cause: Dev dependencies or unnecessary files included

Solution:

bash
# Use --omit=dev flag
npm install --omit=dev

# Exclude unnecessary files
zip -r app.zip dist/ package.json node_modules/ .ebextensions/ \
  -x "*.cache/*" "*.test.js" "*.spec.js"

# Use .ebignore file
echo "*.test.js" >> .ebignore
echo "*.spec.js" >> .ebignore

Verification Steps

Before deploying, always verify:

bash
# 1. Check node_modules size (should be 50MB+ for typical apps)
du -sh node_modules
# Expected: 50M-100M (if bundled)
# Red flag: 3M-5M (likely symlinks)

# 2. Verify critical packages exist
ls -la node_modules/pg
ls -la node_modules/fastify
ls -la node_modules/@your-workspace/package

# 3. Check for symlinks (should see real directories)
file node_modules/@your-workspace/package
# Expected: "directory"
# Red flag: "symbolic link to ../../packages/your-package"

# 4. Verify dist directories for workspace packages
test -d node_modules/@your-workspace/package/dist || echo "ERROR: dist missing"

# 5. Test the deployment package locally
unzip -q app.zip -d /tmp/test-deploy
cd /tmp/test-deploy
node dist/index.js  # Should start without errors

Best Practices

1. Always Include package-lock.json

✅ Do: Include package-lock.json for reproducible builds

yaml
zip -r app.zip dist/ package.json package-lock.json node_modules/

❌ Don't: Omit lock file or use only package.json

2. Verify Deployment Package
bash
# Inspect before uploading
unzip -l app.zip | grep node_modules | head -20

# Check size
ls -lh app.zip
# Should be: 50-100MB (bundled) or 5-10MB (unbundled)
3. Test Locally First
bash
# Extract and test the exact deployment package
unzip app.zip -d /tmp/deployment-test
cd /tmp/deployment-test
npm start  # Should work without any npm install
4. Monitor First Deployment

When switching from unbundled to bundled (or vice versa):

  • Watch EB console logs carefully
  • Verify application starts successfully
  • Check for dependency-related errors
  • Have rollback plan ready
5. Keep Deployment Packages

Save successful deployment packages for rollback:

bash
aws s3 cp app.zip s3://my-bucket/deployments/app-$(date +%Y%m%d-%H%M%S).zip

Decision Tree: Which Strategy to Use?

Does your app use monorepo workspace packages?
├─ Yes → Use bundled node_modules (Strategy 2)
│   └─ Install in clean context (outside workspace)
└─ No → Do you need maximum reliability?
    ├─ Yes → Use bundled node_modules (Strategy 2)
    │   └─ Faster deploys, no registry issues
    └─ No → Are all packages in public npm registry?
        ├─ Yes → Let EB install (Strategy 1)
        │   └─ Smaller packages, standard approach
        └─ No (private packages) → Use bundled node_modules (Strategy 2)

Real-World Example: PRPM Registry

This project uses bundled node_modules approach because:

  • @prpm/types is a workspace package (not in npm registry)
  • Requires reliable deployments without registry dependencies
  • Migrations need pg package available immediately
  • Speed and predictability are critical

See .github/workflows/deploy-registry.yml for full implementation.

Additional Resources

© 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/elastic-beanstalk-deployment of pr-pm/prpm.

Open the folder on GitHubat commit 5f993e6

Compare with similar skills

Elastic Beanstalk Deployment 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.

Elastic Beanstalk Deployment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Elastic Beanstalk Deployment this skillpr-pm/prpm122—~2.5kAutomated safety check: PassMIT
TS SDK Authormindfold-ai/Trellis15k—~6.1kAutomated safety check: PassMIT
Setup Portlessqdhenry/Claude-Command-Suite1.3k—~1.2kAutomated safety check: NotesNone
Handsontable Node Script Conventionshandsontable/handsontable22k—~1.1kAutomated safety check: PassCustom licence
Reflexo ReleaseMyriad-Dreamin/typst.ts1.2k—~1.5kAutomated safety check: PassApache-2.0
Remotion Bits Releaseav/remotion-bits488—~1.2kAutomated safety check: PassNone

Similar skills

  • TS SDK Author

    mindfold-ai/Trellis

    Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo.

    15k GitHub stars~6.1k tokensUpdated 10 days ago
    DevelopmentAuto-check passed

  • Setup Portless

    qdhenry/Claude-Command-Suite

    Sets up Portless for a project to replace port numbers with stable named .localhost URLs.

    1.3k GitHub stars~1.2k tokensUpdated 7 mo ago
    DevelopmentAuto-check: notes

  • Handsontable Node Script Conventions

    handsontable/handsontable

    Conventions for .mjs files in the Handsontable monorepo: native node: imports, top-level await, the tasks.json dispatcher and native modules instead of extra dependencies.

    22k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Reflexo Release

    Myriad-Dreamin/typst.ts

    Guide Reflexo/typst.ts release preparation and operator handoffs.

    1.2k GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

  • Remotion Bits Release

    av/remotion-bits

    Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.

    488 GitHub stars~1.2k tokensUpdated 23 days ago
    DevelopmentAuto-check passed

  • Cline CLI Release Publisher

    cline/cline

    Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.

    70k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check: warnings

More from pr-pm/prpm

All 35 skills in this repo

  • Creating Claude Code Agents

    pr-pm/prpm

    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 2 repos~4k tokens
    Auto-check passed

  • Creating Claude Code Hooks

    pr-pm/prpm

    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

  • Creating Claude Rules Files

    pr-pm/prpm

    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

  • Creating Agent Skills Packages

    pr-pm/prpm

    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

  • Integrating Stripe Webhooks

    pr-pm/prpm

    A skill your agent uses when implementing Stripe webhook endpoints and getting 'Raw body not available' or signature verification errors - provides raw body parsing solutions and subscription period…

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

  • Creating agents.md Files

    pr-pm/prpm

    Guides writing an agents.md project-context file: plain markdown with no frontmatter, focused on what an AI coding assistant cannot already know.

    122 GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Elastic Beanstalk Deployment

What does Elastic Beanstalk Deployment do?

A skill your agent uses when deploying Node.js applications to AWS Elastic Beanstalk or troubleshooting deployment issues - provides dependency installation strategies, monorepo handling, and…. Elastic Beanstalk Deployment is an agent skill from pr-pm/prpm.

When should I use Elastic Beanstalk Deployment?

Elastic Beanstalk Deployment fits situations like: deploying Node.js applications to AWS Elastic Beanstalk; troubleshooting deployment issues - provides dependency installation strategies; monorepo handling; deployment best practices.

How do I install Elastic Beanstalk Deployment in Claude Code?

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

How do I install Elastic Beanstalk Deployment in Codex?

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

Can I use Elastic Beanstalk Deployment 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 elastic-beanstalk-deployment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/elastic-beanstalk-deployment, .gemini/skills/elastic-beanstalk-deployment, .github/skills/elastic-beanstalk-deployment and .opencode/skills/elastic-beanstalk-deployment in your project.

What does Elastic Beanstalk Deployment need to run?

Going by SKILL.md and its folder, Elastic Beanstalk Deployment needs the command-line tools its instructions call (npm, node and aws). Our summary lists: Node.js; Docker.

Does Elastic Beanstalk Deployment access the network?

SKILL.md names 2 domains. As links in the text: docs.aws.amazon.com and docs.npmjs.com. This is read from the text; nothing was executed.

Is Elastic Beanstalk Deployment 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 Elastic Beanstalk Deployment use?

Elastic Beanstalk Deployment 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 Elastic Beanstalk Deployment use?

About 2.5k tokens (SKILL.md is roughly 10k 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 Elastic Beanstalk Deployment?

Skills that share tags, products or a category with Elastic Beanstalk Deployment: TS SDK Author (mindfold-ai/Trellis, 15k stars), Setup Portless (qdhenry/Claude-Command-Suite, 1.3k stars), Handsontable Node Script Conventions (handsontable/handsontable, 22k stars) and Reflexo Release (Myriad-Dreamin/typst.ts, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Elastic Beanstalk Deployment?

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.