intent-detection
FeaturedRoute ambiguous or mixed Phoenix/LiveView/Ecto requests before choosing a workflow. Use when user is unsure where to start/how to approach work, asks for the right workflow, or combines intents such as fixing and refactoring. NOT for a clear task.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- oliver-kriska
- Repository
- oliver-kriska/claude-elixir-phoenix
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- Python
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
intent
Classify user intent and route work to the correct omi stage before execution starts.
intent-routing
Classify any raw user input about workplace communication against the WiseTalk routing map and return a routing decision — routed agent, use case, context label, confidence — with a clarification round when confidence is borderline (0.4–0.6) so the user is asked to disambiguate instead of silently falling to GENERAL_CHAT. Use for EVERY user message entering the WiseTalk system. Do NOT use for content generation, coaching, or critique — this skill only decides WHO handles the message.
intent-router
Converges an underspecified request into a typed IntentSpec before any planning, routing or acting starts. Use when the user asks to implement, add, change, refactor, fix, migrate, configure, handle, triage, sort out, look into or decide something and the request leaves decisions open (which objects, which approach, what happens on failure, which trade-off) — in a codebase, a ticket queue, a research brief or an ops runbook — or when the user says "clarify the intent", "what do you need from me", or invokes intent-router. Looks up answers in whatever sources it can reach (code, deps, version history, tests, CI, docs, or a ticket log, an order record, entitlements, the policy in force) before asking the human; asks only preference or irreversible questions, one at a time, with a recommended default; halts instead of guessing. Do not use for explaining existing state ("what does X do", "why is Y slow"), or for a task whose objects, approach and failure behaviour are already stated.