Does it automatically document the infrastructure?

Yes, it provides structured commands like /infra-doc and /adr to help generate factual records and Architecture Decision Records based on the evidence found during investigation.

What is Infrastructure Archaeology?

Infrastructure Archaeology is the process of systematically investigating and documenting inherited cloud resources to understand their original intent, current state, and potential risks.

How does this skill handle company mergers?

It specifically looks for 'merge artifacts' such as duplicate resources, overlapping network CIDRs, and redundant logging pipelines that typically occur when separate infrastructures are combined.

Which cloud platforms does this skill support?

This skill provides specific investigation patterns for AWS (including VPC, RDS, and Redshift), Azure (Resource Groups and NSGs), and Kubernetes (specifically kOps and EKS).

Infrastructure Archaeology

Name: Infrastructure Archaeology
Author: simplycycling

bysimplycycling

0•

Cloud Infrastructure

Investigates, interprets, and documents legacy or inherited cloud infrastructure to recover missing design context and intent.

Infrastructure Archaeology provides a forensic framework for engineers to navigate and document 'mystery' infrastructure, making it indispensable during company mergers or handovers. It guides Claude through a systematic investigation of AWS, Azure, and Kubernetes environments—moving from raw resource evidence to inferred hypotheses. The skill helps identify why specific configurations exist, maps out complex networking like kOps-managed clusters and VPC peering, and surfaces hidden technical debt. By categorizing findings as factual or inferred, it enables teams to build a reliable source of truth for legacy systems that lack traditional documentation.

Key Features

01Automated identification of 'merge artifacts' like overlapping CIDRs or redundant RDS instances

02Multi-cloud support with specific patterns for AWS, Azure, and Kubernetes

03Four-layer investigation framework: Inventory, Function, Intent, and Risk

04Standardized tagging system for legacy debt, undocumented resources, and inferred decisions

05Specialized kOps state-store analysis for EKS migration readiness

060 GitHub stars

Use Cases

01Mapping out undocumented cloud resources after a company merger or acquisition

02Preparing for cloud migrations by auditing kOps-managed clusters for configuration drift

03Reverse-engineering the intent behind complex legacy Kubernetes RBAC and networking

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add simplycycling/dotfiles infra-archaeology

For use in Claude.ai and ChatGPT

Key Features

01Automated identification of 'merge artifacts' like overlapping CIDRs or redundant RDS instances

02Multi-cloud support with specific patterns for AWS, Azure, and Kubernetes

03Four-layer investigation framework: Inventory, Function, Intent, and Risk

04Standardized tagging system for legacy debt, undocumented resources, and inferred decisions

05Specialized kOps state-store analysis for EKS migration readiness

060 GitHub stars

Use Cases

01Mapping out undocumented cloud resources after a company merger or acquisition

02Preparing for cloud migrations by auditing kOps-managed clusters for configuration drift

03Reverse-engineering the intent behind complex legacy Kubernetes RBAC and networking