Agent skill

Pulumi Troubleshooting

Comprehensive guide to troubleshooting Pulumi TypeScript errors, infrastructure issues, and best practices - covers common errors, Outputs handling, AWS Beanstalk deployment, and cost optimization

MITAuto-check passedDevOps & Cloud

Install Pulumi Troubleshooting

skills CLI

$ npx skills add pr-pm/prpm --skill pulumi-troubleshooting -a claude-code

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

GitHub CLI

$ gh skill install pr-pm/prpm pulumi-troubleshooting --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/pulumi-troubleshooting .claude/skills/pulumi-troubleshooting && 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/

Paste into Claude Code

Install the "pulumi-troubleshooting" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/pulumi-troubleshooting into .claude/skills/pulumi-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pulumi-troubleshooting", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/pr-pm/prpm/tree/main/.claude/skills/pulumi-troubleshooting

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add pr-pm/prpm --skill pulumi-troubleshooting -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pr-pm/prpm pulumi-troubleshooting --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pulumi-troubleshooting .agents/skills/pulumi-troubleshooting && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pulumi-troubleshooting" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/pulumi-troubleshooting into .agents/skills/pulumi-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pulumi-troubleshooting", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pr-pm/prpm --skill pulumi-troubleshooting -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pr-pm/prpm pulumi-troubleshooting --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pulumi-troubleshooting .cursor/skills/pulumi-troubleshooting && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pulumi-troubleshooting" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/pulumi-troubleshooting into .cursor/skills/pulumi-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pulumi-troubleshooting", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/pr-pm/prpm.git --path .claude/skills/pulumi-troubleshooting

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pr-pm/prpm --skill pulumi-troubleshooting -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pr-pm/prpm pulumi-troubleshooting --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pulumi-troubleshooting .gemini/skills/pulumi-troubleshooting && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "pulumi-troubleshooting" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/pulumi-troubleshooting into .gemini/skills/pulumi-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pulumi-troubleshooting", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install pr-pm/prpm pulumi-troubleshooting

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add pr-pm/prpm --skill pulumi-troubleshooting -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "pulumi-troubleshooting" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/pulumi-troubleshooting into .github/skills/pulumi-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pulumi-troubleshooting", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pr-pm/prpm --skill pulumi-troubleshooting -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pr-pm/prpm pulumi-troubleshooting --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pulumi-troubleshooting .opencode/skills/pulumi-troubleshooting && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pulumi-troubleshooting" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/pulumi-troubleshooting into .opencode/skills/pulumi-troubleshooting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pulumi-troubleshooting", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: pulumi-troubleshooting
GitHub stars: 122
Token cost: ~1.6k tokens
SKILL.md length: 370 words
Files: 1
Skills in repo: 35
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Comprehensive guide to troubleshooting Pulumi TypeScript errors, infrastructure issues, and best practices - covers common errors, Outputs handling, AWS Beanstalk deployment, and cost optimization

Works in 10 steps: "This expression is not callable. Type… → "Modifiers cannot appear here" (export… → "Configuration key 'aws:region' is not… → …
Tasks that involve Infrastructure as code
SKILL.md covers Common Pulumi TypeScript…, Checklist Before Deploying, Common Environment Variables… and Resources
Calls pulumi and npm; needs PULUMI_ACCESS_TOKEN and GITHUB_CLIENT_SECRET

What it does

Pulumi Troubleshooting is an agent skill from pr-pm/prpm. Comprehensive guide to troubleshooting Pulumi TypeScript errors, infrastructure issues, and best practices - covers common errors, Outputs handling, AWS Beanstalk deployment, and cost optimization

Its SKILL.md is about 1.6k 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 Infrastructure as code. It works with Pulumi, TypeScript and Amazon Web Services. The repository describes itself as: The universal registry for AI coding tools. The licence is MIT.

When your agent uses it

Tasks that involve Infrastructure as code

Example prompts

“/pulumi-troubleshooting”

Requirements

A credential in PULUMI_ACCESS_TOKEN
A credential in GITHUB_CLIENT_SECRET

Workflow steps

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

"This expression is not callable. Type 'never' has no call signatures"
"Modifiers cannot appear here" (export in conditional blocks)
"Configuration key 'aws:region' is not namespaced by the project"
Stack Not Found Errors
Working with Pulumi Outputs
Beanstalk Environment Variables
ACM Certificate Validation
GitHub Actions Pulumi Setup
Debugging TypeScript Compilation
Cost Optimization Tips

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:
- pulumi
- npm
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):
- pulumi.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- PULUMI_ACCESS_TOKEN
- GITHUB_CLIENT_SECRET
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pulumi Troubleshooting loads about 1.6k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 370 words of instructions outside code blocks.

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

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). 370 words, ~1,604 tokens.

Download SKILL.mdSave it as .claude/skills/pulumi-troubleshooting/SKILL.md (or your agent's skills folder).

name: pulumi-troubleshooting
description: Comprehensive guide to troubleshooting Pulumi TypeScript errors, infrastructure issues, and best practices - covers common errors, Outputs handling, AWS Beanstalk deployment, and cost optimization

Pulumi Infrastructure Troubleshooting Skill

Common Pulumi TypeScript Errors and Solutions

1. "This expression is not callable. Type 'never' has no call signatures"

Cause: TypeScript infers a type as never when working with Pulumi Outputs, especially with arrays.

Solution: Wrap the value in pulumi.output() and properly type the callback:

typescript

// ❌ Bad - TypeScript can't infer the type
value: pulumi.all(config.vpc.publicSubnets.map((s: any) => s.id))

// ✅ Good - Explicitly wrap and type
value: pulumi.output(config.vpc.publicSubnets).apply((subnets: any[]) =>
  pulumi.all(subnets.map((s: any) => s.id)).apply(ids => ids.join(","))
)

2. "Modifiers cannot appear here" (export in conditional blocks)

Cause: TypeScript doesn't allow export statements inside if blocks.

Solution: Use optional chaining for conditional exports:

typescript

// ❌ Bad
if (opensearch) {
  export const opensearchEndpoint = opensearch.endpoint;
}

// ✅ Good
export const opensearchEndpoint = opensearch?.endpoint;

3. "Configuration key 'aws:region' is not namespaced by the project"

Cause: Pulumi.yaml config with namespaced keys (e.g., aws:region) cannot use default attribute.

Solution: Remove the config section or don't set defaults for provider configs:

yaml

# ❌ Bad
config:
  aws:region:
    description: AWS region
    default: us-east-1

# ✅ Good - set via workflow/CLI instead
config:
  app:domainName:
    description: Domain name

4. Stack Not Found Errors

Cause: Pulumi stack doesn't exist yet in new environments.

Solution: Use || operator to create if not exists:

bash

pulumi stack select $STACK || pulumi stack init $STACK

5. Working with Pulumi Outputs

Key Concepts:

pulumi.Output<T> is a promise-like wrapper for async values
Use .apply() to transform Output values
Use pulumi.all([...]) to combine multiple Outputs
Use pulumi.output(value) to wrap plain values as Outputs

Common Patterns:

typescript

// Transforming a single Output
const url = endpoint.apply(e => `https://${e}`);

// Combining multiple Outputs
const connectionString = pulumi.all([host, port, db]).apply(
  ([h, p, d]) => `postgres://${h}:${p}/${d}`
);

// Interpolating Outputs
const message = pulumi.interpolate`Server at ${endpoint}:${port}`;

Nested Outputs (Properties that are themselves Outputs):

typescript

// ❌ Bad - resource.property might be an Output<string>
const endpoint = instance.apply(i => i.endpoint.split(":")[0]); // ERROR: Property 'split' does not exist

// ✅ Good - unwrap nested Output with pulumi.output()
const endpoint = instance.apply(i =>
  pulumi.output(i.endpoint).apply(e => e.split(":")[0])
);

// ✅ Alternative - use pulumi.all to flatten
const endpoint = pulumi.all([instance]).apply(([inst]) =>
  pulumi.output(inst.endpoint).apply(e => e.split(":")[0])
);

6. Beanstalk Environment Variables

Issue: Complex objects or arrays need to be serialized.

Solution: Use JSON.stringify for complex values:

typescript

{
  namespace: "aws:elasticbeanstalk:application:environment",
  name: "ALLOWED_ORIGINS",
  value: allowedOrigins.apply(origins => JSON.stringify(origins)),
}

7. ACM Certificate Validation

Issue: Certificate validation hangs or times out.

Solution: Ensure DNS records are created and wait for validation:

typescript

// 1. Create certificate
const cert = new aws.acm.Certificate(...);

// 2. Create DNS validation record
const validationRecord = new aws.route53.Record(..., {
  name: cert.domainValidationOptions[0].resourceRecordName,
  type: cert.domainValidationOptions[0].resourceRecordType,
  records: [cert.domainValidationOptions[0].resourceRecordValue],
});

// 3. Wait for validation to complete
const validation = new aws.acm.CertificateValidation(..., {
  certificateArn: cert.arn,
  validationRecordFqdns: [validationRecord.fqdn],
});

8. GitHub Actions Pulumi Setup

Best Practices:

yaml

- name: Setup Pulumi
  uses: pulumi/actions@v5

- name: Configure Stack
  run: |
    STACK="${{ inputs.stack || 'prod' }}"
    pulumi stack select $STACK || pulumi stack init $STACK
    pulumi config set aws:region ${{ env.AWS_REGION }}
    # Set other non-secret configs here

- name: Pulumi Up
  run: pulumi up --yes --non-interactive
  env:
    PULUMI_ACCESS_TOKEN: ${{ secrets.PULUMI_ACCESS_TOKEN }}
    PULUMI_CONFIG_PASSPHRASE: ${{ secrets.PULUMI_CONFIG_PASSPHRASE }}

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

9. Debugging TypeScript Compilation

Quick checks:

Run npm run build in the infra package locally
Check for conditional exports inside blocks
Verify all Pulumi Outputs are properly typed
Look for .map() calls on potentially undefined arrays
Ensure all imports are correct

10. Cost Optimization Tips

Beanstalk vs ECS Fargate:

Beanstalk with t3.micro: ~$32/month
ECS Fargate: ~$126/month
Key difference: Beanstalk runs on EC2 instances you control
Use public subnets to avoid NAT Gateway costs ($32/month)

Checklist Before Deploying

Run npm run build locally to catch TypeScript errors
Test with pulumi preview before pulumi up
Verify all secrets are in GitHub Secrets (not hardcoded)
Check stack name matches environment (dev/staging/prod)
Ensure domain/DNS is configured if using custom domains
Verify VPC/subnets exist if using existing infrastructure
Check that all required extensions/providers are installed

Common Environment Variables to Set

typescript

// Database
DATABASE_URL: pulumi.interpolate`postgres://${user}:${pass}@${host}:5432/${db}`

// Redis
REDIS_URL: redisEndpoint.apply(e => `redis://${e}:6379`)

// S3
S3_BUCKET: bucketName
S3_REGION: region

// Auth
GITHUB_CLIENT_ID: clientId
GITHUB_CLIENT_SECRET: clientSecret

// App Config
NODE_ENV: "production"
PORT: "8080"
LOG_LEVEL: "info"

Resources

Files

Just SKILL.md in .claude/skills/pulumi-troubleshooting of pr-pm/prpm.

Open the folder on GitHubat commit 5f993e6

Compare with similar skills

Pulumi Troubleshooting 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.

Pulumi Troubleshooting compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pulumi Troubleshooting this skillpr-pm/prpm	122	—	~1.6k	Automated safety check: Pass	MIT	3 days ago
AWS Cdk Developmentzxkane/aws-skills	367	2 repos	~2.5k	Automated safety check: Pass	MIT	3 mo ago
AWS Native Runtime Investigationpulumi/pulumi-aws-native	108	—	~753	Automated safety check: Pass	Apache-2.0	yesterday
Ops Add New Chainboundless-xyz/boundless	193	—	~3.8k	Automated safety check: Pass	Apache-2.0	1 mo ago
AWS Sst Developmentzxkane/aws-skills	367	—	~2.7k	Automated safety check: Warn	MIT	3 mo ago
Writing Infrastructure Codeancoleman/ai-design-components	525	—	~3.9k	Automated safety check: Pass	MIT	10 mo ago

Similar skills

AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
367 GitHub starsUsed in 2 repos~2.5k tokens
DevOps & CloudAuto-check passed
AWS Native Runtime Investigation
pulumi/pulumi-aws-native
Official
Use after triage or repository evidence establishes that an issue involves Pulumi AWS Native runtime behavior across the Pulumi provider protocol, generated CloudFormation metadata, and AWS Cloud…
108 GitHub stars~753 tokensUpdated yesterday
DevOps & CloudAuto-check passed
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
AWS Sst Development
zxkane/aws-skills
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
367 GitHub stars~2.7k tokensUpdated 3 mo ago
DevOps & CloudAuto-check: warnings
Writing Infrastructure Code
ancoleman/ai-design-components
Managing cloud infrastructure using declarative and imperative IaC tools.
525 GitHub stars~3.9k tokensUpdated 10 mo ago
DevOps & CloudAuto-check passed
Generating Infrastructure As Code
jeremylongshore/tons-of-skills-marketplace
Execute use when generating infrastructure as code configurations.
2.8k GitHub stars~1.2k tokensUpdated today
DevOps & CloudAuto-check passed

Questions about Pulumi Troubleshooting

What does Pulumi Troubleshooting do?

Comprehensive guide to troubleshooting Pulumi TypeScript errors, infrastructure issues, and best practices - covers common errors, Outputs handling, AWS Beanstalk deployment, and cost optimization. Pulumi Troubleshooting is an agent skill from pr-pm/prpm.

When should I use Pulumi Troubleshooting?

Pulumi Troubleshooting fits situations like: tasks that involve Infrastructure as code.

How do I install Pulumi Troubleshooting in Claude Code?

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

How do I install Pulumi Troubleshooting in Codex?

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

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

What does Pulumi Troubleshooting need to run?

Going by SKILL.md and its folder, Pulumi Troubleshooting needs the command-line tools its instructions call (pulumi and npm) and credentials named PULUMI_ACCESS_TOKEN and GITHUB_CLIENT_SECRET. Our summary lists: A credential in PULUMI_ACCESS_TOKEN; A credential in GITHUB_CLIENT_SECRET.

Does Pulumi Troubleshooting access the network?

SKILL.md names 1 domain. As links in the text: pulumi.com. This is read from the text; nothing was executed.

Is Pulumi Troubleshooting 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 Pulumi Troubleshooting use?

Pulumi Troubleshooting 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 Pulumi Troubleshooting use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 Pulumi Troubleshooting?

Skills that share tags, products or a category with Pulumi Troubleshooting: AWS Cdk Development (zxkane/aws-skills, 367 stars), AWS Native Runtime Investigation (pulumi/pulumi-aws-native, 108 stars), Ops Add New Chain (boundless-xyz/boundless, 193 stars) and AWS Sst Development (zxkane/aws-skills, 367 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pulumi Troubleshooting?

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.

Install Pulumi Troubleshooting

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Pulumi Infrastructure Troubleshooting Skill

Common Pulumi TypeScript Errors and Solutions

1. "This expression is not callable. Type 'never' has no call signatures"

2. "Modifiers cannot appear here" (export in conditional blocks)

3. "Configuration key 'aws:region' is not namespaced by the project"

4. Stack Not Found Errors

5. Working with Pulumi Outputs

6. Beanstalk Environment Variables

7. ACM Certificate Validation

8. GitHub Actions Pulumi Setup

9. Debugging TypeScript Compilation

10. Cost Optimization Tips

Checklist Before Deploying

Common Environment Variables to Set

Resources

Files

Compare with similar skills

Similar skills

More from pr-pm/prpm

Related

Questions about Pulumi Troubleshooting