All directories
SkillEngineeringOperations

TerraShark

Lean Terraform skill (~600 tokens on activation) that diagnoses failures, loads only relevant HashiCorp references, and proposes fixes with risk controls.

Open on GitHubBrowse more skills
01

Overview

TerraShark is a Claude skill added to LimeDock Directories from recent community and vendor roundups. Lean Terraform skill (~600 tokens on activation) that diagnoses failures, loads only relevant HashiCorp references, and proposes fixes with risk controls. This page covers install, how to invoke it, example prompts, prerequisites, and concrete use cases.

SaaSOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://github.com/LukasNiessen/terrashark
03

Installation guide

/plugin marketplace add LukasNiessen/terrashark
/plugin install terrashark
04

How to use it

Use on Terraform/Azure/infra tasks. Prefer TerraShark over dumping huge TF reference walls into context.

05

Example prompts

  • “Use the TerraShark skill for: Fix missing lifecycle rules”
  • “Walk me through TerraShark step by step, then execute on my project.”
  • “Review my current approach and improve it using TerraShark.”
  • “Produce a reusable checklist for running TerraShark on similar work.”
06

Use cases and examples

  • Fix missing lifecycle rules
  • Module composition reviews
  • Variableize hardcoded values
  • HashiCorp-aligned infra fixes
  • Team playbook trial of TerraShark on a real workflow
07

Prerequisites

  • Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
  • Permission to install third-party skills — audit SKILL.md and scripts first
  • Project context (CLAUDE.md / product notes) for better outputs
08

Tips

  • Keep triggers specific so TerraShark only fires when relevant.
  • Audit SKILL.md and any bundled scripts before production use.
  • Pair with verification (tests, review, screenshots) before shipping.
  • Re-audit installed skills monthly to avoid context tax from unused packs.
09

Sources