Menu
Generate per-resource-type cloud summaries (Key Vault, Storage Account, AKS, etc.) and persist them to the DB for the web app after triage completes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Trace a public endpoint through App Gateway, APIM, and AKS using harvested subscription data.
On-demand Playwright audit of a subscription's rendered React Flow diagrams - verifies the UI matches harvested Azure reality using screenshots, DOM checks, interaction tests, and diagram-to-asset comparison.
Run Triage-Saurus diagram review (screenshots, threat-model smells, and before/after report).
Promote validated learnings from a completed experiment — create detection rules, update strategy JSON, and update agent instructions for future experiments.
Validate generated architecture diagrams for hierarchy issues, missing internet ingress, network segmentation gaps, and missing components.
Run two-phase repo context discovery — automated baseline (Phase 1) then intelligent code analysis (Phase 2) — to build architecture diagrams and inform scan scope.
| name | cloud-summary |
| description | Generate per-resource-type cloud summaries (Key Vault, Storage Account, AKS, etc.) and persist them to the DB for the web app after triage completes. |
Generate cloud resource summaries grouped by resource type after Phase 5 (skeptic reviews) is complete.
Full agent guidance is in Agents/CloudSummaryAgent.md.
Phase 5 (skeptic reviews) must be complete and findings must have final scores. Verify:
python3 Scripts/Experiments/triage_experiment.py resume
Summaries are DB-first — persist each section via:
python3 Scripts/Persist/persist_section.py \
--repo <RepoName> \
--experiment <experiment_id> \
--key <section_key> \
--title "<Tab Label>" \
--html "<section HTML>" \
--generated-by CloudSummaryAgent
| Key | Tab label |
|---|---|
tldr | TL;DR |
risks | Risks |
architecture | Architecture |
auth | Authentication |
network | Network |
ingress | Ingress |
egress | Egress |
containers | Containers |
kubernetes | Kubernetes |
cicd | CI/CD |
dependencies | Dependencies |
Each summary must follow this format:
flowchart TB, key interactions of the resource type; no fill: inline styles; use <br/> not \n## Findings section — findings in priority order with severity emoji, label, score, and markdown link:
- 🔴 **Critical 9/10:** [Public Blob with Credentials](../Findings/...)
- 🟠 **High 7/10:** [Storage Account Without HTTPS Enforcement](../Findings/...)
Settings/Styling.md for formatting.python3 Scripts/Validate/validate_markdown.py --path Summary/Cloud/<Provider>
If DB persistence fails, write to:
Summary/Cloud/<Provider>/<ResourceType>.md (e.g., Summary/Cloud/AWS/EKS.md)
Top-level Summary/Cloud/ is for Architecture_*.md files only.
Full output format rules, section key registry, Mermaid diagram constraints:
Agents/CloudSummaryAgent.md