CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

add-intent-router

Replace an existing agent's hand-written routing (keyword if/else chains, regex, or an LLM call that only picks a route) with a Redis Iris Intent Router through redis-iris, so a message maps to a defined intent and its dispatch target by example phrasings and a score threshold. Asks five questions (what the routes are today, a few real phrasings per route, what each route dispatches to, what happens when nothing matches, which embedding model), writes the answers to intents.yaml, provisions the Router from the terminal with `iris intent-router service create`, loads the intents with `iris intent-router intents add`, then wires `router.match()` where the agent decides today. Use when the agent routes with keywords or an extra LLM call, or the user asks for intent detection, intent routing, or semantic routing.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary operational skill body: lean and table-driven with no concept padding, copy-paste-ready commands and code, a fully sequenced workflow with dry-run gates, atomic writes, explicit verification, and tuning feedback loops. The single-file structure is well organized but slightly dense; moving the per-error-code CLI handling into a reference file would make the overview tighter.

DimensionReasoningScore

Conciseness

The body is dense and imperative throughout: a five-question discovery table, exact CLI invocations, a YAML example, and a wiring snippet, with zero explanation of concepts Claude already knows (no 'what is an embedding' or 'what is Redis' padding). The opening paragraph ('The Router embeds the message, finds the nearest example phrasings, groups them by intent, applies a threshold...') describes product-specific behavior Claude would not know, so it earns its tokens. Not 4: there is no identifiable passage of over-explanation that could be trimmed without losing operational information.

5 / 5

Actionability

Fully executable guidance: copy-paste-ready CLI commands ('iris --json --no-input intent-router service create --name support --provider openai --model text-embedding-3-small --dimensions 1536 --role read --wait --write-env .env'), a concrete intents.yaml example, working Python ('router = IntentRouter.from_env()', 'found = router.match(message)'), and a framework wiring table naming exact replacement points (LangGraph router node, OpenAI Agents SDK triage agent, Google ADK before_agent_callback). The 'else: ... # question 4' placeholder is justified flexibility since the fallback is project-specific by design. Not 4: even error paths come with exact responses ('run the command in `details.command`').

5 / 5

Workflow Clarity

Six clearly sequenced sections (Discover → MCP facts → Configure → Wire → Verify → Report) with explicit validation checkpoints: 'Dry-run first: it sends nothing and lists every missing setting. If anything is missing, stop', atomic batch semantics for 'intents add', a six-item Verify section including a negative match test and a failure-mode test ('Unset `IRIS_INTENT_ROUTER_API_KEY` and confirm `ConfigurationError` names it'), and feedback loops for error recovery ('Wrong intent first: add phrasings to the right intent or raise its `minScore`, re-run `intents add`'). Not 4: validation is explicit and feedback loops cover both tuning directions, matching the anchor-5 example's structure.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and the body is a single ~136-line file with clear section headers, a consistent question/command/table pattern, and an external pointer to 'iris intent-router <command> --help' as the full reference. Structure is good and nothing is buried or nested. Not 5: the under-50-line simple-skill exception does not apply at this length, and portions of the CLI operational rules (error handling per error code, key minting workflow) are dense enough that they could live in a one-level reference file, keeping SKILL.md as a tighter overview. Not 3: there is no misplacement — inline content is appropriate to the workflow and navigation is easy.

4 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, complete description that names exact commands and artifacts, defines the problem it replaces (keyword if/else chains, regex, route-only LLM calls), and closes with an explicit 'Use when' clause containing natural trigger phrases. The only weakness is mild: a few natural synonyms like 'classify' or 'triage' are absent from the trigger list.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with exact commands: 'provisions the Router from the terminal with `iris intent-router service create`', 'loads the intents with `iris intent-router intents add`', 'then wires `router.match()`', and 'writes the answers to intents.yaml' — comprehensive coverage of the skill's workflow. Not 4: there are no meaningful gaps; every phase of the skill (discover, configure, provision, load, wire) is named with a concrete artifact or command.

5 / 5

Completeness

It explicitly answers both: 'what' — replace hand-written routing (keyword if/else chains, regex, or an LLM call that only picks a route) with a Redis Iris Intent Router, ask five questions, write intents.yaml, provision, load, wire match() — and 'when' — an explicit 'Use when the agent routes with keywords or an extra LLM call, or the user asks for intent detection, intent routing, or semantic routing' clause with concrete triggers. Not 4: the 'when' clause is already explicit and specific, which is what anchor 4 flags as missing.

5 / 5

Trigger Term Quality

The trigger clause covers natural phrases users would say: 'the agent routes with keywords or an extra LLM call, or the user asks for intent detection, intent routing, or semantic routing'. Not 5: common variations such as 'classify messages', 'message classification', or 'triage' — terms the skill body itself acknowledges via 'a classifier prompt' — are missing from the triggers. Not 3: the included terms are relevant, natural, and include multiple synonyms for the domain.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — replacing an agent's hand-written routing with a specific product (Redis Iris Intent Router via redis-iris) — with distinct triggers ('intent detection, intent routing, or semantic routing') that are unlikely to fire for unrelated skills. Not 4: no plausible overlap with a closely related skill is identifiable from the description; the product, the operation, and the triggers are all specific. Voice is third person throughout ('Replace...', 'Asks five questions...'), so no voice penalty applies.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

redis/agent-skills

Path

plugins/redis-development/skills/add-intent-router/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.