Skip to content
TrustedSkillsbeta
Back to all skills

Provider Actions

Official
hashicorp·vlatest·cloud·MPL-2.0

Provider Actions allows you to execute commands within infrastructure providers (like AWS, Azure, GCP) directly from your workflows for automated management.

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 hashicorp/agent-skills --skill provider-actions -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

hashicorp

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 hashicorp/agent-skills at f706481af9.

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

Commit
f706481af9
Manifest
plugins/terraform/skills/provider-actions/SKILL.md
Scanned
1 file, 484 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 provider-actions skill enables AI agents to interact with and manage infrastructure providers, such as HashiCorp tools, by executing predefined actions like provisioning resources, configuring systems, or monitoring environments. It allows seamless integration between the agent and external provider APIs.

When to use it

  • Automating infrastructure setup for development or testing environments.
  • Performing routine maintenance tasks on cloud or on-premise resources.
  • Integrating AI agents with HashiCorp tools like Terraform or Vault for dynamic configuration management.

Key capabilities

  • Execute provider-specific actions via API calls.
  • Manage infrastructure provisioning and deprovisioning.
  • Support for multiple providers through a unified interface.

Example prompts

  • "Provision a new virtual machine using the AWS provider."
  • "Update the configuration of a Terraform-managed resource."
  • "Check the status of all resources managed by the HashiCorp Vault provider."

Tips & gotchas

  • Ensure that the AI agent has proper authentication credentials for the target provider.
  • Some actions may require elevated permissions or specific API access, so verify these prerequisites before deployment.