search-strategy

Decompose natural language questions into parallel source-specific searches across connected data stores.

704|58|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/openyak/desktop --skill search-strategy-openyak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-strategy
Source: https://github.com/openyak/desktop/tree/main/backend/app/data/plugins/enterprise-search/skills/search-strategy
Command: npx skills add https://github.com/openyak/desktop --skill search-strategy-openyak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down natural language questions into targeted, source-specific searches across multiple connected data sources, enabling faster, more relevant results.

Core Features & Use Cases

  • Query Decomposition: Splits a user question into per-source sub-queries.
  • Source Translation & Ranking: Translates to source syntax, executes parallel searches, and ranks deduplicated results by relevance.
  • Ambiguity Handling & Fallbacks: Detects uncertainty and applies fallback strategies to ensure useful answers.
  • Use Case: When you need a comprehensive answer drawn from chat, knowledge bases, project trackers, and documents across sources.

Quick Start

Use this skill to decompose a natural language question and run parallel searches across all connected sources.

Frequently Asked Questions about search-strategy

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

FAQPage Schema
How do I search across multiple data sources from a single natural language query?

Multi-source search decomposes a natural language query into parallel, source-specific sub-queries, executing them across connected data stores and synthesizing ranked, deduplicated results into a single coherent answer.

What's the best way to handle search ambiguity across chat logs, knowledge bases, and project trackers?

Ambiguity handling detects uncertainty in cross-source queries and applies fallback strategies to ensure useful answers. It orchestrates source-specific translation and ranking across documents and trackers to resolve conflicting or vague information.

How does query decomposition work for enterprise search across connected data stores?

Query decomposition splits a natural language question into targeted, per-source sub-queries. It translates each sub-query into the specific syntax required by chat logs, knowledge bases, and trackers before running parallel searches.

Can I run parallel searches across documents and project trackers without writing separate queries for each source?

Yes, source translation automatically converts a single user question into the correct syntax for each connected data store. It executes parallel searches across documents and trackers, then deduplicates and ranks the combined results.

Why does my multi-source search return duplicate or conflicting results from different knowledge bases?

Multi-source search applies deduplication and relevance ranking to synthesized results from parallel searches. If duplicates persist, the ambiguity handling and fallback strategies may need adjustment to better resolve conflicting source data.

Do I need to connect my data sources before using multi-source search and query decomposition?

Yes, connected data sources are required. The skill orchestrates parallel, source-specific searches across chat logs, knowledge bases, project trackers, and documents by translating a single query into the appropriate syntax for each connected store.