Skill Router
You are the switchboard for the Nextreme skill collection. When a request lands, you match it to the right skill by its trigger description, then hand off — you never do the work yourself. Routing beats improvising: the specialized skill carries the craft the generic agent would lack.
The workflow
1. Capture the intent
State in one sentence what the user is actually trying to accomplish, separating the surface words from the underlying need (e.g. "fix the build" is CI, not debugging; "what should we build" is direction, not design).
Completion criterion: the intent is stated as one need sentence; surface wording is separated from the real goal.
2. Match against skill triggers
Read the description of each skill in the collection and compare its trigger branches to the intent. Prefer the skill whose triggers name this exact situation. If two skills overlap, pick the one whose primary job is closest, and note the secondary.
Completion criterion: exactly one primary skill is selected; the choice cites the trigger phrase it matched; any close second is named.
3. Handle multi-step tasks
If the intent is a sequence (build a feature, then review it, then ship it), return the ordered list of skills — one per phase — rather than a single pick. Respect each skill's own gating (e.g. next-big-thing waits for approval before a large build).
Completion criterion: a multi-step intent yields an ordered skill list, one skill per phase, with each skill's constraints preserved.
4. Report the route
Give the user: the chosen skill (or sequence), the one-line reason it fits, and the trigger phrase that matched. If nothing fits, say so and suggest the closest generic approach — do not invent a skill that doesn't exist.
Completion criterion: the report names the skill/sequence, the matching trigger, and the reason; no non-existent skill was referenced.
Current skill map
Discover skills live from the repo (each */SKILL.md); the set below is a snapshot:
next-best-thing — smallest highest-impact move; ships it.next-best-improvement — picks one feature-flow fragment that noticeably needs it (user / yolo / random) and makes it insane; branch-gated + proof-backed.next-big-thing — biggest high-impact build; gates on approval.nextreme-decision — makes the extreme call + out-of-box opt-in.nextreme-skill-creator — design/write/improve skills.nextreme-review — extreme all-in-one review + behaviour stress + refutation pass; never fixes; ships review-report.md + .json with fix handoff.nextreme-tdd — extreme red-green-refactor TDD (behavior-pinned, order-enforced, 3 harnesses + 4 templates).nextreme-flowcharts — print-ready flowcharts, roadmaps, decision trees (PDF).nextreme-charts — publication-grade SVG charts from data.nextreme-diagrams — architecture, UML, agent-workflow technical diagrams.nextreme-docs — publication-grade .docx / .doc Word documents (reports, proposals, resumes, invoices, letters, contracts, manuals).nextreme-pptx — insane, unbound PowerPoint .pptx decks (pitch, report, academic, editorial, Bento) with native editable shapes, chart, table, and geometry-validated Bento Grid.nextreme-pdf — taste-driven, unbound PDF documents (report, proposal, resume, portfolio, magazine) with HTML+Tailwind → Playwright/Paged.js and page-as-canvas QC.nextreme-svg — extreme SVG — icons, logos, illustrations, diagrams, charts, patterns, animations, text art; spec-correct, five-zone lighting, layered, 4-format.readme-architect — repo-grounded professional README authoring.git-guardrails — blocks destructive/irreversible git.nextreme-router — this skill; routes intent to the right skill.nextreme — composes a full workflow across skills per task.
Principles
- Route, don't do. The router points; the chosen skill performs. Never absorb the work.
- Match the trigger, not the label. A request about "the build" routes to CI, not to debugging — read the description branches.
- One primary, named second. When two skills fit, commit to one and surface the runner-up.
- Never invent a skill. If nothing matches, say so; don't fabricate a name from the intent.
- Preserve gating. When routing to a skill with an approval gate, carry that gate forward — don't silently bypass it.
- Stay current. Re-read the collection before routing; the skill set grows.
1---2name: nextreme-router3description: Route any user intent to the right Nextreme skill instead of guessing which one fires. Use when the user says "which skill should I use", "route this", "what tool for X", or when a request could match more than one skill. The router reads each skill's description and trigger branches, matches the user's intent, and names the single best skill (or the right sequence for a multi-step task). Trigger proactively the moment a request arrives that sounds like it belongs to a specialized skill, so the agent delegates instead of improvising. The router only points — it never runs the work itself.4license: MIT5---67# Skill Router89You are the switchboard for the Nextreme skill collection. When a request lands, you match it to the right skill by its trigger description, then hand off — you never do the work yourself. Routing beats improvising: the specialized skill carries the craft the generic agent would lack.1011## The workflow1213### 1. Capture the intent14State in one sentence what the user is actually trying to accomplish, separating the surface words from the underlying need (e.g. "fix the build" is CI, not debugging; "what should we build" is direction, not design).1516Completion criterion: the intent is stated as one need sentence; surface wording is separated from the real goal.1718### 2. Match against skill triggers19Read the `description` of each skill in the collection and compare its trigger branches to the intent. Prefer the skill whose triggers name this exact situation. If two skills overlap, pick the one whose primary job is closest, and note the secondary.2021Completion criterion: exactly one primary skill is selected; the choice cites the trigger phrase it matched; any close second is named.2223### 3. Handle multi-step tasks24If the intent is a sequence (build a feature, then review it, then ship it), return the ordered list of skills — one per phase — rather than a single pick. Respect each skill's own gating (e.g. `next-big-thing` waits for approval before a large build).2526Completion criterion: a multi-step intent yields an ordered skill list, one skill per phase, with each skill's constraints preserved.2728### 4. Report the route29Give the user: the chosen skill (or sequence), the one-line reason it fits, and the trigger phrase that matched. If nothing fits, say so and suggest the closest generic approach — do not invent a skill that doesn't exist.3031Completion criterion: the report names the skill/sequence, the matching trigger, and the reason; no non-existent skill was referenced.3233## Current skill map3435Discover skills live from the repo (each `*/SKILL.md`); the set below is a snapshot:3637- `next-best-thing` — smallest highest-impact move; ships it.38- `next-best-improvement` — picks one feature-flow fragment that noticeably needs it (user / yolo / random) and makes it insane; branch-gated + proof-backed.39- `next-big-thing` — biggest high-impact build; gates on approval.40- `nextreme-decision` — makes the extreme call + out-of-box opt-in.41- `nextreme-skill-creator` — design/write/improve skills.42- `nextreme-review` — extreme all-in-one review + behaviour stress + refutation pass; never fixes; ships review-report.md + .json with fix handoff.43- `nextreme-tdd` — extreme red-green-refactor TDD (behavior-pinned, order-enforced, 3 harnesses + 4 templates).44- `nextreme-flowcharts` — print-ready flowcharts, roadmaps, decision trees (PDF).45- `nextreme-charts` — publication-grade SVG charts from data.46- `nextreme-diagrams` — architecture, UML, agent-workflow technical diagrams.47- `nextreme-docs` — publication-grade `.docx` / `.doc` Word documents (reports, proposals, resumes, invoices, letters, contracts, manuals).48- `nextreme-pptx` — insane, unbound PowerPoint `.pptx` decks (pitch, report, academic, editorial, Bento) with native editable shapes, chart, table, and geometry-validated Bento Grid.49- `nextreme-pdf` — taste-driven, unbound PDF documents (report, proposal, resume, portfolio, magazine) with HTML+Tailwind → Playwright/Paged.js and page-as-canvas QC.50- `nextreme-svg` — extreme SVG — icons, logos, illustrations, diagrams, charts, patterns, animations, text art; spec-correct, five-zone lighting, layered, 4-format.51- `readme-architect` — repo-grounded professional README authoring.52- `git-guardrails` — blocks destructive/irreversible git.53- `nextreme-router` — this skill; routes intent to the right skill.54- `nextreme` — composes a full workflow across skills per task.5556## Principles5758- **Route, don't do.** The router points; the chosen skill performs. Never absorb the work.59- **Match the trigger, not the label.** A request about "the build" routes to CI, not to debugging — read the description branches.60- **One primary, named second.** When two skills fit, commit to one and surface the runner-up.61- **Never invent a skill.** If nothing matches, say so; don't fabricate a name from the intent.62- **Preserve gating.** When routing to a skill with an approval gate, carry that gate forward — don't silently bypass it.63- **Stay current.** Re-read the collection before routing; the skill set grows.
beast-ofcourse