worker-mention-routing

Route tasks to @-mentioned agents and validate worker availability.

2|Updated Apr 15, 2026

Search Tags:#routing #cli #delegation #multi-agent #orchestration #user-intent

Ready to run

npx skills add https://github.com/getspur/spur --skill worker-mention-routing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worker-mention-routing
Source: https://github.com/getspur/spur/tree/main/.spur/skills/worker-mention-routing
Command: npx skills add https://github.com/getspur/spur --skill worker-mention-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents AI agents from ignoring explicit user instructions when delegating tasks to specific workers, ensuring that user intent always takes precedence over algorithmic routing.

Core Features & Use Cases

Intent Prioritization: Enforces the Iron Law that user @-mentions override internal routing algorithms.
Ambiguity Resolution: Provides a structured framework for handling fuzzy or non-unique worker mentions.
Validation Guardrails: Ensures workers are verified against the available list before delegation, preventing silent failures or invalid assignments.

Quick Start

Use the worker-mention-routing skill to validate and route the current task to the agent explicitly mentioned by the user.

Frequently Asked Questions about worker-mention-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce explicit user @-mentions over algorithmic routing in a multi-agent CLI?▼

To enforce user @-mentions over algorithmic routing in a multi-agent CLI, you need a framework that prioritizes explicit user intent. This skill intercepts delegation instructions and ensures manual worker assignments override internal routing algorithms.

What happens when an AI agent tries to delegate a task to an unavailable or invalid worker?▼

When delegating to an unavailable worker, validation guardrails intercept the task and verify the target against the available list. This prevents silent failures and invalid assignments by blocking the delegation before execution.

How do I resolve ambiguous or non-unique worker mentions during multi-agent orchestration?▼

Resolving ambiguous worker mentions in multi-agent orchestration requires a structured framework for fuzzy matching. The system resolves non-unique mentions by validating them against the available worker list before allowing delegation.

Do I need a plan engine to capture delegation rationale for audit compliance in task routing?▼

Yes, capturing delegation rationale for audit compliance requires integration with a plan engine. This ensures that the reasons for user intent prioritization and worker routing are explicitly recorded during task delegation.

When should I not use algorithmic task routing in a multi-agent environment?▼

You should not use algorithmic task routing when a user explicitly provides an @-mention for a specific agent. In these cases, algorithmic selection must be bypassed to enforce the Iron Law of user preference.