Skill Router

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

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 skill-router
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/skill-router ~/.claude/skills/skill-router

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

From the SKILL.md

# Skill Router

Apply this skill when it is not obvious which practice fits, or when a piece of work will pass through several. It is a map, not a substitute: once a skill is picked, load it and follow it. Before telling someone what a skill says, read that skill — the one-line summaries here are for orientation only.

## Main flows

### Idea to shipped change

1. **Sharpen the idea** — `grilling` (an interview that settles decisions and keeps a glossary and ADRs). For a story with many rules, add `example-mapping`; for a whole process, `event-storming` or `process-level-event-storming`.
2. **Decide what to build first** — `user-story-mapping` for release slices, `splitting-user-stories` to cut stories thinner.
3. **Plan the work** — `to-tickets` for a dependency graph of thin end-to-end tickets; `ticket-writer` for each ticket's content. A single small change can skip straight to step 4.
4. **Build it test-first** — `test-driven-development`, with `unit-testing-principles` for what makes a test worth keeping, `test-data-patterns` for arranging test data, and `art-of-unit-testing` or `xunit-test-patterns` for naming, doubles and test smells.
5. **Keep the design clean as you go** — `tidy-first` for small structural changes ahead of behaviour changes, `refactoring` for named moves.
6. **Review** — `two-axis-code-review`: standards and spec, reported separately; `peer-review` for design, craft and test feedback written as line comments.
Read the full skill on GitHub

Details

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

FAQ

What does the Skill Router skill do?

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

How do I install the Skill Router 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 Skill Router 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

Software Architecture Design

8

Freddy-CHEN-ux/00_claude_skills

System design, architecture patterns, scalability tradeoffs, and distributed systems for production-grade software. Covers microservices, event-driven, CQRS, modular monoliths, and reliability patterns.

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

Software Backend

8

Freddy-CHEN-ux/00_claude_skills

Production-grade backend API development with Node.js 24 LTS/25 Current (Express 5.x/Fastify 5.2/NestJS 11.x), Python 3.14+ (FastAPI 0.115+), Go 1.25+, Rust 1.92+ (Axum 0.8+), Prisma 6.x ORM, PostgreSQL 18. Includes GraphQL, TypeScript 5.9+ strict mode, modern logging (Pino/Winston), secret managers, PM2 process management, and Prisma Accelerate for serverless/edge deployments.

Software Development

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