Mmcp.market

skill-router skill

by rohitg00·rohitg00/pro-workflow·2.9k stars

The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".

A100/100content scan

Is the skill-router skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the skill-router skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/rohitg00/pro-workflow.git /tmp/pro-workflow
mkdir -p ~/.claude/skills
cp -r /tmp/pro-workflow/skills/skill-router ~/.claude/skills/skill-router
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

skill-router

You cannot hold 41 skills and 23 commands in your head. This is the index so you do not have to. Each entry says what it is for and how it fires: [human] you invoke it deliberately, [auto] the agent reaches for it from your prompt.

Keep this honest. When a skill is added, renamed, removed, or changes how it fits a flow, update this file in the same change. A router that points at a skill that no longer exists, or omits a new one, is worse than none.

How to use it

State the job in one line. Match it to a group below. If two skills look close, the when to reach clause is the tiebreaker. Most skills have a matching slash command of the same name, so this index covers commands too.

Self-correction and memory

  • learn-rule [human] - capture a correction as a durable rule loaded on every future session.
  • replay-learnings [auto] - surface past learnings relevant to the task before you start.
  • insights [human] - correction trends, heatmaps, productivity view.
  • skill-optimizer [human] - train a skill's SKILL.md against accumulated corrections.

Planning and decisions

  • plan-interrogate [human] - resolve every open decision before code; emits a decision ledger, a shared-language CONTEXT.md, and decision records.
  • domain-modeling [human] - build the project's shared vocabulary and bounded contexts up front.
  • improve-architecture [human] - audit an area and propose the smallest structural moves; plan, not rewrite.
  • thoroughness-scoring [auto] - score each decision point 1-10 so effort tracks stakes.
  • orchestrate [human] - wire commands, agents, and skills together for a multi-phase feature.

Multi-agent and parallel work

  • agent-teams [human] - lead plus teammates sharing one task list.
  • batch-orchestration [human] - split a large change into independent units, one agent each.
  • parallel-worktrees [human] - git worktrees for zero-dead-time parallel sessions.
  • sprint-status [human] - status across active parallel sessions.

Context and tokens

  • context-engineering [human] - Write, Select, Compress, Isolate; the memory taxonomy.
  • context-optimizer [human] - trim token usage when a session drags.
  • compact-guard [human] - preserve critical state before compaction.
  • token-efficiency [auto] - anti-sycophancy, tool-call budgets, one-pass output.
  • mcp-audit [human] - audit MCP servers for token overhead, redundancy, security.

Quality and review

  • tdd [human] - red-green-refactor loop with good-test guidance.
  • deslop [auto] - strip AI slop and over-engineering from the branch diff; also lints SKILL.md files.
  • smart-commit [human] - quality gates, staged review, conventional commit.
  • llm-gate [auto] - LLM-verified checks on commits, patterns, patches.
  • llm-council [human] - multi-LLM deliberation on a hard call.
  • safe-mode [human] - hook-enforced guard against destructive operations.

Design and writing

  • design-engineering [auto] - interface craft: motion decision framework, easing, timing, springs, component feel, visual foundations.
  • writing-guidelines [auto] - clear-writing standards for docs, UI copy, error messages, commit and PR text.

Knowledge and research

  • wiki-builder [human] - start and grow a persistent FTS5-indexed wiki.
  • wiki-query [auto] - BM25 retrieval over a wiki with citations.
  • wiki-research-loop [human] - budget-capped auto-grow of a wiki.
  • wiki-viewer [human] - self-contained HTML view of a wiki.
  • survey-generator [human] - structured literature survey on a topic.

Orientation, cost, lifecycle, setup

  • module-map [auto] - one-screen map of an unfamiliar area.
  • bug-capture [auto] - turn a reported defect into a domain-language issue.
  • cost-tracker [human] - session cost and budget alerts.
  • permission-tuner [human] - generate allow/deny rules from denial patterns.
  • wrap-up [human] - end-of-session ritual: audit, persist learnings, handoff.
  • session-handoff [human] - structured handoff doc for the next session.
  • file-watcher [human] - hooks that react to config/env/dep changes.
  • auto-setup [human] - configure gates, hooks, settings for a new project.
  • pro-workflow [auto] - the system overview; orchestration patterns and reference.
  • skill-router [human] - this index of every skill and command.

Command-only (no matching skill)

These slash commands ship without a skill of the same name: /commit, /develop, /doctor, /handoff, /learn, /list, /parallel, /replay, /search, /skill-optimize, /wiki.

Naming the invocation mode

Every skill declares one intent. [human] skills are deliberate, side-effectful, or session rituals and carry user-invocable: true. [auto] skills earn their place in context by a description precise enough to fire on the right prompt and stay quiet otherwise. See rules/skill-conventions.mdc for the full convention and the write-operation rules for state-changing skills.

More skills from rohitg00/pro-workflow

  • Aagent-teamsCoordinate multiple Claude Code sessions as a team — lead + teammates with shared task lists, mailbox messaging, and file-lock claiming. Patterns for team sizing, task decomposition, and when to use teams vs sub-agents vs worktrees.
  • Aauto-setupAuto-configure quality gates, hooks, and settings for a new project. Detects project type and sets up appropriate tooling. Use when onboarding a new codebase.
  • Abatch-orchestrationDecompose large-scale changes into independent units and spawn parallel agents in isolated worktrees. Use for migrations, refactors, codemods, and any change touching 10+ files with the same pattern.
  • Cbug-captureCapture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".
  • Acompact-guardSmart context compaction with state preservation. Saves critical files, task progress, and working state before compaction, restores after. Use before manual compact or when auto-compact triggers.
  • Acontext-engineeringMaster the four operations of context engineering — Write, Select, Compress, Isolate. Manage token budgets, compaction strategies, and context partitioning to keep AI sessions sharp and efficient.
  • Acontext-optimizerOptimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.
  • Acost-trackerTrack session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
  • Adesign-engineeringApply interface craft when building or reviewing UI - motion, easing, timing, springs, component feel, and visual foundations. Use when building a component, animation, transition, hover or press state, modal, drawer, toast, or when polishing an interface so it feels right. Says "make this feel better", "add an animation", "polish the UI", "review this component".
  • AdeslopRemove AI-generated code slop, unnecessary comments, and over-engineering from the current branch diff. Cleans up boilerplate, simplifies abstractions, strips defensive code, and in skill-file mode lints SKILL.md files for quality. Use when cleaning up code, simplifying, removing boilerplate, before committing, or when reviewing a skill before promoting it.
  • Adomain-modelingBuild the project's shared language and bounded contexts before writing code, so names stay consistent and the agent stops paraphrasing domain concepts. Produces a CONTEXT.md glossary and decision records. Use at the start of a project or feature, or when the codebase and the people describing it speak different languages.
  • Afile-watcherConfigure file watching hooks to auto-react to config changes, env file updates, and dependency modifications. Use to set up reactive workflows.

All agent skills → · MCP servers