Terraform and data platform infrastructure
Skill vaquarkhan/data-engineering-agent-skills/skills/terraform-and-data-platform-infrastructure
Production-grade Agent Skills for data engineering AI agents: 73 workflows, platform presets, safe backfill/replay, Kafka & Spark reliability, MCP observability, and VS Code/JetBrains installers.
npx -y skills add vaquarkhan/data-engineering-agent-skills --skill terraform-and-data-platform-infrastructureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 21 stars21 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
Guides agents through infrastructure as code for data platforms. Use when provisioning or modifying storage, roles, secrets, networking, orchestration resources, catalogs, compute, or environment-specific data platform foundations.
SKILL.md
2.3 KB, 388 tokens by cl100k_base, as published. Nobody here has run it
Terraform And Data Platform Infrastructure
Overview
Use this skill when data engineering work depends on platform infrastructure, not just SQL or code. It helps agents make environment setup reproducible, reviewable, and promotion-safe.
When to Use
- provisioning buckets, warehouses, jobs, roles, or secrets
- changing network or access boundaries
- creating environment-specific data platform resources
- standardizing dev, staging, and production infrastructure
Do not treat manual console changes as equivalent to managed infrastructure.
Workflow
-
Identify the platform boundary. Decide which resources belong in infrastructure code versus application or transformation code.
-
Model environments explicitly. Capture:
- naming rules
- isolation boundaries
- secrets strategy
- promotion path
-
Keep access and governance in the same review surface as infrastructure.
-
Validate change safety before apply. Watch for:
- destructive resource replacement
- role drift
- environment coupling
- hidden manual dependencies
-
Document day-two operations. Provisioning is only part of the lifecycle.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "It is faster to click this in the console." | Manual changes drift quickly and are hard to review or reproduce. |
| "We only need Terraform for production." | Lower environments drift first and make promotion less trustworthy. |
| "Security can update roles separately." | Infra and access changes often need one coordinated review. |
Red Flags
- resource names and environments are inconsistent
- secrets handling is unclear
- destructive changes are not reviewed explicitly
- manual prerequisites are undocumented
Verification
- Infrastructure boundaries and environment model are explicit
- Access, secrets, and governance are reviewed with the infra change
- Apply risk is understood before rollout
- Day-two operations are documented where relevant
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.