القائمة
Trace a public endpoint through App Gateway, APIM, and AKS using harvested subscription data.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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.
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 | route-trace |
| description | Trace a public endpoint through App Gateway, APIM, and AKS using harvested subscription data. |
Trace a route using the DB-backed trace API in web/app.py.
curl -sf http://127.0.0.1:9000 > /dev/null || echo "Server not running"
appgw_routing_rules, apim_api_routes, apim_backends, and aks_routes exist.Trace an endpoint directly:
curl -s "http://127.0.0.1:9000/api/cloud/route-trace?sub=<subscription_id>&endpoint=https://events.mydomain.co.uk" | jq
Or, when the subscription id is already known:
curl -s "http://127.0.0.1:9000/api/subscriptions/<subscription_id>/trace-route?endpoint=https://events.mydomain.co.uk" | jq
resolved_chain — the exact hop list, typically:
internet → listener → appgw → backend_pool → apim_service → apim_api → apim_backend → aks_ingress → aks_service → aks_deployment → aks_clustermermaid — a ready-to-render flowchart for the resolved routematches — candidate subscription/route matches when multiple routes existUse this skill when you want to:
If the returned chain does not match the rendered diagram, use:
subscription-diagram-check to audit the UI renderingdiagram-review to inspect the broader diagram generation pipeline