new-terraform-provider
by hashicorpThe new-terraform-provider skill helps backend and infrastructure developers scaffold a new Terraform provider with the Plugin Framework. It guides workspace creation, Go module setup, main.go wiring, and build/test validation for a clean provider bootstrap.
This skill scores 68/100, which is acceptable for directory listing but not especially strong. For users, that means it provides a real, usable workflow for scaffolding a new Terraform provider, yet they should expect some manual interpretation because the instructions are fairly brief and one key step remains a TODO in the example code.
- Directly triggerable for a specific task: scaffolding a new Terraform provider with Plugin Framework.
- Provides a concrete, ordered workflow including workspace creation, Go module setup, dependency install, build, and test steps.
- Includes an example main.go file, which gives agents a practical starting point instead of only abstract guidance.
- The example code still contains TODO comments and a placeholder provider address, so adoption requires manual cleanup.
- No install command, references, or deeper docs are provided, so agents may need to infer some implementation details.
Overview of new-terraform-provider skill
What new-terraform-provider does
The new-terraform-provider skill helps you scaffold a new Terraform provider with the Plugin Framework. It is aimed at backend and infrastructure developers who want a working starting point, not a theoretical explanation.
Who should use it
Use the new-terraform-provider skill when you need to create a new provider workspace, initialize the Go module, wire up a main.go, and validate the first build/test loop. It is most useful if you already know the provider you want to build but want the setup done in the right order.
What makes it useful
This skill is decision-oriented: it tells the agent when to stop and confirm before creating a new workspace, and it pushes a practical sequence of setup steps instead of loose brainstorming. That reduces the common adoption blockers for a new-terraform-provider install, like generating files in the wrong directory or skipping the build and test checks.
How to Use new-terraform-provider skill
Install and activate it
Use the new-terraform-provider install flow in your agent environment, then point the skill at the Terraform provider project you want to create or bootstrap. If you are already inside an existing provider repo, the skill should first confirm whether a new workspace is actually desired.
Give the skill a concrete target
For best new-terraform-provider usage, provide the provider name, intended registry address, module path, and whether you are starting fresh or extending an existing repo. A weak request is “set up a Terraform provider”; a stronger one is “create a new provider workspace named terraform-provider-acme, use registry.terraform.io/acme/widgets, and keep the build target minimal for now.”
Follow the repo files in order
Start with SKILL.md, then read assets/main.go to see the expected provider entrypoint pattern. The example main file is the most important support artifact here because it shows the debug flag, provider server wiring, and where the TODOs still need to be replaced with real values.
Use the skill as a scaffold, not a finished provider
The skill’s job is to create a clean bootstrap path: new Go module, framework dependency, provider entrypoint, go mod tidy, go build -o /dev/null, and go test ./.... It does not replace provider design work such as schema planning, CRUD implementation, authentication strategy, or acceptance-test setup.
new-terraform-provider skill FAQ
Is new-terraform-provider only for brand-new repos?
No. It is best for a new workspace, but it can also help you set up a provider scaffold inside a larger mono-repo if you want a clean Terraform-specific module boundary. If you are already in a provider workspace, the skill should ask before creating another one.
What is the main difference from a normal prompt?
A normal prompt often forgets critical setup steps or produces a main.go that does not match the Plugin Framework pattern. The new-terraform-provider skill gives you a more reliable installation flow and a clearer sequence for getting from empty directory to compiling provider binary.
Is this a good beginner skill?
Yes, if your goal is to start a provider project with guidance. It is not a substitute for learning Terraform provider architecture, but it lowers the friction of the first setup pass and reduces the chance of missing basic module and build steps.
When should I not use it?
Do not use new-terraform-provider if you already have an established provider codebase and only need to add a resource, fix a schema, or refactor an existing binary. In those cases, the skill would add workspace-scaffolding steps you do not need.
How to Improve new-terraform-provider skill
Provide the missing values up front
The best new-terraform-provider skill outputs come from inputs that name the provider address, module path, package layout, and whether debug support matters. If you leave those blank, the agent will have to infer values like example.org/terraform-provider-demo or a placeholder registry address, which usually leads to follow-up cleanup.
Replace placeholders immediately
The repo example still includes TODO-driven placeholders in assets/main.go, especially around the provider address and release-time version wiring. After the first pass, update those values before you consider the scaffold complete, or your build may succeed while the binary still points to a demo identity.
Validate the scaffold the same way the skill does
The workflow is only complete when go mod tidy, go build -o /dev/null, and go test ./... pass in the new workspace. If any of those fail, fix the module path, provider import path, or package layout before adding resources or acceptance tests.
Iterate from scaffold to real provider design
Once the workspace is stable, ask for the next layer: provider schema, authentication, resource layout, and documentation generation. That is where new-terraform-provider for Backend Development becomes most valuable, because it gets the foundation right and leaves the implementation details to the next focused pass.