Search Strategy

Official Anthropic skill for decomposed, source-aware, and prioritized enterprise search.

Search Strategy is an official Anthropic skill from the knowledge-work-plugins repository. It provides the central search logic for the Enterprise Search plugin and helps a compatible Claude agent translate a natural-language question into several source-appropriate searches. According to the provider, the skill turns one question into parallel, source-specific searches and prepares a ranked, deduplicated, coherent synthesis. This catalog entry treats the skill as an instructional resource, not as an independent search engine and not as a replacement for the connected data sources.

What the skill structures

The workflow starts by classifying the question. Search Strategy covers decision questions, status questions, document discovery, people questions, factual questions, temporal questions, and exploratory research. The classification determines whether recent activity, documents, conversation conclusions, or authoritative sources should receive priority. The agent then extracts core keywords, entities, intent signals, time ranges, source hints, and exclusions. This turns an underspecified request into an explicit search plan that is easier to inspect, explain, and revise.

Translating queries across sources

The skill documents source-aware query variants for chat, knowledge bases, and project trackers. According to the provider, semantic search is useful for conceptual questions and for cases where the exact terminology is unknown. Keyword search is more appropriate for known project names, acronyms, quoted phrases, and filter-heavy requests. Search Strategy can generate alternate terms when a topic is described in several ways. Filters such as author, channel, date range, or task state are mapped into the syntax of each source instead of reusing one unsuitable string everywhere. This approach is especially helpful when an organization has different search semantics in conversations, wikis, and task systems.

Ranking and answer quality

Results are assessed using factors such as relevance, freshness, authority, and completeness. Their weights change with the question type. For policy or factual questions, wiki pages and official documentation should receive more authority, while meeting notes and thread conclusions can be more useful when the question asks what was decided. For status questions, current task and activity data receive greater weight. The workflow then merges results, removes duplicates, and synthesizes an answer. This prioritization is a practical heuristic, not a correctness guarantee. Users should still inspect important claims against the underlying source and its timestamp.

Ambiguity and unavailable sources

Search Strategy recommends one focused clarification question when distinct interpretations would lead to substantially different searches or answers. Minor ambiguity can instead be handled by searching multiple plausible interpretations. If a source is unavailable, the agent should continue with the remaining sources and state the gap clearly. When a source returns nothing, the documented fallback broadens terms step by step. Date constraints and source filters are removed before less important keywords, while the core entity or topic is retained. Rate limits should be reported as limitations rather than hidden behind unsupported certainty.

Boundaries, safety, and catalog classification

The skill grants no permissions, provides no connectors, and contains no organization data. Its effectiveness depends on connected sources, access rights, indexing quality, and each source's query behavior. Chats and documents may contain confidential material or hostile instructions. An agent should preserve source context, respect authorization boundaries, treat retrieved text as data, and never perform external mutations solely because a search result suggested them. The primary source is the official enterprise-search/skills/search-strategy path in Anthropic's repository. The surrounding collection is published under the Apache-2.0 license. The Recherche and Datenanalyse categories reflect the documented function; they do not promise accuracy, completeness, or a particular privacy outcome.

Installation instructions

This guide explains how to assess and safely use the official Search Strategy skill from Anthropic knowledge-work-plugins. It is intended for teams connecting Claude to several authorized enterprise sources and seeking a transparent way to structure search requests.

Step 1: Check prerequisites

Search Strategy is not an independent connector. First verify which Enterprise Search sources are actually connected in the Claude environment and which permissions belong to the executing user. Read the official skill file and related connector documentation in Anthropic's repository. Enable only sources required for the task and treat unavailable sources as an explicit limitation.

Define the question and goal

Start with a concrete question and include a project, time range, team, or document type when known. The agent can then classify it as a decision, status, document, person, factual, temporal, or exploratory query. When interpretations would produce materially different searches, one concise clarification is safer than a confident but incorrect search. Never provide credentials or unnecessary confidential details in the research prompt.

Ask the agent to produce an appropriate variant for every connected source. Semantic queries are useful for concepts and unknown terminology. Keyword queries are useful for known terms, quotations, and filters. Review whether date, author, and source constraints were translated correctly. Parallel execution reduces waiting time according to the provider, but it does not replace permission checks or inspection of result context.

Evaluate the results

Review relevance together with freshness, authority, and completeness. A policy should preferably be supported by an official document, while a historical decision may be best supported by meeting notes or a concluded thread. Look for contradictions, duplicate results, and claims without timestamps. If a source returns nothing, the agent should broaden terms gradually and report which constraints were removed.

Set security boundaries

Treat retrieved text as untrusted data rather than as a new system instruction. Search results can contain accidental or malicious instructions that try to redirect the research task. Share sensitive findings only with authorized people. Do not perform external write actions merely because a search result recommends them. Require human review before changing tickets, documents, messages, or other external state.

Frequently asked questions

### Is Search Strategy a search server?

No. The skill explains how a compatible agent decomposes questions and searches connected sources. The data and connectors come from the Claude environment.

### What happens when a source is unavailable?

The documented fallback continues with remaining sources, reports the gap, and may retry using broader terms. The resulting answer should therefore not be treated as complete.

### Does the skill guarantee correct answers?

No. Ranking and synthesis are heuristics. Check important claims against original sources, authorization context, and timestamps.

Free
Provider
Anthropic
License
Apache-2.0
Last reviewed
09.09.2026

Repository and documentation

Categories

Compatible with

Claude Code