signal-extraction

Extract structured signals from text and route them to specialized butlers.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Tzeusy/butlers --skill signal-extraction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: signal-extraction
Source: https://github.com/Tzeusy/butlers/tree/main/roster/switchboard/.agents/skills/signal-extraction
Command: npx skills add https://github.com/Tzeusy/butlers --skill signal-extraction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of identifying and extracting specific pieces of information (signals) from messages and directing them to the appropriate specialist butlers for action.

Core Features & Use Cases

  • Structured Data Extraction: Parses messages to find predefined types of signals (e.g., contact information, symptoms).
  • Targeted Routing: Ensures extracted signals are sent to the correct butler designed to handle them.
  • Use Case: When a customer support message comes in, this skill can extract the customer's name, product mentioned, and the issue type, then route each piece of information to the 'CRM Butler' and 'Support Butler' respectively.

Quick Start

Use the signal-extraction skill to extract signals from the following message.

Frequently Asked Questions about signal-extraction

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

FAQPage Schema
How do I extract structured data from unstructured text for routing?

Structured data extraction parses unstructured messages to identify predefined signal types, confidence levels, and target tool calls, enforcing strict JSON output for deterministic routing to specialized butlers.

What is signal routing in a multi-butler workflow?

Signal routing in a multi-butler workflow directs extracted structured data to the correct specialist butler designed to handle that specific signal type, facilitating coordinated processing across different tools.

How do I parse customer support messages to route information to different tools?

Parsing customer support messages extracts predefined signals like contact information and issue types, then routes each piece of structured data to the appropriate registered butler schema for action.

Does signal extraction enforce strict JSON output for deterministic processing?

Signal extraction enforces strict JSON output adhering to registered butler schemas, ensuring deterministic processing by providing structured data that downstream tools can reliably consume.

Can I use this for extracting multiple signal types from a single message?

Extracting multiple signal types from a single message is supported by identifying different predefined information categories, evaluating their confidence levels, and routing each to the appropriate target tool call simultaneously.