search-strategy

Decompose questions into parallel source-specific searches and synthesize ranked results.

1|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/zzafergok/arktos --skill search-strategy-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: search-strategy
Source: https://github.com/zzafergok/arktos/tree/main/.agent/skills/search-strategy
Command: npx skills add https://github.com/zzafergok/arktos --skill search-strategy-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Answering questions that span multiple systems (chat, wikis, task trackers, email) is slow and error-prone when done manually, and single-source searches often miss the real answer. This Skill turns one natural language question into coordinated, source-specific searches and merges the evidence into a single coherent answer. ## Core Features & Use Cases - Query Decomposition: Classifies questions by type (decision, status, document, person, factual, temporal, exploratory) and extracts keywords, entities, intent signals, and constraints. - Source-Specific Query Translation: Maps enterprise filters like from:, in:, and after: to the correct syntax for chat, knowledge base, and project tracker sources, choosing semantic or keyword search appropriately. - Ranking and Synthesis: Scores results by relevance, freshness, authority, and completeness, then deduplicates and merges them into one answer. - Use Case: A user asks "What did we decide about the API migration timeline?" The Skill runs parallel searches across chat, the wiki, and the task tracker, prioritizes thread conclusions and meeting notes, and returns a synthesized decision summary. ## Quick Start Ask the assistant to find what was decided about a project across chat, the wiki, and the task tracker, and have it synthesize the results into one answer.

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 sources like chat, wiki, and task trackers at once?▼

Decompose the question into source-specific sub-queries and execute them in parallel, then merge, rank, and deduplicate the results. Total search time should approximate the slowest single source, not the sum of all sources.

When should I use semantic search versus keyword search?▼

Use semantic search for conceptual or exploratory questions where exact keywords are unknown. Use keyword search for known terms, project names, acronyms, exact quoted phrases, and filter-heavy queries with from:, in:, or after: constraints.

How do I rank search results from different enterprise sources?▼

Score results on keyword match, freshness, authority, and completeness, weighting factors by query type. Apply an authority hierarchy: official docs rank highest for factual questions, while task trackers lead for status questions.

What should I do when a search source returns no results?▼

Broaden the query by removing constraints in order: date filters first, then source filters, then less important keywords, keeping only core entity terms. If a source is unavailable, skip it and note the gap in the final answer.

When is it appropriate to ask a clarifying question before searching?▼

Ask one focused clarifying question only when genuinely distinct interpretations would produce very different results or change which sources to search. Do not ask when minor ambiguity can be resolved by returning results from multiple interpretations.