Install any skill in seconds. Free to start, no credit card required.
Get Started Free →oliver-kriska/intent-detection
Route ambiguous or mixed Phoenix/LiveView/Ecto requests before choosing a workflow.
Passed 16 of 23 test cases with the skill, and 7 of 23 without it.
and 11 more in the full report
14 fixed3 passed either way3 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have an existing plan file for the search index integration, but we need to enhance the plan with more detail regarding cache invalidation edge cases before implementation.
| Checked | Without skill | With skill |
|---|---|---|
| Suggests `/phx-plan --existing` to update the plan. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
| 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 then deploy |
| "performance", "slow", "N+1", "memory" | Performance | /phx-perf |
| "PR review", "review comments", "address feedback", "respond to PR" | PR response | /phx-pr-review |
| "that worked", "fixed it", "problem solved" | Knowledge capture | /phx-compound |
| "enhance plan", "more detail", "deepen" | Plan enhancement | /phx-plan --existing |
| "triage", "which findings", "prioritize fixes" | Finding triage | /phx-triage |
[command] — want me to run it, or should I just dive in?"/phx-* command: follow it, don't re-suggesttest cases passed, vs 7 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.