⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

terrashark

lukasniessen@lukasniessen⭐ 703 stars· last commit 2mo ago· 0 open issues

Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps. Use when generating, reviewing, refactoring, or migrating IaC and when building delivery/testing pipelines.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐ 703 on GitHubGitHub ↗

Popular

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Terraform Skill for Claude Code, Codex, Antigravity, and Gemini CLI: TerraShark

Claude Skill Codex Skill Gemini Skill Antigravity Skill License: MIT GitHub stars

The #1 Terraform skill for Claude Code and Codex, measured by GitHub stars.

Fixes Hallucinations.

LLMs hallucinate a lot when it comes to Terraform. This skill fixes it. It includes best practices for Terraform and OpenTofu - good, bad, and neutral examples so the AI avoids common mistakes. Using TerraShark, the AI keeps proven practices in mind, eliminates hallucinations, and defaults to modular, reusable, security-first design.

Very Token-Efficient.

Most Terraform skills dump huge text-of-walls onto the agent and burn expensive tokens - with no upside. LLMs don't need the entire Terraform docs again. TerraShark was aggressively de-duplicated and optimized for maximum quality per token.

Based on HashiCorp's Official Best Practices.

TerraShark is primarily based on HashiCorp official recommended practices. When guidance conflicts, it prioritizes HashiCorp's recommendations.


Quick Start • Why TerraShark? • Token Strategy • What's Included • How It Works • Sponsor • Philosophy


⚡ 2 min Quickstart

Option 1: Clone

macOS / Linux:

git clone https://github.com/LukasNiessen/terrashark.git ~/.claude/skills/terrashark

Windows (Powershell):

git clone https://github.com/LukasNiessen/terrashark.git "$env:USERPROFILE\.claude\skills\terrashark"

Windows (Command Prompt):

git clone https://github.com/LukasNiessen/terrashark.git "%USERPROFILE%\.claude\skills\terrashark"

That's it. Claude Code auto-discovers skills in ~/.claude/skills/ - no restart needed.

Option 2: Marketplace

Claude Code has a built-in plugin system with marketplace support. Instead of cloning manually, you can add TerraShark's marketplace and install directly from the CLI:

/plugin marketplace add LukasNiessen/terrashark
/plugin install terrashark

Or use the interactive plugin manager - run /plugin, switch to the Discover tab, and install from there. The marketplace reads the .claude-plugin/marketplace.json in this repo to register TerraShark as an installable plugin.

Option 3: Codex

Codex has no global skill system - setup is per-project. Clone TerraShark into your repo and reference it from your AGENTS.md:

# Clone into your project root
git clone https://github.com/LukasNiessen/terrashark.git .terrashark

Then add to your AGENTS.md (or create one in the repo root):

## Terraform

When working with Terraform or OpenTofu, follow the workflow in `.terrashark/SKILL.md`.
Load references from `.terrashark/references/` as needed.

Option 4: Antigravity

macOS / Linux:

git clone https://github.com/LukasNiessen/terrashark.git ~/.gemini/antigravity/skills/terrashark

Windows (PowerShell):

git clone https://github.com/LukasNiessen/terrashark.git "$env:USERPROFILE\.gemini\antigravity\skills\terrashark"

Antigravity auto-discovers skills in the skills directory — no restart needed.

Option 5: Gemini CLI

Gemini CLI discovers skills in several standard locations.

Global Installation (All Workspaces):

git clone https://github.com/LukasNiessen/terrashark.git ~/.gemini/skills/terrashark

Local Installation (Current Workspace):

git clone https://github.com/LukasNiessen/terrashark.git .gemini/skills/terrashark

Gemini CLI auto-discovers skills in these directories. Run /skills list in the CLI to verify.

That's it!

Done. Now ask Claude Code / Codex / Antigravity / Gemini CLI any Terraform question. TerraShark responses follow the 7-step failure-mode workflow and include an output contract with assumptions, tradeoffs, and rollback notes.

Invoke explicitly:

/terrashark Create a multi-region S3 module with replication
/terrashark Refactor our EKS stack into separate state files per environment, add moved blocks to avoid recreation, set up a GitHub Actions pipeline with plan on PR and gated apply on merge, and wire in Checkov for compliance scanning

Or just ask naturally - TerraShark activates automatically for any Terraform/OpenTofu task:

Review my main.tf for security issues
Migrate this module from count to for_each

🎬 Demo

https://github.com/user-attachments/assets/2bc4c9ff-9f54-4a49-8bf0-5cfc0f26dec6

📊 Library Comparison

Here's how TerraShark compares to other Terraform and OpenTofu agent skills:

FeatureTerraSharkAnton Babenko terraform-skillterraform-patterns
Core Architecture✅ Failure-mode workflow⚠️ Static reference manual⚠️ Pattern checklist
SKILL.md Activation Cost✅ ~600 tokens⚠️ ~4,400 tokens⚠️ Single broad reference
Reference Granularity✅ 19 focused files⚠️ 6 large files❌ No focused reference library
Token Burn Per Query✅ Low (load 1-2 small refs)⚠️ High for deep references⚠️ Loads broad guidance
Diagnoses Before Generating✅ Step 2 requires diagnosis❌ No❌ No
Hallucination Prevention✅ Core design goal⚠️ Indirect via best practices⚠️ Indirect via patterns
Output Contract✅ Assumptions, tradeoffs, rollback❌ No❌ No
Failure-Mode Coverage✅ Identity, secrets, blast radius, CI, compliance⚠️ General state/security advice⚠️ General anti-pattern summary
Migration Playbooks✅ 5 dedicated playbooks⚠️ Partial inline snippets⚠️ Import and moved-block notes
Good/Bad/Neutral Examples✅ 3 dedicated files⚠️ Inline DO/DON'T examples⚠️ Inline BAD/GOOD snippets
Do/Don't Checklist✅ Dedicated file⚠️ Inline only⚠️ Inline only
Compliance Framework Mapping✅ ISO 27001, SOC 2, FedRAMP, GDPR, PCI DSS, HIPAA⚠️ Scanner-oriented guidance❌ No
Trusted Module Awareness✅ AWS, Azure, GCP, OCI, IBM loaded condi

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • SKILL.md3.3 KBupstream ↗
    ---
    name: terrashark
    description: "Prevent Terraform/OpenTofu hallucinations by diagnosing and fixing failure modes: identity churn, secret exposure, blast-radius mistakes, CI drift, and compliance gate gaps. Use when generating, reviewing, refactoring, or migrating IaC and when building delivery/testing pipelines."
    ---
    
    # Terrashark: Failure-Mode Workflow for Terraform/OpenTofu
    
    Run this workflow top to bottom.
    
    ## 1) Capture execution context
    
    Record before writing code:
    - runtime (`terraform` or `tofu`) and exact version
    - provider(s), target platform, and state backend
    - execution path (local CLI, CI, HCP Terraform/TFE, Atlantis)
    - environment criticality (dev/shared/prod)
    
    If unknown, state assumptions explicitly.
    
    ## 2) Diagnose likely failure mode(s)
    
    Select one or more based on user intent and risk:
    - identity churn: resource addressing instability, refactor breakage
    - secret exposure: secrets in state, logs, defaults, artifacts
    - blast radius: oversized stacks, weak boundaries, unsafe applies
    - CI drift: version mismatch, unreviewed applies, missing artifacts
    - compliance gate gaps: missing policies/approvals/audit controls
    
    ## 3) Load only the relevant reference file(s)
    
    Primary references:
    - `references/identity-churn.md`
    - `references/secret-exposure.md`
    - `references/blast-radius.md`
    - `references/ci-drift.md`
    - `references/compliance-gates.md`
    
    Supplemental references (only when needed):
    - `references/testing-matrix.md`
    - `references/quick-ops.md`
    - `references/examples-good.md`
    - `references/examples-bad.md`
    - `references/examples-neutral.md`
    - `references/coding-standards.md`
    - `references/module-architecture.md`
    - `references/ci-delivery-patterns.md`
    - `references/security-and-governance.md`
    - `references/do-dont-patterns.md`
    - `references/mcp-integration.md`
    
    Conditional references (CRR; load only on detected signals):
    - `references/conditional/backend-state-safety.md` (backend is `s3`, `azurerm`, `gcs`, `remote`, `cloud`, `pg`, `consul`, or `local`, or task mentions backend migration, locking, state backup, or restore)
    - `references/conditional/trusted-modules.md` (provider is `aws`, `azurerm`, `google`, `oci`, or `ibm`)
    
    Do not load multiple conditional references unless the task spans multiple detected backends, providers, or tools.
    
    ## 4) Propose fix path with explicit risk controls
    
    For each fix, include:
    - why this addresses the failure mode
    - what could still go wrong
    - guardrails (tests, approvals, rollback)
    
    ## 5) Generate implementation artifacts
    
    When applicable, output:
    - HCL changes (typed vars, stable keys, bounded versions)
    - migration blocks (`moved`, import strategy)
    - CI pipeline updates (plan/apply separation, artifacts, policy checks)
    - compliance controls (approvals, policy rules, evidence paths)
    
    When a trusted registry module covers the requested resource and the user has not asked for raw HCL, default to that module with an exact `version` pin (see `references/conditional/trusted-modules.md`).
    
    ## 6) Validate before finalize
    
    Always provide command sequence tailored to runtime and risk tier.
    Never recommend direct production apply without reviewed plan and approval.
    
    ## 7) Output contract
    
    Return:
    - assumptions and version floor
    - selected failure mode(s)
    - chosen remediation and tradeoffs
    - validation/test plan
    - rollback/recovery notes for destructive-impact changes
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/lukasniessen-terrashark.md

// REPO STATS

703 stars
0 open issues
Last commit: 2mo ago