Multi-agent routing, channel bindings, and tool policies
36
32%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./src/skills/bundled/routing/SKILL.mdRoute messages to specialized agents, configure channel bindings, and manage tool access policies.
/agents List available agents
/agent trading Switch to trading agent
/agent research Switch to research agent
/agent main Switch to main agent
/agent status Current agent info/bind trading Bind channel to trading agent
/bind research Bind channel to research agent
/unbind Remove channel binding
/bindings List all bindings/tools List available tools
/tools allow <agent> <tool> Allow tool for agent
/tools deny <agent> <tool> Deny tool for agent
/tools policy <agent> View agent's tool policyimport { createRoutingService } from 'clodds/routing';
const routing = createRoutingService({
// Default agent
defaultAgent: 'main',
// Agent definitions
agents: {
main: {
name: 'Main',
description: 'General assistant',
model: 'claude-3-sonnet',
systemPrompt: 'You are a helpful trading assistant...',
allowedTools: ['*'], // All tools
},
trading: {
name: 'Trading',
description: 'Order execution specialist',
model: 'claude-3-haiku',
systemPrompt: 'You execute trades efficiently...',
allowedTools: ['execute', 'portfolio', 'markets', 'feeds'],
},
research: {
name: 'Research',
description: 'Market analysis expert',
model: 'claude-3-opus',
systemPrompt: 'You provide deep market analysis...',
allowedTools: ['web-search', 'web-fetch', 'markets', 'news'],
},
alerts: {
name: 'Alerts',
description: 'Notification handler',
model: 'claude-3-haiku',
systemPrompt: 'You manage price alerts...',
allowedTools: ['alerts', 'feeds'],
},
},
// Storage
storage: 'sqlite',
dbPath: './routing.db',
});// Route determines best agent
const route = await routing.route({
message: 'Buy 100 shares of Trump YES',
channelId: 'telegram-123',
userId: 'user-456',
});
console.log(`Routed to: ${route.agent}`);
console.log(`Confidence: ${route.confidence}`);
console.log(`Reason: ${route.reason}`);const agents = routing.getAgents();
for (const [id, agent] of Object.entries(agents)) {
console.log(`${id}: ${agent.name}`);
console.log(` ${agent.description}`);
console.log(` Model: ${agent.model}`);
console.log(` Tools: ${agent.allowedTools.join(', ')}`);
}routing.addAgent({
id: 'defi',
name: 'DeFi Specialist',
description: 'Solana and EVM DeFi expert',
model: 'claude-3-sonnet',
systemPrompt: 'You are an expert in DeFi protocols...',
allowedTools: ['solana', 'evm', 'bridge', 'portfolio'],
patterns: [
/swap|dex|liquidity|pool/i,
/solana|jupiter|raydium/i,
/uniswap|1inch|bridge/i,
],
});routing.updateAgent('trading', {
model: 'claude-3-sonnet', // Upgrade model
allowedTools: [...currentTools, 'futures'],
});// Bind channel to specific agent
await routing.addBinding({
channelId: 'telegram-trading-group',
agentId: 'trading',
});
// Get binding for channel
const binding = await routing.getBinding('telegram-trading-group');
console.log(`Channel bound to: ${binding?.agentId || 'default'}`);
// List all bindings
const bindings = await routing.getBindings();
for (const b of bindings) {
console.log(`${b.channelId} → ${b.agentId}`);
}
// Remove binding
await routing.removeBinding('telegram-trading-group');// Check if tool is allowed for agent
const allowed = routing.isToolAllowed('trading', 'web-search');
console.log(`web-search allowed for trading: ${allowed}`);
// Get allowed tools for agent
const tools = routing.getAllowedTools('trading');
console.log(`Trading agent tools: ${tools.join(', ')}`);
// Update tool policy
routing.setToolPolicy('trading', {
allow: ['execute', 'portfolio', 'futures'],
deny: ['web-search', 'browser'],
});| Agent | Model | Purpose | Tools |
|---|---|---|---|
| main | Sonnet | General assistant | All |
| trading | Haiku | Fast order execution | Execute, Portfolio |
| research | Opus | Deep analysis | Search, Fetch, News |
| alerts | Haiku | Notifications | Alerts, Feeds |
Messages are routed based on:
{
trading: [/buy|sell|order|position|close/i],
research: [/analyze|research|explain|why/i],
alerts: [/alert|notify|when|watch/i],
}| Category | Tools |
|---|---|
| Execution | execute, portfolio, markets |
| Data | feeds, news, web-search, web-fetch |
| Crypto | solana, evm, bridge |
| System | files, browser, docker |
Each agent can have isolated workspace:
routing.addAgent({
id: 'research',
workspace: {
directory: '/tmp/research',
allowedPaths: ['/tmp/research/**'],
sandboxed: true,
},
});e71a5f6
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.