terraform-skill MCP — 사용 사례, 설치 & 라이브 데모

왜 쓰나요

핵심 기능

Testing decision framework: native tests vs Terratest by scenario
Module structure, naming, versioning, and docs conventions
Ready-to-adapt GitHub Actions and GitLab CI pipelines with Infracost + tfsec/Checkov
Side-by-side recommended vs problematic patterns
Based on terraform-best-practices.com and the terraform-aws-modules ecosystem

라이브 데모

실제 사용 모습

terraform-skill.replay ▶ 준비됨

0/0

설치

클라이언트 선택

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "terraform-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/antonbabenko/terraform-skill",
        "~/.claude/skills/terraform-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop → Settings → Developer → Edit Config 열기. 저장 후 앱 재시작.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "terraform-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/antonbabenko/terraform-skill",
        "~/.claude/skills/terraform-skill"
      ],
      "_inferred": true
    }
  }
}

Cursor는 Claude Desktop과 동일한 mcpServers 스키마 사용. 프로젝트 설정이 전역보다 우선.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "terraform-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/antonbabenko/terraform-skill",
        "~/.claude/skills/terraform-skill"
      ],
      "_inferred": true
    }
  }
}

Cline 사이드바의 MCP Servers 아이콘 클릭 후 "Edit Configuration" 선택.

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "terraform-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/antonbabenko/terraform-skill",
        "~/.claude/skills/terraform-skill"
      ],
      "_inferred": true
    }
  }
}

Claude Desktop과 같은 형식. Windsurf 재시작 후 적용.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "terraform-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/antonbabenko/terraform-skill",
        "~/.claude/skills/terraform-skill"
      ]
    }
  ]
}

Continue는 맵이 아닌 서버 오브젝트 배열 사용.

~/.config/zed/settings.json

{
  "context_servers": {
    "terraform-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/antonbabenko/terraform-skill",
          "~/.claude/skills/terraform-skill"
        ]
      }
    }
  }
}

context_servers에 추가. 저장 시 Zed가 핫 리로드.

claude mcp add terraform-skill -- git clone https://github.com/antonbabenko/terraform-skill ~/.claude/skills/terraform-skill

한 줄 명령. claude mcp list로 확인, claude mcp remove로 제거.

사용 사례

실전 활용법: terraform-skill

Scaffold a new Terraform module the idiomatic way

👤 Platform engineers publishing a reusable module ⏱ ~45 min intermediate

언제 쓸까: You're splitting out a module for internal or public reuse and want the structure right the first time.

흐름

State the module's purpose

Use the terraform-skill. Scaffold a module for an AWS ECS service with optional ALB and CloudWatch alarms.✓ 복사됨

→ Structure follows terraform-aws-modules conventions — main.tf, variables.tf, outputs.tf, versions.tf, README.md, examples/
Add tests

Recommend tests — native or Terratest? Apply the decision framework.✓ 복사됨

→ Reasoned choice and scaffolded test files

결과: A module that passes review on the first PR.

함정

Versioning too loose (~> vs specific) — Skill defaults to pinned minors for required_providers

함께 쓰기: github

Add a hardened CI pipeline to an existing Terraform repo

👤 DevOps / platform engineers ⏱ ~40 min advanced

언제 쓸까: Your repo lacks plan-on-PR, cost checks, or security scans.

사전 조건

GitHub or GitLab hosting — For the respective pipeline template

흐름

Request the pipeline

Use terraform-skill. Add GitHub Actions for plan-on-PR, Infracost, tfsec, and gated apply on main.✓ 복사됨

→ Workflow files with concurrency guards, OIDC auth, status checks
Security tune

Which Checkov / tfsec rules should we fail on vs warn?✓ 복사됨

→ Opinionated list with rationale

결과: A pipeline that blocks risky changes without slowing everyone down.

함정

Pipeline uses long-lived AWS keys — Skill prefers OIDC/role assumption, not static keys

함께 쓰기: github

Design a multi-environment layout without state explosions

👤 Teams scaling from dev/prod to dev/staging/prod/per-tenant ⏱ ~60 min advanced

언제 쓸까: You feel the pain of copy-pasted env folders or a monolith state.

흐름

Describe the envs

Use terraform-skill. We need dev/staging/prod plus per-tenant envs. What layout scales?✓ 복사됨

→ Recommendation with tradeoffs (workspaces vs dirs vs Terragrunt)
Plan the migration

We're currently on a single state. Sketch the migration.✓ 복사됨

→ State-move plan with risk callouts

결과: A layout you can defend in an ADR.

함정

Moving state without imports/breakdowns can destroy resources — The skill insists on terraform state mv / import steps, not delete-and-recreate

조합

다른 MCP와 조합해 10배 효율

terraform-skill + github

Skill produces module + workflow; GitHub MCP opens the PR

Scaffold the module, add the workflow, open a PR into our platform repo.✓ 복사됨

terraform-skill + aws

Cross-check the Terraform plan against live AWS state

Show me the plan, then diff against actual resources via the AWS MCP.✓ 복사됨

도구

이 MCP가 노출하는 것

도구	입력	언제 호출
Module scaffolding	module purpose + provider	Starting a new module
Test strategy advisor	module scope	Adding test coverage
CI pipeline templates (GHA / GitLab)	hosting choice	Setting up CI for a repo
Pattern compare	a snippet	Reviewing existing code

비용 및 제한

운영 비용

API 쿼터: None
호출당 토큰: 2-6k per session — moderate
금액: Free — skill is local
팁: Ask one focused question (testing / CI / layout) at a time.

보안

권한, 시크릿, 파급범위

자격 증명 저장: No credentials in the skill. Any provider creds belong in your env, not the generated code.

데이터 외부 송신: None from the skill itself

Generated CI pipelines may reference secret names — make sure you set those secrets in the repo settings before merging.

문제 해결

자주 발생하는 오류와 해결

Skill's suggestion conflicts with your org's style

Provide your .terraform-docs config and existing module as style anchors.

Recommended OIDC setup fails on assume-role

Check the trust policy's sub condition matches your branch/env.

대안

terraform-skill 다른 것과 비교

대안	언제 쓰나	단점/장점
Terragrunt-first skills	You're committed to Terragrunt	Less coverage here; Terragrunt workflows differ substantially
Cloud-provider-native IaC skills (aws-cdk, pulumi)	You're not on Terraform/OpenTofu	Different tool, different patterns

terraform-skill