STOP. READ THIS ENTIRE SKILL.MD BEFORE CALLING ANY ENDPOINT.

/extract-entities

Extract control IDs, domain phrases, control metadata, relationship edges, interface commands, dataset/source mentions, and taxonomy tags from any question text. The extraction result defines the shape of the request before routing, gates, or LLM calls run.

Always-On Request Gate

Run /extract-entities on every user request in chat and project-agent systems. It is deterministic and cheap, so it should run before routing to $ask, $create-figure, $create-evidence-case, $analytics, or project-specific subagents.

The result should be persisted with the run as entity_context.json so failures are debuggable. Downstream skills must read this structured context instead of regex-parsing the prompt again.

For figure/data requests, extraction should identify: