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.
npx skills add majiayu000/claude-skill-registry --skill arch-view --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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`: ``` For each repo: Launch subagent with: "Read catalog-info.yaml from [repo_path
- Purpose
- When to Use
- Workflow
- Phase 1: Discover Repositories
- Phase 2: Parallel Metadata Collection
- Phase 3: Aggregate and Build Model
- Phase 4: Generate Requested View
- View Templates
- Service Dependency Graph
- Request Flow Map
- Event Topology
- Service Groupings
- Scripts
- aggregate-metadata.py
Aggregate from repos directory python skills/arch-view/scripts/aggregate-metadata.py repos/ Output as JSON python skills/arch-view/scripts/aggregate-metadata.py repos/ --format json Output as summary python skills/arch-view/scripts/aggregate-metadata.py repos/ --summary Generate all views python skills/arch-view/scripts/generate-mermaid.py aggregated.json Generate specific view python skills/arch-view/scripts/generate-mermaid.py aggregated.json --view dependency
What does the arch-view skill do?
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.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill arch-view --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.