Agent skill · design visual · aiskillstore
arch-view
This skill should be used when the user asks to "generate architecture view", "show service dependency graph", "map request flows", "show event topology", "group services by domain", "visualize architecture", or mentions cross-repository architecture analysis, service mapping, or architectural visualization.
Why this skill is useful
Generates detailed architectural visualizations and service dependency graphs that the AI wouldn't reliably create on its own.
What it needs
Requires gh installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Architecture View Generate cross-repository architectural views by aggregating catalog-info.yaml metadata from all repositories using parallel subagents. Purpose Create visual architectural representations (Mermaid diagrams, markdown tables) that show how services fit together, how requests flow through gateways, how events propagate, and how services group by domain/team. When to Use Trigger this skill when: User asks to "show service dependency graph" or "map the architecture" User wants to understand "how services connect" User asks about "request flows" or "event topology" User wants to "group services by domain/team" User mentions "cross-repo architecture" or "system architecture" Workflow Phase 1: Discover Repositories Find all repositories to analyze: 1. Check repos/ directory - Local cloned repositories 2. Optionally fetch from GitHub - Use gh repo list Astrabit-CPT for full list 3. Filter for active repos - Skip archived or template repos Phase 2: Parallel Metadata Collection Use subagents IN PARALLEL to read each repository's catalog-info.yaml: Parallel processing strategy: Launch 5-10 subagents simultaneously Collect all results Handle missing metadata gracefully (skip or note as missing) Phase 3: Aggregate and Build Model Combine all metadata into a unified model: Phase 4: Generate Requested View Based on user request, generate the appropriate view: View Command/Trigger Output ------ ----------------- -------- Service Dependency Graph "dependency graph", "show dependencies" Mermaid graph Request Flow Maps "request flows", "how requests flow" Mermaid flowchart Event Topology "event topology", "event map" Mermaid graph Service Groupings "group services", "services by domain" Markdown tables Full Architecture "architecture view", "full architecture" All views combined View Templates Service Dependency Graph Generation logic: Nodes: All components from catalog-info.yaml Edges: From dependsOn relationships Shape: Database nodes use [(name)], others use [name] …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/arch-view