Skill Router logo

Skill Router

Community
juew
skill-router

Use when the user explicitly asks to diagnose or improve Codex skill/plugin routing, determine which skill or plugin should handle a request, refresh or check a skill registry, investigate why a skill/plugin did not trigger, or review skill descriptions for trigger quality. Do not use for ordinary task execution when a concrete domain skill clearly applies, unless routing is ambiguous or the user asks for routing.

Overview

Publisherjuew
RepositorySkill-Routing-Kit
Skill nameskill-router
Stars
119
Forks
7
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by juew on GitHub. Read the source before you install it.

Installation

Install the Skill Router AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/juew/Skill-Routing-Kit/tree/main/skills/skill-router
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/juew/Skill-Routing-Kit.git /tmp/Skill-Routing-Kit
mkdir -p .claude/skills
cp -r /tmp/Skill-Routing-Kit/skills/skill-router .claude/skills/skill-router
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Skill Router in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Skill Router on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Skill Router is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Skill Router

Use this skill as a diagnostic and routing-assistance layer. It does not replace Codex native skill discovery, Superpowers process skills, or subagent orchestration. It helps decide which capabilities are relevant, why they are relevant, and when not to use them.

Boundaries

  • Do not execute the user's domain task unless the user asks you to continue after routing.
  • Do not assume external connectors are authenticated or can see data.
  • Do not treat registry cards as the source of truth. Use them as hints with provenance.
  • Do not perform dynamic scanning unless the user asks to refresh or check the registry.
  • Prefer local files, local repositories, browser verification, and build/test commands unless the user explicitly names an external app or the source of truth clearly lives there.

When To Use

Use this skill when the user asks things like:

  • "Which skill should handle this?"
  • "Why did this skill not trigger?"
  • "Refresh the skill registry."
  • "Review this skill description for trigger quality."
  • "List likely skills/plugins for this task."
  • "Help me improve skill/plugin hit rate."

When Not To Use

Do not use this skill for simple tasks with an obvious primary skill:

  • Editing a local PDF: use the PDF skill.
  • Creating a slide deck: use the presentation skill.
  • Debugging a failing test: use systematic debugging first.
  • Implementing a frontend app: use frontend app building/testing skills.

If the task is complex or ambiguous, perform a brief routing check and then continue with the selected primary skill.

Diagnostic Workflow

  1. Classify the user request:
    • task type: explain, create, edit, debug, analyze, test, review, deploy
    • source: local, web, GitHub, Gmail, Drive, Notion, Slack, Figma, Linear
    • artifact: code, document, spreadsheet, presentation, PDF, image, webpage, report
    • process need: planning, debugging, TDD, verification, review, orchestration
  2. Read the registry if available.
  3. Identify recommended skill/plugin candidates.
  4. Apply local-first and connector-explicit rules.
  5. Return concise output:
    • Recommended skill
    • Helper skills
    • Why
    • Do not use
    • Needs confirmation
  6. If debug mode is requested, include skipped candidates and scoring details.

Output Format

text
Recommended skill:
- ...

Helper skills:
- ...

Why:
- ...

Do not use:
- ...

Needs confirmation:
- ...

Registry Maintenance

Use scripts/build_registry.py only when the user explicitly asks to refresh the registry or when the registry is stale, missing, or inconsistent.

Use scripts/route_request.py --check-registry to inspect registry health.

See references/capability-card-schema.md for card fields and provenance requirements.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Skill Router AI skill do?

Use when the user explicitly asks to diagnose or improve Codex skill/plugin routing, determine which skill or plugin should handle a request, refresh or check a skill registry, investigate why a skill/plugin did not trigger, or review skill descriptions for trigger quality. Do not use for ordinary task execution when a concrete domain skill clearly applies, unless routing is ambiguous or the user asks for routing.

Why use Skill Router on TypingMind?

Because you install it once and use it with any model. Skill Router is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Skill Router in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/juew/Skill-Routing-Kit/tree/main/skills/skill-router. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Skill Router?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Skill Router?

As many as you like. As long as a model supports skills, you can use Skill Router with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Skill Router AI skill free?

Yes. It is published on GitHub by juew under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇