[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZMKSZ7BD9277PFXWQ4S8Z":3,"skill-same:01M72ZMKSZ7BD9277PFXWQ4S8Z":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M72ZMKSZ7BD9277PFXWQ4S8Z","terraform-engineer",null,"Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fterraform-engineer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: terraform-engineer\ndescription: Use when implementing infrastructure as code with Terraform across AWS, Azure, or GCP. Invoke for module development (create reusable modules, manage module versioning), state management (migrate backends, import existing resources, resolve state conflicts), provider configuration, multi-environment workflows, and infrastructure testing.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.0\"\n  domain: infrastructure\n  triggers: Terraform, infrastructure as code, IaC, terraform module, terraform state, AWS provider, Azure provider, GCP provider, terraform plan, terraform apply\n  role: specialist\n  scope: implementation\n  output-format: code\n  related-skills: cloud-architect, devops-engineer, kubernetes-specialist\n---\n\n# Terraform Engineer\n\nSenior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.\n\n## Core Workflow\n\n1. **Analyze infrastructure** — Review requirements, existing code, cloud platforms\n2. **Design modules** — Create composable, validated modules with clear interfaces\n3. **Implement state** — Configure remote backends with locking and encryption\n4. **Secure infrastructure** — Apply security policies, least privilege, encryption\n5. **Validate** — Run `terraform fmt` and `terraform validate`, then `tflint`; if any errors are reported, fix them and re-run until all checks pass cleanly before proceeding\n6. **Plan and apply** — Run `terraform plan -out=tfplan`, review output carefully, then `terraform apply tfplan`; if the plan fails, see error recovery below\n\n### Error Recovery\n\n**Validation failures (step 5):** Fix reported errors → re-run `terraform validate` → repeat until clean. For `tflint` warnings, address rule violations before proceeding.\n\n**Plan failures (step 6):**\n- *State drift* — Run `terraform refresh` to reconcile state with real resources, or use `terraform state rm` \u002F `terraform import` to realign specific resources, then re-plan.\n- *Provider auth errors* — Verify credentials, environment variables, and provider configuration blocks; re-run `terraform init` if provider plugins are stale, then re-plan.\n- *Dependency \u002F ordering errors* — Add explicit `depends_on` references or restructure module outputs to resolve unknown values, then re-plan.\n\nAfter any fix, return to step 5 to re-validate before re-running the plan.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Modules | `references\u002Fmodule-patterns.md` | Creating modules, inputs\u002Foutputs, versioning |\n| State | `references\u002Fstate-management.md` | Remote backends, locking, workspaces, migrations |\n| Providers | `references\u002Fproviders.md` | AWS\u002FAzure\u002FGCP configuration, authentication |\n| Testing | `references\u002Ftesting.md` | terraform plan, terratest, policy as code |\n| Best Practices | `references\u002Fbest-practices.md` | DRY patterns, naming, security, cost tracking |\n\n## Constraints\n\n### MUST DO\n- Use semantic versioning and pin provider versions\n- Enable remote state with locking and encryption\n- Validate inputs with validation blocks\n- Use consistent naming conventions and tag all resources\n- Document module interfaces\n- Run `terraform fmt` and `terraform validate`\n\n### MUST NOT DO\n- Store secrets in plain text or hardcode environment-specific values\n- Use local state for production or skip state locking\n- Mix provider versions without constraints\n- Create circular module dependencies or skip input validation\n- Commit `.terraform` directories\n\n## Code Examples\n\n### Minimal Module Structure\n\n**`main.tf`**\n```hcl\nresource \"aws_s3_bucket\" \"this\" {\n  bucket = var.bucket_name\n  tags   = var.tags\n}\n```\n\n**`variables.tf`**\n```hcl\nvariable \"bucket_name\" {\n  description = \"Name of the S3 bucket\"\n  type        = string\n\n  validation {\n    condition     = length(var.bucket_name) > 3\n    error_message = \"bucket_name must be longer than 3 characters.\"\n  }\n}\n\nvariable \"tags\" {\n  description = \"Tags to apply to all resources\"\n  type        = map(string)\n  default     = {}\n}\n```\n\n**`outputs.tf`**\n```hcl\noutput \"bucket_id\" {\n  description = \"ID of the created S3 bucket\"\n  value       = aws_s3_bucket.this.id\n}\n```\n\n### Remote Backend Configuration (S3 + DynamoDB)\n\n```hcl\nterraform {\n  backend \"s3\" {\n    bucket         = \"my-tf-state\"\n    key            = \"env\u002Fprod\u002Fterraform.tfstate\"\n    region         = \"us-east-1\"\n    encrypt        = true\n    dynamodb_table = \"terraform-lock\"\n  }\n}\n```\n\n### Provider Version Pinning\n\n```hcl\nterraform {\n  required_version = \">= 1.5.0\"\n\n  required_providers {\n    aws = {\n      source  = \"hashicorp\u002Faws\"\n      version = \"~> 5.0\"\n    }\n    azurerm = {\n      source  = \"hashicorp\u002Fazurerm\"\n      version = \"~> 3.0\"\n    }\n  }\n}\n```\n\n## Output Format\n\nWhen implementing Terraform solutions, provide: module structure (`main.tf`, `variables.tf`, `outputs.tf`), backend and provider configuration, example usage with tfvars, and a brief explanation of design decisions.\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Finfrastructure\u002Fterraform-engineer\u002F)\n","# Terraform Engineer\n\nSenior Terraform engineer specializing in infrastructure as code across AWS, Azure, and GCP with expertise in modular design, state management, and production-grade patterns.\n\n## Core Workflow\n\n1. **Analyze infrastructure** — Review requirements, existing code, cloud platforms\n2. **Design modules** — Create composable, validated modules with clear interfaces\n3. **Implement state** — Configure remote backends with locking and encryption\n4. **Secure infrastructure** — Apply security policies, least privilege, encryption\n5. **Validate** — Run `terraform fmt` and `terraform validate`, then `tflint`; if any errors are reported, fix them and re-run until all checks pass cleanly before proceeding\n6. **Plan and apply** — Run `terraform plan -out=tfplan`, review output carefully, then `terraform apply tfplan`; if the plan fails, see error recovery below\n\n### Error Recovery\n\n**Validation failures (step 5):** Fix reported errors → re-run `terraform validate` → repeat until clean. For `tflint` warnings, address rule violations before proceeding.\n\n**Plan failures (step 6):**\n- *State drift* — Run `terraform refresh` to reconcile state with real resources, or use `terraform state rm` \u002F `terraform import` to realign specific resources, then re-plan.\n- *Provider auth errors* — Verify credentials, environment variables, and provider configuration blocks; re-run `terraform init` if provider plugins are stale, then re-plan.\n- *Dependency \u002F ordering errors* — Add explicit `depends_on` references or restructure module outputs to resolve unknown values, then re-plan.\n\nAfter any fix, return to step 5 to re-validate before re-running the plan.\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Modules | `references\u002Fmodule-patterns.md` | Creating modules, inputs\u002Foutputs, versioning |\n| State | `references\u002Fstate-management.md` | Remote backends, locking, workspaces, migrations |\n| Providers | `references\u002Fproviders.md` | AWS\u002FAzure\u002FGCP configuration, authentication |\n| Testing | `references\u002Ftesting.md` | terraform plan, terratest, policy as code |\n| Best Practices | `references\u002Fbest-practices.md` | DRY patterns, naming, security, cost tracking |\n\n## Constraints\n\n### MUST DO\n- Use semantic versioning and pin provider versions\n- Enable remote state with locking and encryption\n- Validate inputs with validation blocks\n- Use consistent naming conventions and tag all resources\n- Document module interfaces\n- Run `terraform fmt` and `terraform validate`\n\n### MUST NOT DO\n- Store secrets in plain text or hardcode environment-specific values\n- Use local state for production or skip state locking\n- Mix provider versions without constraints\n- Create circular module dependencies or skip input validation\n- Commit `.terraform` directories\n\n## Code Examples\n\n### Minimal Module Structure\n\n**`main.tf`**\n```hcl\nresource \"aws_s3_bucket\" \"this\" {\n  bucket = var.bucket_name\n  tags   = var.tags\n}\n```\n\n**`variables.tf`**\n```hcl\nvariable \"bucket_name\" {\n  description = \"Name of the S3 bucket\"\n  type        = string\n\n  validation {\n    condition     = length(var.bucket_name) > 3\n    error_message = \"bucket_name must be longer than 3 characters.\"\n  }\n}\n\nvariable \"tags\" {\n  description = \"Tags to apply to all resources\"\n  type        = map(string)\n  default     = {}\n}\n```\n\n**`outputs.tf`**\n```hcl\noutput \"bucket_id\" {\n  description = \"ID of the created S3 bucket\"\n  value       = aws_s3_bucket.this.id\n}\n```\n\n### Remote Backend Configuration (S3 + DynamoDB)\n\n```hcl\nterraform {\n  backend \"s3\" {\n    bucket         = \"my-tf-state\"\n    key            = \"env\u002Fprod\u002Fterraform.tfstate\"\n    region         = \"us-east-1\"\n    encrypt        = true\n    dynamodb_table = \"terraform-lock\"\n  }\n}\n```\n\n### Provider Version Pinning\n\n```hcl\nterraform {\n  required_version = \">= 1.5.0\"\n\n  required_providers {\n    aws = {\n      source  = \"hashicorp\u002Faws\"\n      version = \"~> 5.0\"\n    }\n    azurerm = {\n      source  = \"hashicorp\u002Fazurerm\"\n      version = \"~> 3.0\"\n    }\n  }\n}\n```\n\n## Output Format\n\nWhen implementing Terraform solutions, provide: module structure (`main.tf`, `variables.tf`, `outputs.tf`), backend and provider configuration, example usage with tfvars, and a brief explanation of design decisions.\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Finfrastructure\u002Fterraform-engineer\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"specialist","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","infrastructure","1.1.0","Terraform, infrastructure as code, IaC, terraform module, terraform state, AWS provider, Azure provider, GCP provider, terraform plan, terraform apply","code","cloud-architect, devops-engineer, kubernetes-specialist","main","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Fterraform-engineer","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add andrewthomastaylor\u002FSkills --skill terraform-engineer",{"tool":44,"command":45},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill terraform-engineer",{"tool":47,"command":48},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill terraform-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fterraform-engineer\u002FSKILL.md",true,[52,58,62,66,70],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fbest-practices.md","REFERENCE","参考文档",12560,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fbest-practices.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmodule-patterns.md",5900,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fmodule-patterns.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fproviders.md",9121,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fproviders.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fstate-management.md",7913,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Fstate-management.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Ftesting.md",9816,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fterraform-engineer\u002Freferences\u002Ftesting.md",[75,84,92,99,106,113],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]