Airweave Search
Use this skill to effectively search and retrieve context from Airweave collections, whether answering questions or gathering context to complete tasks.
When to Search
Search when the user:
- Asks about data in their connected apps ("What did we discuss in Slack about...")
- Needs to find documents, messages, issues, or records
- Asks factual questions about their workspace ("Who is responsible for...", "What's our policy on...")
- References specific tools by name ("in Notion", "on GitHub", "in Jira")
- Needs recent information you don't have in your training
- Needs you to check app data for context to complete a task ("check our Notion docs", "look at the Jira ticket", "see what we decided in Slack")
Don't search when:
- User asks general knowledge questions (use your training)
- User is asking how to SET UP Airweave (use
airweave-setup skill instead)
- User already provided all needed context in the conversation
- The question is about Airweave itself, not data within it
Search Modes
Airweave provides three search modes. Choose based on user intent:
| Mode |
When to Use |
Speed |
instant |
Simple lookups, exact term matching, browsing |
Fastest |
classic |
Most searches — AI generates an optimized search plan |
Fast |
agentic |
Complex questions requiring reasoning, multi-step retrieval |
Slower, highest quality |
Mode Selection Guide
| User Intent |
Mode |
| Quick document lookup |
instant |
| Finding specific information |
classic (default) |
| General topic exploration |
classic |
| "Summarize", "analyze", "compare" |
agentic |
| Complex multi-source questions |
agentic |
| Simple keyword search |
instant with retrieval_strategy: "keyword" |
Query Formulation
Extract Key Concepts
Turn user intent into effective search queries:
| User Says |
Search Query |
| "What did Sarah say about the launch?" |
"Sarah product launch" |
| "Find the API documentation" |
"API documentation" |
| "Any bugs reported this week?" |
"bug report issues" |
| "What's our refund policy?" |
"refund policy customer" |
Query Tips
- Use natural language - Airweave uses semantic search, not keyword matching
- Include context - "pricing feedback" is better than just "pricing"
- Be specific but not too narrow - Start moderately specific, broaden if no results
- Avoid filler words - Skip "please find", "can you search for"
Parameter Quick Reference
| Parameter |
Values |
When to Use |
mode |
instant/classic/agentic |
instant for speed, classic for most searches, agentic for complex reasoning |
limit |
1-1000 |
Lower (5-10) for quick answers, higher (20-50) for exploration |
offset |
0+ |
Pagination (instant/classic only) |
retrieval_strategy |
hybrid/neural/keyword |
Instant mode only: keyword for exact terms, neural for concepts, hybrid (default) for both |
thinking |
boolean |
Agentic mode only: enable extended reasoning for complex queries |
See PARAMETERS.md for detailed guidance.
Handling Results
Interpreting Scores
Results include a relevance_score field:
| Score |
Meaning |
Action |
| 0.85+ |
Highly relevant |
Use confidently |
| 0.70-0.85 |
Likely relevant |
Use with context |
| 0.50-0.70 |
Possibly relevant |
Mention uncertainty |
| Below 0.50 |
Weak match |
Consider rephrasing query |
Understanding Result Structure
Each result contains:
name — Document/entity title
textual_representation — The full text content
breadcrumbs — Hierarchy path (e.g., Workspace > Channel > Message)
airweave_system_metadata.source_name — Source app (e.g., "Slack", "Notion")
web_url — Link back to the original item
created_at / updated_at — Timestamps
Synthesizing Answers
When presenting results to users:
- Lead with the answer - Don't start with "I found 5 results"
- Cite sources - Mention where info came from ("According to your Slack conversation...")
- Use breadcrumbs - Reference the hierarchy path for context ("In the Engineering > API Design channel...")
- Synthesize, don't dump - Combine relevant parts into coherent response
- Acknowledge gaps - If results don't fully answer, say so
Handling No/Poor Results
If search returns no results or low-quality matches:
- Try a different mode - Switch from
instant to classic, or classic to agentic
- Broaden the query - Remove specific terms, use more general concepts
- Try different phrasing - Rephrase using synonyms or related terms
- Increase limit - Fetch more results to find relevant matches
- Check source availability - The data source might not be connected
- Ask for clarification - User might have more context to share
Finding the Search Tool
Airweave MCP tools follow the naming pattern search-{collection-name}. Look for tools matching this pattern in your available MCP tools.
Examples:
search-acmes-slack-k8v2x1
search-acmes-notion-p3m9q7
search-acmes-jira-w5n4r2
If no Airweave search tool is available:
- The user may not have Airweave MCP configured
- Ask if they have Airweave set up and connected to their AI assistant
- Suggest using the
airweave-setup skill for configuration help
Multiple collections:
If multiple search-* tools are available, choose based on the collection name and the user's request. If unclear which to use, ask the user or try the most general-sounding one first.
Calling the Search Tool
Use the search-{collection} MCP tool with your chosen parameters:
search-acmes-slack-k8v2x1({
query: "customer feedback pricing",
mode: "classic",
limit: 10
})
search-acmes-notion-p3m9q7({
query: "API authentication docs",
mode: "instant",
retrieval_strategy: "hybrid"
})
search-acmes-jira-w5n4r2({
query: "What decisions were made about the refund policy?",
mode: "agentic"
})
Examples
See EXAMPLES.md for complete conversation examples showing effective search patterns.
1---2name: airweave-search3description: Search and retrieve context from Airweave collections. Use when users ask about their data in connected apps (Slack, GitHub, Notion, Jira, Confluence, Google Drive, Salesforce, databases, etc.), need to find documents or information from their workspace, want answers based on their company data, or need you to check app data for context to complete a task.4---56# Airweave Search78Use this skill to effectively search and retrieve context from Airweave collections, whether answering questions or gathering context to complete tasks.910## When to Search1112**Search when the user:**13- Asks about data in their connected apps ("What did we discuss in Slack about...")14- Needs to find documents, messages, issues, or records15- Asks factual questions about their workspace ("Who is responsible for...", "What's our policy on...")16- References specific tools by name ("in Notion", "on GitHub", "in Jira")17- Needs recent information you don't have in your training18- Needs you to check app data for context to complete a task ("check our Notion docs", "look at the Jira ticket", "see what we decided in Slack")1920**Don't search when:**21- User asks general knowledge questions (use your training)22- User is asking how to SET UP Airweave (use `airweave-setup` skill instead)23- User already provided all needed context in the conversation24- The question is about Airweave itself, not data within it2526## Search Modes2728Airweave provides three search modes. Choose based on user intent:2930| Mode | When to Use | Speed |31|------|-------------|-------|32| `instant` | Simple lookups, exact term matching, browsing | Fastest |33| `classic` | Most searches — AI generates an optimized search plan | Fast |34| `agentic` | Complex questions requiring reasoning, multi-step retrieval | Slower, highest quality |3536### Mode Selection Guide3738| User Intent | Mode |39|-------------|------|40| Quick document lookup | `instant` |41| Finding specific information | `classic` (default) |42| General topic exploration | `classic` |43| "Summarize", "analyze", "compare" | `agentic` |44| Complex multi-source questions | `agentic` |45| Simple keyword search | `instant` with `retrieval_strategy: "keyword"` |4647## Query Formulation4849### Extract Key Concepts5051Turn user intent into effective search queries:5253| User Says | Search Query |54|-----------|--------------|55| "What did Sarah say about the launch?" | "Sarah product launch" |56| "Find the API documentation" | "API documentation" |57| "Any bugs reported this week?" | "bug report issues" |58| "What's our refund policy?" | "refund policy customer" |5960### Query Tips61621. **Use natural language** - Airweave uses semantic search, not keyword matching632. **Include context** - "pricing feedback" is better than just "pricing"643. **Be specific but not too narrow** - Start moderately specific, broaden if no results654. **Avoid filler words** - Skip "please find", "can you search for"6667## Parameter Quick Reference6869| Parameter | Values | When to Use |70|-----------|--------|-------------|71| `mode` | instant/classic/agentic | `instant` for speed, `classic` for most searches, `agentic` for complex reasoning |72| `limit` | 1-1000 | Lower (5-10) for quick answers, higher (20-50) for exploration |73| `offset` | 0+ | Pagination (instant/classic only) |74| `retrieval_strategy` | hybrid/neural/keyword | Instant mode only: `keyword` for exact terms, `neural` for concepts, `hybrid` (default) for both |75| `thinking` | boolean | Agentic mode only: enable extended reasoning for complex queries |7677See [PARAMETERS.md](PARAMETERS.md) for detailed guidance.7879## Handling Results8081### Interpreting Scores8283Results include a `relevance_score` field:8485| Score | Meaning | Action |86|-------|---------|--------|87| 0.85+ | Highly relevant | Use confidently |88| 0.70-0.85 | Likely relevant | Use with context |89| 0.50-0.70 | Possibly relevant | Mention uncertainty |90| Below 0.50 | Weak match | Consider rephrasing query |9192### Understanding Result Structure9394Each result contains:95- **`name`** — Document/entity title96- **`textual_representation`** — The full text content97- **`breadcrumbs`** — Hierarchy path (e.g., Workspace > Channel > Message)98- **`airweave_system_metadata.source_name`** — Source app (e.g., "Slack", "Notion")99- **`web_url`** — Link back to the original item100- **`created_at`** / **`updated_at`** — Timestamps101102### Synthesizing Answers103104When presenting results to users:1051061. **Lead with the answer** - Don't start with "I found 5 results"1072. **Cite sources** - Mention where info came from ("According to your Slack conversation...")1083. **Use breadcrumbs** - Reference the hierarchy path for context ("In the Engineering > API Design channel...")1094. **Synthesize, don't dump** - Combine relevant parts into coherent response1105. **Acknowledge gaps** - If results don't fully answer, say so111112### Handling No/Poor Results113114If search returns no results or low-quality matches:1151161. **Try a different mode** - Switch from `instant` to `classic`, or `classic` to `agentic`1172. **Broaden the query** - Remove specific terms, use more general concepts1183. **Try different phrasing** - Rephrase using synonyms or related terms1194. **Increase limit** - Fetch more results to find relevant matches1205. **Check source availability** - The data source might not be connected1216. **Ask for clarification** - User might have more context to share122123## Finding the Search Tool124125Airweave MCP tools follow the naming pattern `search-{collection-name}`. Look for tools matching this pattern in your available MCP tools.126127**Examples:**128- `search-acmes-slack-k8v2x1`129- `search-acmes-notion-p3m9q7`130- `search-acmes-jira-w5n4r2`131132**If no Airweave search tool is available:**133- The user may not have Airweave MCP configured134- Ask if they have Airweave set up and connected to their AI assistant135- Suggest using the `airweave-setup` skill for configuration help136137**Multiple collections:**138If multiple `search-*` tools are available, choose based on the collection name and the user's request. If unclear which to use, ask the user or try the most general-sounding one first.139140## Calling the Search Tool141142Use the `search-{collection}` MCP tool with your chosen parameters:143144```145search-acmes-slack-k8v2x1({146 query: "customer feedback pricing",147 mode: "classic",148 limit: 10149})150```151152```153search-acmes-notion-p3m9q7({154 query: "API authentication docs",155 mode: "instant",156 retrieval_strategy: "hybrid"157})158```159160```161search-acmes-jira-w5n4r2({162 query: "What decisions were made about the refund policy?",163 mode: "agentic"164})165```166167## Examples168169See [EXAMPLES.md](EXAMPLES.md) for complete conversation examples showing effective search patterns.