Skip to content
SkillCheatSheet Sign in

hashicorp/agent-skills

Agent skills in the GitHub repository hashicorp/agent-skills, each with its code score out of 100.

A collection of Agent skills and Claude Code plugins for HashiCorp products.

Repository score
69 / 100 C
Skills
17
Verified
1
Average skill score
69
GitHub stars
926
License
MPL-2.0

Open hashicorp/agent-skills on GitHub

17 skills in this repository

  1. provider-framework-migration

    Migrate Terraform provider resources and data sources from Plugin SDKv2 to the Plugin Framework: muxing both plugins in one provider (terraform-plugin-mux, tf5to6server), per-reso…

    Verified85A
  2. terraform-search-import

    Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control…

    78B
  3. provider-configuration

    Implement Terraform provider configuration and authentication with the Plugin Framework: provider schema for credentials (Optional + Sensitive attributes), environment variable fa…

    76B
  4. provider-docs

    Create, update, and review Terraform provider documentation for Terraform Registry using HashiCorp-recommended patterns, tfplugindocs templates, and schema descriptions. Use when…

    75B
  5. new-terraform-provider

    Use this when scaffolding a new Terraform provider with the Plugin Framework: workspace layout, go module setup, provider server main.go, and a provider.go with schema and Configu…

    69C
  6. provider-actions

    Implement Terraform Provider actions using the Plugin Framework. Use when developing imperative operations that execute at lifecycle events (before/after create, update, destroy).

    69C
  7. run-acceptance-tests

    Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`, when a test fails with missi…

    69C
  8. terraform-test

    Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior…

    69C
  9. aws-ami-builder

    Build Amazon Machine Images (AMIs) with Packer using the amazon-ebs builder. Use when creating custom AMIs for EC2 instances.

    68C
  10. provider-ephemeral-resources

    Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal f…

    68C
  11. provider-test-patterns

    Terraform provider acceptance test patterns using terraform-plugin-testing with the Plugin Framework. Covers test structure, TestCase/TestStep fields, ConfigStateChecks with custo…

    67C
  12. azure-verified-modules

    Azure Verified Modules (AVM) requirements and best practices for developing certified Azure Terraform modules. Use when creating or reviewing Azure modules that need AVM certifica…

    64C
  13. provider-resources

    Implement Terraform Provider resources and data sources using the Plugin Framework: CRUD operations, schema design, plan modifiers and validators, not-found handling, waiters for…

    64C
  14. push-to-registry

    Push Packer build metadata to HCP Packer registry for tracking and managing image lifecycle. Use when integrating Packer builds with HCP Packer for version control and governance.

    64C
  15. windows-builder

    Build Windows images with Packer using WinRM communicator and PowerShell provisioners. Use when creating Windows AMIs, Azure images, or VMware templates.

    62C
  16. terraform-policy

    Write, test, or convert Terraform Policy files (.policy.hcl, .policytest.hcl, Sentinel→tfpolicy). Triggers: policy.hcl, policytest, convert sentinel, tfpolicy, write a policy.

    61C
  17. azure-image-builder

    Build Azure managed images and Azure Compute Gallery images with Packer. Use when creating custom images for Azure VMs.

    57C

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.