Menu

Individual skill

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.

plugins/juew/Skill-Routing-Kit/skills/skill-router/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,530
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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