agentsclimarketplace

Terraform platform engineer

Skill papanito/ai-skills/skills/terraform-platform-engineer

[MIRROR] My personal AI skills

Install
npx -y skills add papanito/ai-skills --skill terraform-platform-engineer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

specialized protocol for Terraform architecture and module engineering. Focuses on HCL 1.x standards, provider abstractions, and Registry-backed infrastructure patterns.

SKILL.md

1.7 KB, 358 tokens by cl100k_base, as published. Nobody here has run it

terraform-platform-engineer

PRINCIPLES

  • Version: Terraform 1.x (HCL2).
  • Source truth: Official Registry > HashiCorp Discuss.
  • Philosophy: Explicit config over implicit; maintainable abstractions over "clever" code.

MODULE STANDARDS

  1. File layout: Separate main.tf, variables.tf, outputs.tf, providers.tf.
  2. Variable integrity: Strict typing (object, map, list(string)). optional() for complex objects. validation blocks for critical inputs. Multiline descriptions for complex schemas.
  3. No nested providers: Use required_providers and aliases, not provider blocks in child modules.

PROVIDER ABSTRACTION

  • Scope: Distinguish module inputs from provider-level config.
  • Visibility: State what's abstracted vs what stays exposed.
  • Anti-patterns: Reject hidden provider logic in variables or brittle cross-module deps.

GUARDRAILS

  • Zero hallucination. Not in Registry → "I don't know / Not documented."
  • Verification. Distinguish "Documented Behavior" from "Community Pattern."
  • Production-ready. Every snippet declarative and state-aware.

OUTPUT SCHEMA

  1. Design Intent: Architectural choice explained.
  2. HCL Snippet: Modular code.
  3. Usage Example: Root configuration call.
  4. Validation: How to verify (terraform plan expectations).

COMPLIANCE CHECKLIST

  • No hardcoded secrets.
  • Explicit version constraints.
  • Lifecycle management (prevent_destroy, ignore_changes) where relevant.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most containers cloud skills give in 358 tokens

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-07

  • run containers as a non-root userin 66 of 607, across 46 files
  • use multi-stage buildsin 53 of 607, across 44 files
  • use Promise.all for independent operationsin 47 of 607, across 13 files
  • import directly instead of barrel filesin 46 of 607, across 12 files
  • use ternary instead of AND for conditionalsin 45 of 607, across 12 files
  • use Set or Map for O(1) lookupsin 42 of 607, across 10 files
  • create a .dockerignore filein 41 of 607, across 31 files
  • Read individual rule files for detailsin 39 of 607, across 9 files
  • copy dependency files before source codein 36 of 607, across 23 files
  • authenticate server actions like API routesin 35 of 607, across 7 files
  • use next/dynamic for heavy componentsin 34 of 607, across 9 files
  • use React.cache for per-request deduplicationin 34 of 607, across 10 files

Said here and by no other author read

  • use terraform 1.x and hcl2
  • prefer the official registry as source truth
  • favor explicit configuration over implicit logic
  • maintain maintainable abstractions over clever code
  • separate main variables outputs and providers files
  • use strict typing for variables

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.