Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →zzafergok/search-strategy
Query decomposition and multi-source search orchestration. Breaks natural language questions into targeted searches per source, translates queries into source-specific syntax, ranks results by relevance, and handles ambiguity and fallback strategies.
Passed 19 of 22 test cases with the skill, and 13 of 22 without it.
and 9 more in the full report
7 fixed12 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to construct a task search payload for our project tracking tool when searching for open tasks assigned to Sarah created after January 1st, 2025. A teammate suggested using `filter_user` and `created_after`. What exact parameter key should be mapped for the date filter, and how should completion status be restricted for active task searches?
| Checked | Without skill | With skill |
|---|---|---|
| Maps the date constraint using the modified_on_after parameter. | Missed | Passed |
| Includes completed set to false for active status queries. | Passed | Passed |
The instructions your model reads when the skill loads.
First inspect which search tools and connected sources are actually available. Treat the source syntax examples below as patterns, not as guaranteed tool names.
The core intelligence behind enterprise search. Transforms a single natural language question into parallel, source-specific searches and produces ranked, deduplicated results.
Turn this:
"What did we decide about the API migration timeline?"
Into targeted searches across every connected source:
~~chat: "API migration timeline decision" (semantic) + "API migration" in:#engineering after:2025-01-01
~~knowledge base: semantic search "API migration timeline decision"
~~project tracker: text search "API migration" in relevant workspace
Then synthesize the results into a single coherent answer.
Classify the user's question to determine search strategy:
| Query Type | Example | Strategy |
|---|---|---|
| Decision | "What did we decide about X?" | Prioritize conversations (~~chat, email), look for conclusion signals |
| Status | "What's the status of Project Y?" | Prioritize recent activity, task trackers, status updates |
| Document | "Where's the spec for Z?" | Prioritize Drive, wiki, shared docs |
| Person | "Who's working on X?" | Search task assignments, message authors, doc collaborators |
| Factual | "What's our policy on X?" | Prioritize wiki, official docs, then confirmatory conversations |
| Temporal | "When did X happen?" | Search with broad date range, look for timestamps |
| Exploratory | "What do we know about X?" | Broad search across all sources, synthesize |
test cases passed, vs 13 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.