PW

pcx-wave/skill-router

部署与 DevOps

本页由 AI 翻译,技术细节请以原文为准。 查看原文

27 stars 质量 43 趋势 15

Claude Code 的一个元技能,将请求路由到正确的安装技能——建议模式或静默自动路由

概览

你安装了183个技能,但记不清哪个负责什么?就用这个吧。它会准确选中你需要的技能。 Skill-Router 每次会话激活一次,扫描你安装的每一项技能,建立一个轻量级索引,然后悄无声息地将请求路由到正确的平台——你无需动手。 没有公告。简单问题也没有额外负担。触发技能的门槛故意很高:只有当技能会真正改变回答质量时,门槛才会触发。 (默认——求婚,加载前询问): 当技能符合你的请求时,你会看到: 自动路由并通过技能名称附加到路由后的回复上。没有其他功能。 累计计数会在多次会话中持续显示为~/.claude/skill-usage.json——这对发现你从未真正使用过的技能并清理它们很有帮助。 当你发送实质性请求时,路由器会在响应前检查索引:

概述(AI 翻译)

你装了183个技能,但记不清哪个负责什么? 就用这个吧。它会准确选中你需要的东西。

skill-router 每次游戏激活一次,扫描你安装的每一个技能,建立一个轻量级索引,然后悄无声息地将请求转发到正确的位置——你无需动手。

没有公告。简单问题也没有额外负担。触发技能的门槛故意很高:只有当某个技能确实会改变回答质量时才触发。


安装

用途

建议模式(默认——提议,加载前询问):

当技能符合你的请求时,你会看到:

自动模式(带归因的静默路由):

自动路由并将*(via skill-name)*附加到已路由的响应上。除此之外没有其他功能。

查看被索引的内容:

看看你实际使用哪些技能:

累计计数会在各场次持续到~/.claude/skill-usage.json——这对发现你从未真正使用过的技能并清理它们很有帮助。

关掉它:


它是如何运作的

当你发送实质性请求时,路由器会在响应前检查索引:

本页由 AI 翻译,技术细节请以原文为准。

README

skill-router

You’ve got 183 skills installed but can’t remember which one handles what?
Just use this one. It’ll pick exactly what you need.

skill-router activates once per session, scans every skill you have installed, builds a lightweight index, then silently routes your requests to the right one — without you lifting a finger.

No announcements. No overhead on simple questions. The bar for triggering a skill is deliberately high: it only fires when a skill would actually change the quality of the response.


Install

mkdir -p ~/.claude/skills/skill-router
curl -o ~/.claude/skills/skill-router/SKILL.md \
  https://raw.githubusercontent.com/pcx-wave/skill-router/main/SKILL.md

Usage

Suggest mode (default — proposes, asks before loading):

/skill-router on
Skill Router active [suggest] — 42 skills indexed (GEO/SEO, Testing, Deployment, Git, Security).

When a skill matches your request, you’ll see:

Suggested skills for this request:
  1. geo-audit — matches "GEO audit" + domain name
  2. geo-technical — also relevant for site-level analysis

Use skill 1, 2, or answer directly? (1/2/no)

Auto mode (silent routing with attribution):

/skill-router on --auto

Routes automatically and appends *(via skill-name)* to routed responses. Nothing else.

Check what’s indexed:

/skill-router status

See which skills you actually use:

/skill-router stats
Skill Usage Stats
-----------------
Skill               | Total | Session | Last Used
--------------------+-------+---------+----------
geo-audit           |    12 |       2 | 2026-05-15
vibe                |     8 |       0 | 2026-05-10
geo-schema          |     0 |       0 | never

Cumulative counts are persisted to ~/.claude/skill-usage.json across sessions — handy for spotting skills you’ve never actually used and cleaning them out.

Turn it off:

/skill-router off

How it works

When you send a substantive request, the router checks the index before responding:

  • Simple question or short message? → answered directly, no skill loaded
  • Substantive task with a clear keyword match? → suggests or auto-routes depending on mode
  • Weak or ambiguous match? → answered directly, no skill mentioned, no noise

One skill per request, max.


Limits

  • The skill index is session-only — routing state resets on new sessions
  • Usage stats are persisted to ~/.claude/skill-usage.json (written on each invocation)
  • In very long sessions, context compression can silently reset the routing state — just re-run /skill-router on if you notice it stopped
  • Requires skills installed at ~/.claude/skills/

License

MIT

在 GitHub 查看完整 README

推荐工具

换一个关键词,或者移除筛选条件。

安装

npx skillfish add pcx-wave/skill-router
新手?先看 mcpskill.org 教程 →