task-router
Skill4 starsChanged 52 days agoMITView on GitHub
Use only when the user explicitly requests help selecting a workflow or skill for a complex software task; choose relevant skills from their descriptions without implementing a custom skill router.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- pat-lewczuk/skillstheir own version, first seen Nov 1, 2026
- 2649895039-blip/task-api-routertheir own version, first seen Oct 13, 2026
- AidALL/ghost-alicetheir own version, first seen Oct 11, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- AidALL/ghost-alice★ 15same name
- pat-lewczuk/skills★ 3same name
- 2649895039-blip/task-api-router★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository37 other files it gives its agents.
- global-instructions/AGENTS.mdAGENTS.md
- api-contract-safetySkill
- api-endpoint-deprecationSkill
- aspnet-core-api-developmentSkill
- background-services-dotnetSkill
- bug-investigationSkill
- code-qualitySkill
- code-reviewSkill
- context-resetSkill
- dependency-managementSkill
- deployment-readiness-dotnetSkill
- diff-reviewSkill
- distributed-workflowsSkill
- dotnet-architectureSkill
- dotnet-implementationSkill
- dotnet-securitySkill
- ef-core-safetySkill
- exception-handlingSkill
- git-workflowSkill
- google-bigquery-dotnetSkill
- google-cloud-pubsub-dotnetSkill
- google-firestore-dotnetSkill
- http-client-integrationsSkill
- integration-testing-dotnetSkill
- observability-dotnetSkill
- performance-diagnostics-dotnetSkill
- poc-developmentSkill
- production-debuggingSkill
- production-hotfixSkill
- production-loggingSkill
- redis-dotnetSkill
- relational-database-dotnetSkill
- retry-resilienceSkill
- safe-terminalSkill
- shared-code-impactSkill
- targeted-validationSkill
- unit-testingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 28
Add api-contract-safety, exception-handling, production-logging, ef-core-safety, distributed-workflows, dependency-management, or …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Task router
Choose the smallest matching workflow. Do not turn classification into a deliverable.
| Request | Load |
| Bug fix | bug-investigation, then implementation/testing/validation as needed |
| Minor enhancement | dotnet-implementation; add contract/shared-impact skills when touched |
| Major feature | dotnet-architecture and dotnet-implementation |
| New customer-facing API | aspnet-core-api-development, api-contract-safety, and exception-handling; add logging and provider skills only as touched |
| Refactoring | shared-code-impact, unit-testing, targeted-validation |
| Production hotfix | production-hotfix |
| POC/experiment | poc-development |
| Investigation only | bug-investigation; do not implement without authorization |
| Code review | code-review |
| Testing only | unit-testing |
| API deprecation/removal | api-endpoint-deprecation |
| Dependency work | dependency-management |
| Google Cloud data/messaging | Load only the matching Pub/Sub, BigQuery, or Firestore skill |
| PostgreSQL/Oracle access | relational-database-dotnet and only its matching provider reference; also load ef-core-safety when EF Core behavior is involved |
| Commit/push/branch work | git-workflow |
Add api-contract-safety, exception-handling, production-logging, ef-core-safety, distributed-workflows, dependency-management, or production-debugging only when their subject is actually involved. Never preload unrelated cloud or database provider guidance. End code-changing work with diff-review and proportionate targeted-validation.
For every category, preserve unrelated behavior, constrain the blast radius, and inspect shared dependencies. Task size changes investigation and validation depth, never safety standards.
For outbound HTTP integration, load http-client-integrations; for boundary tests load integration-testing-dotnet. Load observability-dotnet, performance-diagnostics-dotnet, background-services-dotnet, or deployment-readiness-dotnet only when the specific task involves those concerns.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.