Skip to content
TrustedSkillsbeta
Back to all skills

Pulumi Automation Api

Official
pulumi·vlatest·cloud·Apache-2.0

Helps with automation, API as part of deploying and managing cloud infrastructure workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add pulumi/agent-skills --skill pulumi-automation-api --full-depth -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

pulumi

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned pulumi/agent-skills at 9b794aec9c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9b794aec9c
Manifest
pulumi/skills/pulumi-automation-api/SKILL.md
Scanned
3 files, 310 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The Pulumi Automation API enables programmatic control over infrastructure as code (IaC) workflows, allowing users to automate deployment, updates, and management of cloud resources using Pulumi programs. It supports integration with CI/CD pipelines and provides a consistent interface for managing infrastructure across multiple cloud providers.

When to use it

  • Automating the deployment of infrastructure during continuous integration or delivery processes.
  • Managing infrastructure changes in response to application code updates.
  • Orchestrating multi-cloud resource provisioning through a single API.
  • Building tools that need to interact with Pulumi projects programmatically, such as custom dashboards or monitoring systems.

Key capabilities

  • Programmatic deployment and management of Pulumi stacks.
  • Integration with CI/CD pipelines for automated infrastructure updates.
  • Support for multiple cloud providers (AWS, Azure, GCP, etc.).
  • Ability to manage stack configurations, secrets, and outputs through API calls.

Example prompts

  • "Deploy the latest version of my Pulumi stack to AWS."
  • "Update the configuration of the 'dev' environment stack with new resource parameters."
  • "List all stacks in my project along with their current status."

Tips & gotchas

  • Ensure your Pulumi project is properly configured and authenticated before using the API.
  • Be cautious when making bulk changes to infrastructure via automation; always test in non-production environments first.