intent-classifier
Skill2 starsChanged 10 days agoMITView on GitHub
Classify user intents and route to appropriate skills, commands, or workflows. Use when determining which skill to invoke, routing requests to specialized agents, or building skill selection logic. Trigger on 'which skill should I use', 'route this to', 'classify this request', 'skill selection', or when multiple skills could handle a task. Not for skill-creator, skill-evaluator.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- s977043/PlanGatetheir own version, first seen Nov 2, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- s977043/PlanGate★ 3same 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 repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/avoid-ai-writing/AGENTS.mdAGENTS.md
- .agents/skills/do-web-doc-resolver/AGENTS.mdAGENTS.md
- .agents/skills/skill-evaluator/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- accessibility-auditorSkill
- agent-browserSkill
- agentic-abstentionSkill
- agents-mdSkill
- api-design-firstSkill
- architecture-diagramSkill
- avoid-ai-writingSkill
- cicd-pipelineSkill
- cloudflare-worker-apiSkill
- codacySkill
- codeberg-apiSkill
- code-review-assistantSkill
- css-render-performanceSkill
- database-devopsSkill
- debuggerSkill
- delegateSkill
- dependency-upgradesSkill
- dist-channel-selectionSkill
- docs-hookSkill
- document-rendering-and-locatorsSkill
- dogfoodSkill
- dora-reportSkill
- do-web-doc-resolverSkill
- durable-objectsSkill
- eu-ai-act-complianceSkill
- git-github-workflowSkill
- goap-agentSkill
- implementerSkill
- iterative-refinementSkill
- jules-delegatorSkill
- learnSkill
- lifecycle-managementSkill
- local-context-sanitizationSkill
- memory-contextSkill
- migration-refactoringSkill
- nested-build-isolationSkill
- privacy-firstSkill
- progressive-deliverySkill
- pwa-offline-syncSkill
- reader-ui-uxSkill
- readme-best-practicesSkill
- secrets-managementSkill
- secure-invite-and-accessSkill
- security-code-auditorSkill
- shell-script-qualitySkill
- skill-creatorSkill
- skill-evaluatorSkill
- static-analysisSkill
- testing-strategySkill
- test-runnerSkill
- triz-solverSkill
- turso-dbSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Consider skill descriptions and keywords
- Distinctive: line 60
When a request contains multiple intents:
- Distinctive: line 63
Composite: - Use parent skill that orchestrates sub-skills
- Distinctive: line 76
Update the skill catalog using:
≈ “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
Intent Classifier
Classify user requests and route them to the most appropriate skill, command, or specialized agent.
When to Use
- User asks which skill to use or how to route a request
- Need to determine which skill handles a given task
- Multiple skills could handle a request and disambiguation is needed
- Even if they just say "which skill should I use" or "route this"
Classification Workflow
1. Intent Extraction
- Parse the user's natural language request
- Identify primary action (create, update, delete, analyze, etc.)
- Extract entities (file paths, technologies, specific terms)
2. Skill Matching
- Compare against available skills catalog
- Score match confidence for each candidate
- Consider skill descriptions and keywords
3. Route Decision
- Select highest-confidence match
- Handle ties and ambiguous cases
- Fall back to general assistance if no match
Classification Rules
Priority Order
- Exact keyword match - Skill description contains exact phrase
- Domain match - Technology stack alignment
- Action match - Verb/action alignment
- Context match - File paths, extensions, surrounding context
Confidence Scoring
High (0.8-1.0): Exact description match, multiple keyword hits
Medium (0.5-0.7): Partial match, related domain
Low (0.3-0.4): Weak match, shared keywords only
None (<0.3): No relevant matchMulti-Intent Handling
When a request contains multiple intents:
- Sequential - Chain skills in dependency order
- Parallel - Execute independent skills simultaneously
- Composite - Use parent skill that orchestrates sub-skills
Fallback Strategies
| Confidence | Action |
| > 0.7 | Execute primary skill |
| 0.5 - 0.7 | Execute skill with confirmation |
| 0.3 - 0.5 | Present top 2-3 options to user |
| < 0.3 | Use general assistance |
Dynamic Catalog
Update the skill catalog using:
./scripts/generate-skill-catalog.shThis scans .agents/skills/ and regenerates the skill registry with:
- Skill names and full descriptions (1024-char budget,
Not forguards retained) - Categories, with a per-category index
Regenerate after adding, renaming, or removing a skill. The previous
dynamic-catalog.sh entry point is a deprecated shim that delegates here.
Skill Selection Examples
| User Request | Primary Intent | Routed Skill |
| "Create a new skill for Docker" | Skill creation | skill-creator |
| "Audit my code for security issues" | Security audit | security-code-auditor |
| "Design a REST API for users" | API design | api-design-first |
| "Fix this bug in my Python script" | Code debugging | (general) |
See Also
skill-creator— Create and improve skillsskill-evaluator— Evaluate and score skillsgoap-agent— Orchestrator for complex multi-step tasks
Rationalizations
| Rationalization | Reality |
| "I can just pick a skill manually" | Systematic classification ensures the best-matched skill is used and prevents overlooking specialized alternatives. |
| "Close enough is fine, I'll just pick the first match" | Low-confidence matches lead to wrong workflows and wasted tokens; present options when uncertain. |
Red Flags
- Routing to a skill without checking confidence score
- Ignoring multi-intent requests that require chaining skills
- Failing to update the dynamic catalog after adding new skills
References
references/classification-rules.md- Detailed classification algorithmreferences/skill-catalog.md- Auto-generated skill registryreferences/workflow-patterns.md- Multi-skill orchestration patterns
Voice & Context
- Default:
professional+blog - Reference:
voice-profilesskill for definitions and auto-detection.
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.

