Search Strategy

anthropics/knowledge-work-pluginsOfficial

This is the query routing layer that turns "what did we decide about the API migration?" into parallel, source-specific searches across Slack, wikis, task trackers, and other connected tools. It classifies query intent (decision vs. status vs. document lookup), extracts keywords and constraints, then translates them into each source's native syntax (semantic search for Slack, keyword filters for wikis, task parameters for project trackers). Results get ranked by relevance weights that shift based on query type: fresh chat messages win for status questions, official docs win for policy questions. The fallback strategy is smart: it broadens queries when results are thin and runs everything in parallel so you're waiting on the slowest source, not all of them sequentially.

skills.sh installs: 5.4K
GitHub stars: 35.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add anthropics/knowledge-work-plugins --skill search-strategy --agent claude-code

Installs into .claude/skills of the current project.

Files

Search Strategy

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

The core intelligence behind enterprise search. Transforms a single natural language question into parallel, source-specific searches and produces ranked, deduplicated results.

The Goal

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.