hashicorp agent-skills
OFFICIALLABSCO SUMMARY
Four skills cover Packer: building AWS AMIs, Azure managed and Compute Gallery images, and Windows images, plus pushing build metadata to the HCP Packer registry. The other twelve are Terraform, and six of those are about developing a terraform-provider-* project itself with the Plugin Framework — scaffolding a new provider, implementing resources and data sources, writing imperative actions, generating Registry documentation with tfplugindocs, and writing acceptance tests. The remaining six are for people who just write Terraform configuration: the official HCL style guide, native .tftest.hcl testing, refactoring a monolith into modules, importing existing cloud resources with Terraform Search, Terraform Stacks, and Azure Verified Modules certification.
Two different readers get value here. If you maintain a Terraform provider, the six provider-development skills are the reason to install this at all; nothing else in the ecosystem documents the Plugin Framework this specifically. If you're a typical Terraform user writing .tf files, only about six of these sixteen skills will ever fire for you, and the provider-building half will sit unused. Packer users building custom images get a smaller, self-contained set of four regardless of which side of Terraform interests them.
READ THE FULL ANALYSIS
Cloud credentials, sometimes. Five of the sixteen skills need real account credentials configured before they do anything — unsurprising for the Packer image builders, which have to actually reach AWS or Azure to build an image — while the other eleven work against local Terraform or Packer tooling alone.
Two products today, more implied. The README's own file tree lists a placeholder for future HashiCorp products — Vault, Consul, and others — but as of this snapshot only Terraform and Packer have any skills in it.
ALSO IN THIS PACKAGE
terraform
Terraform skills for configuration, modules, providers, tests, imports, stacks, and policy.
packer
Packer skills for image building and HCP Packer registry workflows.
WHAT'S INSIDE
16 showing · 16 totalaws-ami-builder
Set up a stock Linux server on Amazon once — updates, packages, your own configuration — and freeze it into an image every future server launches from.
azure-image-builder
Takes a freshly prepared Azure virtual machine and saves it as a reusable image, so every machine launched from it afterwards starts out already configured.
azure-verified-modules
Azure certifies reusable Terraform building blocks, and this is the rulebook they are judged against: 37 requirements covering naming, version pinning, variables, outputs, testing and breaking changes.
new-terraform-provider
A Terraform provider is the plug-in that teaches Terraform how to manage one particular service; this sets up an empty one — folders, module, entry point — that already compiles and passes its tests.
provider-actions
Terraform describes what infrastructure should look like; it does not run errands. An action is the exception — a job fired at a set moment, such as just after something is created — and this adds one to a plug-in, tests and docs included.
provider-docs
The public reference pages for a Terraform plug-in, written as descriptions inside the code and regenerated from it, so what people read always matches what the software does.
provider-resources
Adds one more kind of thing a Terraform plug-in can manage — a database, a bucket, a DNS record — so it can be created, read back, changed and deleted from a configuration file, with tests to prove it.
provider-test-patterns
Terraform provider tests create real infrastructure and then check it; this is how to write those tests so a resource's whole life — created, changed, imported, destroyed — is covered and old bugs cannot come back.
push-to-registry
Keeps a catalogue of every machine image you build and of which version is current, so the servers you create always pick up the right one.
refactor-module
One giant Terraform configuration grows unmanageable; this turns it into tidy, reusable building blocks other projects can pull in, while the infrastructure already running stays untouched.
run-acceptance-tests
Runs one of a Terraform provider's live tests — the kind that really creates cloud infrastructure — and, when it fails, narrows down why.
terraform-search-import
Cloud accounts fill up with servers and buckets nobody created through Terraform; this tracks them down and puts them under its management, without rebuilding anything.
terraform-stacks
A layer that sits above ordinary Terraform: describe the pieces of a system once, then roll the whole thing out again and again — another region, another account, another environment.
terraform-style-guide
Tidies Terraform files into the layout and naming HashiCorp itself recommends, so a configuration reads the way every other well-kept one does.
terraform-test
Automated tests for a Terraform module, so a change is proved correct by a test run instead of by someone watching a real deployment.
windows-builder
A Windows server image that new machines start from already configured, built automatically instead of installing and updating Windows by hand every time — on Amazon, Azure or VMware.
HOW TO GET IT
npx skills add hashicorp/agent-skillsnpx skills add hashicorp/agent-skills --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
/plugin marketplace add hashicorp/agent-skills/plugin install terraform@hashicorp/plugin install packer@hashicorpTyped inside the agent's own prompt, not in a terminal. The marketplace is called hashicorp, which is the part after the @.