Description
Universal Dots Search gives an agent one reliable workflow for questions such as “where did we decide this?”, “find the bug about imports,” or “which row describes that feature?” It interprets the requested scope, searches the appropriate Dots stores, pages bounded result sets, and returns concise matches with durable row handles. When the request is code-oriented, it can connect the answer to repository knowledge rather than treating text search as the only source.
The workflow centralizes query construction and output shaping in a deterministic helper. This prevents each skill from guessing CLI flags or presenting raw result dumps. Search remains read-only, distinguishes absence from truncation, and can narrow by a named Dotabase when the user already knows the store.
Selling Points
- Recovers decisions and prior work without requiring the buyer to remember where they were stored.
- Returns durable handles that can be opened, linked, or passed directly into later workflows.
- Searches across the workspace while still supporting precise store-scoped questions.
- Handles paging and result shaping consistently, reducing false “nothing found” conclusions.
- Bridges conversational discovery with the same Dots knowledge surfaces used by the rest of the platform.
User Story
A product lead remembers deciding how archive behavior should work but cannot recall whether it lives in a lesson, artifact, or specification. They ask the agent to find it. Universal Search translates the request into a bounded workspace search, presents the most relevant rows with citations, and identifies the authoritative decision. The lead walks away with the exact record instead of re-litigating the question.
Extension Surface
This shared feature is automatable. payload/skills/search/SKILL.md makes it invocable from natural requests, while payload/skills/search/scripts/run-search.mjs wraps the Dots search surface with stable paging and output behavior. payload/skills/search/workflows/run-search.md governs scope resolution. The underlying search platform can index many Dotabases, but this plugin workflow does not expose a custom ranking or provider registration point.
Capabilities & Limits
- Searches workspace-wide or within a named Dotabase and returns cited row handles.
- Supports discovery of decisions, bugs, projects, tasks, notes, and other durable knowledge.
- Pages results and reports misses without pretending a truncated response is complete.
- Limit: it does not mutate results, guarantee semantic relevance when the source corpus lacks context, or replace code-graph traversal for impact analysis.
Implementation Map
payload/skills/search/SKILL.mdpayload/skills/search/workflows/run-search.mdpayload/skills/search/scripts/run-search.mjspayload/lib/search.mjs