How do I install the Y Miyazaki Config Terraform Validation skill?

Run npx skillmds@latest add tomevault-io/y-miyazaki-config-terraform-validation in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Y Miyazaki Config Terraform Validation skill do?

Input It is listed under DevOps & Infra on SkillMD.

Is Y Miyazaki Config Terraform Validation safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Y Miyazaki Config Terraform Validation?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Y Miyazaki Config Terraform Validation free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Y Miyazaki Config Terraform Validation?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Y Miyazaki Config Terraform Validation by tomevault-io

Name: Y Miyazaki Config Terraform Validation
Author: tomevault-io

File contents

Input

Terraform path or directory (required)
Validation script: scripts/validate.sh (required, run from the terraform-validation skill directory)
Optional flags: --fix, --verbose

Output Specification

Return structured Markdown in accordance with references/common-output-format.md.

Structured results in fixed order: terraform fmt, terraform validate, tflint, trivy config.

Execution Scope

Always use scripts/validate.sh for comprehensive validation. Do not run individual commands.
Script runs all checks in deterministic order.
Individual commands are for debugging only (see references/common-individual-commands.md).
Do not review code design decisions (use terraform-review for that)

USE FOR:

run Terraform syntax/lint/security checks before commit
reproduce CI validation failures locally
validate a scoped Terraform directory during iterative changes

DO NOT USE FOR:

perform design and architecture review (use terraform-review)
implement Terraform resource changes as a primary task
validate non-Terraform files

Reference Files Guide

common-checklist.md (always read)
common-output-format.md (always read)
common-troubleshooting.md - Read when checks fail unexpectedly.
common-individual-commands.md - Read when debugging one tool directly.
category-security.md - Read when trivy reports security findings.

Workflow

Run bash scripts/validate.sh.
For scoped runs, pass a target directory: bash scripts/validate.sh ./terraform/<target>/.
Use --fix for formatting corrections and --verbose for diagnostics.
Retry at most 2 times after fixes; if checks still fail, return blocking findings and stop.

Examples

bash scripts/validate.sh
bash scripts/validate.sh ./terraform/base/
bash scripts/validate.sh --fix --verbose

Source: y-miyazaki/config — distributed by TomeVault.

---name: y-miyazaki-config-terraform-validationdescription: Input---## Input- Terraform path or directory (required)- Validation script: `scripts/validate.sh` (required, run from the terraform-validation skill directory)- Optional flags: `--fix`, `--verbose`## Output SpecificationReturn structured Markdown in accordance with [references/common-output-format.md](references/common-output-format.md).Structured results in fixed order: terraform fmt, terraform validate, tflint, trivy config.## Execution Scope- **Always use `scripts/validate.sh`** for comprehensive validation. Do not run individual commands.- Script runs all checks in deterministic order.- Individual commands are for debugging only (see [references/common-individual-commands.md](references/common-individual-commands.md)).- **Do not review code design decisions** (use terraform-review for that)### USE FOR:- run Terraform syntax/lint/security checks before commit- reproduce CI validation failures locally- validate a scoped Terraform directory during iterative changes### DO NOT USE FOR:- perform design and architecture review (use terraform-review)- implement Terraform resource changes as a primary task- validate non-Terraform files## Reference Files Guide- [common-checklist.md](references/common-checklist.md) (always read)- [common-output-format.md](references/common-output-format.md) (always read)- [common-troubleshooting.md](references/common-troubleshooting.md) - Read when checks fail unexpectedly.- [common-individual-commands.md](references/common-individual-commands.md) - Read when debugging one tool directly.- [category-security.md](references/category-security.md) - Read when trivy reports security findings.## Workflow1. Run `bash scripts/validate.sh`.2. For scoped runs, pass a target directory: `bash scripts/validate.sh ./terraform/<target>/`.3. Use `--fix` for formatting corrections and `--verbose` for diagnostics.4. Retry at most 2 times after fixes; if checks still fail, return blocking findings and stop.### Examples```bashbash scripts/validate.shbash scripts/validate.sh ./terraform/base/bash scripts/validate.sh --fix --verbose```---> Source: [y-miyazaki/config](https://github.com/y-miyazaki/config) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Y Miyazaki Config Terraform Validation