Skip to content
TrustedSkillsbeta
Back to all skills

Terraform Specialist

Listed
sickn33·vlatest·cloud·MIT

Automates infrastructure provisioning and management on AWS, Azure, and GCP using Terraform code.

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 sickn33/agentic-awesome-skills --skill terraform-specialist -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

sickn33

Taken from the source listing. We haven't verified who controls this account.

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Scanned
0 files
Copies in repo
3 — all of them scanned
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

The Terraform Specialist skill enables AI agents to manage cloud infrastructure as code, specifically focusing on the lifecycle of Terraform state files and resource provisioning. It allows agents to safely plan, apply, and destroy resources while maintaining strict control over remote backends like S3 or Azure Blob Storage.

When to use it

  • Automating the creation and modification of complex multi-cloud environments without manual CLI intervention.
  • Managing state file locking and consistency across distributed teams to prevent configuration drift.
  • Executing safe resource destruction workflows that adhere to organizational compliance policies.
  • Generating and validating terraform plan outputs before committing changes to production repositories.

Key capabilities

  • State file management with remote backends (S3, Azure Blob, GCS).
  • Resource lifecycle automation including create, read, update, and delete operations.
  • Integration with version control systems for infrastructure code tracking.
  • Execution of terraform init, plan, and apply commands programmatically.

Example prompts

  • "Initialize a new Terraform project in AWS and provision a VPC with public and private subnets."
  • "Plan the changes required to update the instance type for all production EC2 resources from t3.medium to t3.large."
  • "Destroy the development environment state file located in our S3 bucket after confirming no active workloads exist."

Tips & gotchas

Ensure your AI agent has explicit read/write permissions on the remote backend storage before attempting state management operations. Always verify that terraform plan outputs are reviewed by a human or validated against policy-as-code rules before executing apply in production environments to prevent accidental data loss.