Service Atlas

Survey a service's codebase and publish a Miro "atlas" of it — a Pete Hodgson tech debt wall (value × cost cards), SIG-style health scorecard, hotspot treemap (churn × size), change coupling, pay-down roadmap, code quality metrics (cyclomatic complexity risk profile, unit size, parameters, duplication), system context map and coupling matrix (Khononov strength, efferent/afferent), domain logic leaking into the application layer, a Big Picture EventStorming, and one process-level EventStorming frame per pivotal phase. Grounds every claim in the code with parallel read-only agents, measures with

5 stars 2 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add vnovakovits/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add vnovakovits/claude-skills --skill service-atlas
Manual install
git clone --depth 1 https://github.com/vnovakovits/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/engineering-practices/skills/service-atlas ~/.claude/skills/service-atlas

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Service Atlas

One run produces a Miro board that answers, for one service: what hurts, where it hurts, why, how it is wired to its neighbours, and how work flows through it. The board is for onboarding and for deciding what to fix next.

Everything on it must be traceable to the code. Agents read; you verify the headline claims before anything is drawn; scripts draw.

## Before you start

- **Miro MCP** connected (`canvas_create_from_svg`, `canvas_update_from_svg`, `canvas_read_as_svg`, `board_create`). Load the Canvas Composer skill (`canvas_get_canvas_composer_skill`, step `design` then `dsl`) once per conversation; the bundled renderer already follows its grammar, but you need it to patch frames.
- **Python 3** and **lizard** (`pip install lizard`, ideally into a venv in the scratchpad) and **git**.
- Work read-only on the service repo. Write outputs to the scratchpad, and offer to copy `atlas.json` plus the SVGs into the repo (for example `docs/service-atlas/`) at the end; Miro URLs rot, a checked-in model survives.

Ask the user once, in a single batched question, only for what you cannot infer: the service name, the scope (for example "the v3 API only": exclude legacy versions everywhere), and whether to create a new board (default) or extend an existing one.

## Workflow

### 1. Measure

```bash
python scripts/measure.py <repo> <src-dir> <scratch>/measurements.json --ext .cs --since <one year ago>
```
Read the full skill on GitHub

Details

Skill name
service-atlas
Path
plugins/engineering-practices/skills/service-atlas/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Service Atlas skill do?

Survey a service's codebase and publish a Miro "atlas" of it — a Pete Hodgson tech debt wall (value × cost cards), SIG-style health scorecard, hotspot treemap (churn × size), change coupling, pay-down roadmap, code quality metrics (cyclomatic complexity risk profile, unit size, parameters, duplication), system context map and coupling matrix (Khononov strength, efferent/afferent), domain logic leaking into the application layer, a Big Picture EventStorming, and one process-level EventStorming frame per pivotal phase. Grounds every claim in the code with parallel read-only agents, measures with

How do I install the Service Atlas skill?

Claude Code plugin: /plugin marketplace add vnovakovits/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Service Atlas popular?

It lives in vnovakovits/claude-skills, which has 5 GitHub stars and 2 forks.

Related skills

Accidental Cio

5

vnovakovits/claude-skills

Apply Scott Millett's "The Accidental CIO — A Lean and Agile Playbook for IT Leaders" (Wiley, 2024) when designing or reviewing how a technology organisation decides, funds, governs and delivers work. Covers the five components of an adaptive IT operating model (organised, work, govern, talent, lead) and its four themes (outcomes over output, intrinsic motivation, being not doing agile, manage flow not people); matching method and governance to context via Cynefin and Wardley evolution; governance as demand management + funding + measurement + decision rights, shifting from project funding to

Frontend & Design

Agent Retro

5

vnovakovits/claude-skills

Run a retrospective on a coding-agent session and improve the agent's environment, not the code. Combines Derby & Larsen's five-stage retrospective, Shigeo Shingo's poka-yoke (turn a mechanical mistake into a check that makes it impossible), and Matt Pocock's retro categories — navigation, automated checks, coding standards, steering files, tool economy, information access. Covers mining the session transcript for corrections, wrong turns and slow searches; deciding where each fix belongs (analyzer, hook, CI, reviewer standards, CLAUDE.md pointer, skill, doc or memory); the no-op test for stee

AI, LLMs & Agents

API Design

5

vnovakovits/claude-skills

Design APIs that are clear, evolvable, and idiomatic to their protocol — covering REST (Fielding, Richardson Maturity Model, Massé), GraphQL, gRPC/protobuf, versioning strategies, pagination, error responses (RFC 7807 Problem Details), idempotency, authentication, documentation (OpenAPI), and the pragmatic trade-offs between RESTful purity and developer ergonomics. Use when designing a new endpoint, choosing between REST/GraphQL/gRPC, defining versioning, structuring error responses, deciding pagination strategy, or evaluating an existing API's evolvability.

Software Development

Show Me

5

bolasblack/claude-skills

Make the current discussion concrete with diagrams, code-shape sketches, and focused HTML artifacts. Use when the user asks to see a structure, flow, relationship, layout, or before-and-after change.

Software Development

Semantic Search

8

Freddy-CHEN-ux/00_claude_skills

INVOKE BEFORE writing new code to find existing implementations (DRY). Also for codebase exploration and production data search. Run: docker exec arsenal-semantic-search-cli code-search find 'query

Software Development

Skill Router

5

vnovakovits/claude-skills

Pick the right engineering-practices skill, or sequence of skills, for the situation at hand. Maps common situations — a fuzzy idea, a feature to plan, code to write or test, a bug, legacy code, a design or architecture question, an event-sourced model, a review, a pull request, a slow team or process, product discovery, writing, an agent session that went wrong — to the skills in this plugin, and lays out the main flows through them (idea to shipped change, bug to fix, legacy change, design review, improving how a team works). Use when unsure which skill applies, when the user asks "which ski

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.