intent-detection

Featured

Route 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.

Code & Development 543 stars 38 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
91
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Intent Detection — Workflow Routing When user describes work WITHOUT specifying a `/phx:` command, analyze their intent and suggest the appropriate workflow BEFORE starting work. **Hard guard — check FIRST**: if the message starts with any slash command (`/phx:`, `/ecto:`, `/lv:`, or any other `/command`), this skill does not apply. Follow the invoked command directly — no routing analysis, no suggestion, zero output from this skill. ## Routing Table | Signal | Detected Intent | Suggest | |--------|----------------|---------| | "bug", "error", "crash", "failing", "broken", stack trace | Bug investigation | `/phx:investigate` | | "brainstorm", "explore idea", "not sure what I need", "vague idea", "let's discuss", "how to approach" | Ideation/requirements | `/phx:brainstorm` | | "add", "implement", "build", "create" + multi-step | New feature | `/phx:plan` | | "review", "check", "audit" code | Code review | `/phx:review` | | "fix" + small/specific scope | Quick fix | handle directly or `/phx:quick` | | "refactor", "clean up", "improve" | Refactoring | `/phx:plan` (needs scope) | | "research", "how to", "what's the best" | Research | `/phx:research` | | "evaluate", "compare", "adopt", "library", "should we use" | Library evaluation | `/phx:research --library` | | "test", "spec", "coverage" | Testing | handle directly or `/phx:plan` | | Describes 1-2 file changes, < 50 lines | Small task | handle directly | | "deploy", "release", "production" | Deployment | `/phx:verify` th...

Details

Author
oliver-kriska
Repository
oliver-kriska/claude-elixir-phoenix
Created
7 months ago
Last Updated
yesterday
Language
Python
License
MIT

Integrates with

Model Context Protocol · AI

Bundled in these plugins

claude-elixir-phoenix

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

intent

Classify user intent and route work to the correct omi stage before execution starts.

2 Updated today
ibahgat
AI & Automation Listed

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.

0 Updated 1 months ago
ay4322-a11y
AI & Automation Solid

template-workflows

Router and workflow hub for the Research Project Template — code, tests, manuscripts, pipeline, validation, docs, and reproducibility. USE WHEN the user wants to audit the repo, debug ./run.sh or execute_pipeline.py, add a feature, write tests, scaffold a manuscript, verify claims, fix cross-references, run validation gates, refactor, or prepare a Zenodo release, discover relevant template skills, improve agent routing, review external agentic operating models or retrieval references such as Steward OS, AutoResearch CLI, or LEANN, research a topic, write/review/revise a paper, or run a research-to-publication workflow — even if they never say "prompt", "skill", or docs/prompts. Also USE WHEN intent is ambiguous ("something wrong with my manuscript", "full health check", "fix the pipeline") — pick ONE child skill from the routing table and follow it. Do NOT use for generic homework, unrelated app security scans, or casual PDF summarization.

19 Updated today
docxology