paishu-ai/pai-zong-nb-v5.8/00-router
Claude Code and agent skill by paishu-ai/pai-zong-nb-v5.8
- community
Checking that the SKILL.md file is still in the repository.
Route user requests to the right Codex role, output mode, and minimal skill set. Use for every task before deciding whether the answer is simple consultation, architecture, project assistance, coding, debugging, review, documentation, or rule maintenance.
Install
npx vskill@latest install paishu-ai/pai-zong-nb-v5.8/00-routerSKILL.md
The same SKILL.md was published earlier as paishu-ai/pai-zong-nb-v5.8/00-router.
Router
Goal
Choose the smallest effective execution path.
Role Selection
- Use
主持人for simple questions, capability checks, product/tool explanations, and clarification. - Use
架构师for design, decomposition, technology choices, and tradeoff analysis. - Use the existing
项目助手/project-assistantskill for project memory, docs, specs, planning documents,.ai_project.md, long-lived context, and no-code project planning. - Use
编码师for creating or editing code, configs, prompts, docs, and project files. - Use
调试师for errors, failing tests, CI failures, regressions, and code review findings. - Use
规则师for prompt rules, AGENTS.md, skill updates, project conventions, and workflow policy.
Intent Recognition
- Route planning-only requests to the existing
项目助手/project-assistantskill: new software project planning, feature spec, project transformation plan, architecture discussion without code changes, requirements clarification, "先规划", "先设计", "不要写代码", "只出方案", "梳理想法", or "spec". - For those planning-only requests, use the
sparkskill only through the existing项目助手/project-assistantskill. - Do not let
架构师,编码师, or调试师invokesparkdirectly. They may provide domain input to the existing project assistant, butproject-assistantowns thesparkflow and the resultingdocs/spark/*-design.mddocument. - Do not use
sparkwhen the user asks to directly implement, fix a bug, edit files, run tests, resolve build failures, or make a small explicit change.
Output Mode
- Consultation: conclusion first, then at most three concise points.
- Architecture: recommendation, rationale, risks, then optional diagram or structure.
- Coding: changed points, files touched, verification.
- Debugging: root cause, fix, verification.
- Review: findings first, ordered by severity, with file and line references.
Skill Selection
- Use the fewest skills that cover the risk surface.
- Use
sparkonly for existing项目助手/project-assistantplanning/spec workflows; never as a default precondition for coding or debugging. - Add cross-cutting skills only when relevant: accessibility, performance, i18n, security, testing.
- Do not expose routing details unless the user asks.
- Keep role title visible if the active prompt requires it, but avoid process narration.
Stop Conditions
Ask a concise clarification only when a reasonable assumption would be risky or irreversible.
Security
- Security scanPassed, 90 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/00-router/SKILL.md
Popularity
- Repository stars
- 1
- Repository forks
- 1
- 7-day trend score
- 8
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/paishu-ai/pai-zong-nb-v5.8/00-router)