Menu

Individual skill

techstack-infra

0upvotes

Infrastructure tech-stack identification — cloud providers, CDN/WAF, DNS services, TLS/CT, DevOps tooling, plus asset discovery (domains, subdomains, IPs).

skills/techstack-identification/infra/SKILL.md

Read pinned source

Source commit 95fdc128af4ca1ae16b3226f9430f1bad97b0656

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
611
Repository last updated
Jul 29, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Infrastructure Tech-Stack Identification

## Scope

Identify the hosting and operational layer: cloud providers (AWS/GCP/Azure/DO/Linode/Vultr), PaaS (Heroku/Vercel/Netlify/Render/Railway/Fly), CDN (Cloudflare/Akamai/Fastly/CloudFront/Azure CDN), WAF (Imperva/Sucuri/F5/Fortinet), DNS provider, certificate authority, DevOps tooling (CI/CD, IaC, containers, orchestration), and the asset inventory (root domain, subdomains, IPs, certificates) that the rest of the engagement consumes.

## Signals (input)

- IP attribution (cloud IP ranges, ASN, WHOIS)
- DNS records: A, AAAA, MX, TXT, NS, CNAME, SRV
- TLS certificate metadata (issuer, SAN, validity, JARM)
- CT logs (crt.sh)
- HTTP headers tagging cloud/CDN/WAF
- Repository config files (`*.tf`, `Dockerfile`, `.github/workflows/*`, `Chart.yaml`, etc.)
Back to top