terraform-patterns
This skill should be used when the user asks to "analyze Terraform modules", "scan IaC for security issues", "review Terraform configurations", "check infrastructure code for misconfigurations", or "audit cloud resources".
What this skill does
# Terraform Patterns > **Category:** Engineering > **Domain:** Infrastructure as Code ## Overview The **Terraform Patterns** skill provides automated analysis of Terraform configurations for module complexity, security misconfigurations, and infrastructure best practices. It catches open ports, public buckets, missing encryption, and overly permissive IAM policies before they reach production. ## Quick Start ```bash # Analyze Terraform module structure and complexity python scripts/tf_module_analyzer.py --path ./modules/vpc # Scan for security misconfigurations python scripts/tf_security_scanner.py --path ./environments/production # JSON output for CI pipelines python scripts/tf_security_scanner.py --path . --format json # Recursive analysis of all modules python scripts/tf_module_analyzer.py --path . --recursive ``` ## Tools Overview ### tf_module_analyzer.py Analyzes Terraform modules for complexity, structure, dependencies, and documentation quality. | Feature | Description | |---------|-------------| | Complexity scoring | Scores modules by resource count, variable count, nesting | | Dependency mapping | Maps module dependencies and data source usage | | Variable analysis | Checks for missing types, defaults, descriptions | | Output completeness | Validates output documentation and coverage | | Naming conventions | Checks resource and variable naming patterns | ### tf_security_scanner.py Scans Terraform configurations for security misconfigurations and compliance violations. | Feature | Description | |---------|-------------| | Open ports | Detects 0.0.0.0/0 CIDR in security groups | | Public access | Flags public S3 buckets, databases, instances | | Encryption gaps | Checks for missing encryption at rest and in transit | | IAM overreach | Identifies wildcard actions and overly broad policies | | Logging gaps | Verifies CloudTrail, flow logs, access logging | ## Workflows ### Security Review Workflow 1. **Scan** - Run tf_security_scanner.py across all environments 2. **Triage** - Prioritize critical findings (public data, open access) 3. **Remediate** - Apply recommended fixes per finding 4. **Verify** - Re-scan to confirm fixes resolved issues 5. **Gate** - Add scanner to PR checks for continuous enforcement ### Module Quality Workflow 1. **Analyze** - Run tf_module_analyzer.py on each module 2. **Score** - Review complexity scores, identify modules over threshold 3. **Refactor** - Break down modules scoring above 70/100 complexity 4. **Document** - Fill in missing variable and output descriptions 5. **Standardize** - Apply consistent naming and file organization ### CI Integration ```bash # Security gate python scripts/tf_security_scanner.py --path . --format json --min-severity high if [ $? -ne 0 ]; then echo "Security scan failed - blocking merge" exit 1 fi # Module quality check python scripts/tf_module_analyzer.py --path . --recursive --format json ``` ## Reference Documentation - [Terraform Patterns](references/terraform-patterns.md) - Module design, state management, naming conventions ## Common Patterns Quick Reference ### Module Structure ``` modules/vpc/ main.tf # Primary resources variables.tf # Input variables with descriptions outputs.tf # Module outputs versions.tf # Required providers and versions locals.tf # Local values and computed expressions ``` ### Security Checklist | Resource | Check | Rule | |----------|-------|------| | Security Groups | No 0.0.0.0/0 ingress | Restrict to known CIDRs | | S3 Buckets | No public ACLs | Use bucket policies instead | | RDS | No public access | Set publicly_accessible = false | | EBS/S3/RDS | Encryption enabled | Add encryption configuration | | IAM | No wildcard actions | Use least-privilege policies | | CloudTrail | Enabled in all regions | is_multi_region_trail = true | | VPC | Flow logs enabled | Create flow log resources | ### Complexity Scoring | Score | Rating | Action | |-------|--------|--------| | 0-30 | Low | No action needed | | 31-60 | Medium | Consider splitting | | 61-80 | High | Should refactor | | 81-100 | Critical | Must refactor |
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.