Query builder
Design query families so a topic is covered from several angles, then validate the queries before execution.
When to use
- A single query is unlikely to surface the full picture.
- You know the intent (find exact text, technical docs, contradictions, historical record) but not the best phrasing.
- You want site/filetype-constrained variants of a topic.
Tools used
build_search_query— produce a family (nvariants) from atopic, with an optionalfamilyintent,targettype,site, andfiletype.validate_search_query— check a query for balanced quotes/operators and structural validity before burning a search call.
Query families
discovery · exact · technical · implementation · source_specific ·
verification · contradiction · historical · current · alternative
Workflow
- Fix the topic; pick the family(ies) that match the research intent.
build_search_query→ review variants, keep the strong ones.validate_search_queryeach survivor; drop invalid forms.- Hand validated queries to
web-search/search-operators.
Input schema
{ "topic": "str", "family": "str", "n": "int", "target": "str", "site": "str", "filetype": "str" }
Output schema
{ "queries": "list[str]" }
Security
Queries are neutral; what they retrieve is not. Route retrieved content through
source-analysis before weighing it.
Related skills
search-operators, query-expansion, query-refinement, web-search