More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Repair Terraform Import State Address Alias Collision

    1

    Prevent accidental ownership overlap after importing cloud objects into renamed module addresses

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair Terraform Import State Address Alias Collision

    Repair Terraform Import State Address Alias Collision

    Example session with this skill installed

    A bucket appears in state twice after module refactor and import, while live configuration has one object.

    Available sources: terraform state list and import blocks (partial excerpts only). Additional evidence requested: module moved directives, plan JSON. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.

    • Read your context and instructions
    • Compiled the repair terraform import

    Repair Terraform Import State Address Alias Collision — EVIDENCE-LIMITED REVIEW

    Scenario received

    A bucket appears in state twice after module refactor and import, while live configuration has one object.

    Source register

    • S1: terraform state list — partial extract described, independent verification not provided.
    • S2: import blocks — partial extract described, independent verification not provided.
    • S3: module moved directives — NOT PROVIDED; validation pending.
    • S4: plan JSON — NOT PROVIDED; validation pending.

    Case-specific checks

    1. resolve resource identity against remote IDs — NEEDS VERIFICATION against S1/S2 and missing sources.
    2. trace moved and imported address collisions — NEEDS VERIFICATION against S1/S2 and missing sources.
    3. check state locking and ownership — NEEDS VERIFICATION against S1/S2 and missing sources.
    4. prepare no-destroy state migration validation — NEEDS VERIFICATION against S1/S2 and missing sources.

    Deliverables and review gates

    • address-to-resource map: DRAFT ONLY; do not infer unsupported outcomes.
    • duplicate state diagnosis: DRAFT ONLY; do not infer unsupported outcomes.
    • reviewed import repair steps: DRAFT ONLY; do not infer unsupported outcomes.

    Preliminary conclusion

    INCOMPLETE / REVIEW REQUIRED. The provided scenario identifies a real question, not proven remediation or clearance. Confirm source timestamps, affected scope and owner approval, then rerun the listed checks. No external system was accessed or changed.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Repair Terraform Import State Address Alias Collision is a ToolForge Labs Cursor Skill workflow. Prevent accidental ownership overlap after importing cloud objects into renamed module addresses.

    What this skill checks

    1. resolve resource identity against remote IDs.
    2. trace moved and imported address collisions.
    3. check state locking and ownership.
    4. prepare no-destroy state migration validation.

    What to provide

    • terraform state list.
    • import blocks.
    • module moved directives.
    • plan JSON.

    Deliverables

    • address-to-resource map.
    • duplicate state diagnosis.
    • reviewed import repair steps.

    Evidence policy Only supplied, authorized evidence is used. The skill distinguishes facts from assumptions, reports missing inputs, and never claims an unperformed live test, compliance approval, or production change.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 25 days ago

    Permissions

    Read Files

    Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.

    Listed25 days ago
    Updated9 days ago

    What's inside

    Frequently Asked Questions

    This skill identifies scenarios where a single cloud resource is incorrectly tracked under multiple Terraform addresses, a common issue during module refactors. It prevents the "Resource Already Exists" error and accidental deletions by generating a safe, verified migration path.

    Yes, it is fully compatible with both HashiCorp Terraform and OpenTofu. It utilizes standard JSON outputs from their respective CLIs to perform state analysis and collision detection.

    This skill acts as a diagnostic and planning layer; it analyzes your state and plan logs to provide repair steps but does not directly access or modify your live infrastructure or state files. You maintain full control by reviewing and executing the proposed commands manually.

    You will need to provide the skill with specific text or file outputs, such as `terraform state list` and `terraform plan -json`. These provide the necessary evidence for the skill to map resource identities and find overlapping aliases.

    Unlike generic prompts, this skill uses a specialized four-step verification process that links every proposed action to a confirmed resource ID. This prevents the common LLM mistake of suggesting destructive 'state rm' commands without verifying resource ownership first.

    You receive the specialized agent skill designed to resolve state collisions, along with a guide on how to export the required JSON files from your CLI. The purchase includes any future logic updates or optimizations released for this specific skill.

    New in DevOps & Cloud