Search across company knowledge bases (Confluence, Jira, internal docs) to find and explain internal concepts, processes, and technical details. When an agent needs to: (1) Find or search for information about systems, terminology, processes, deployment, authentication, infrastructure, architecture,

Search Company Knowledge Keywords find information, search company knowledge, look up, what is, explain, company docs, internal documentation, Confluence search, Jira search, our documentation, internal knowledge, knowledge base, search for, tell me about, get information about, company systems, terminology, find everything about, what do we know about, deployment, authentication, infrastructure, processes, procedures, how to, how does, our systems, our processes, internal systems, company processes, technical documentation, engineering docs, architecture, configuration, search our docs, search internal docs, find in our docs Overview Search across siloed company knowledge systems (Confluence, Jira, internal documentation) to find comprehensive answers to questions about internal concepts, systems, and terminology. This skill performs parallel searches across multiple sources and synthesizes results with proper citations. Use this skill when: Users ask about internal company knowledge that might be documented in Confluence pages, Jira tickets, or internal documentation. Workflow Follow this 5 step process to provide comprehensive, well cited answers: Step 1: Identify Search Query Extract the core search terms from the user's question. Examples: User: "Find everything about Stratus minions" → Search: "Stratus minions" User: "What do we know about the billing system?" → Search: "billing system" User: "Explain our deployment process" → Search: "deployment process" Consider: Main topic or concept Any specific system/component names Technical terms or jargon Step 2: Execute Parallel Search Search across all available knowledge sources simultaneously for comprehensive coverage. Option A: Cross System Search (Recommended First) Use the search tool (Rovo Search) to search across Confluence and Jira at once: When to use: Default approach for most queries When you don't know which system has the information Fastest way to get results from multiple sources search is semantic search — pass natural language, never query syntax. CQL or JQL in query will silently return poor results instead of erroring. Use searchConfluence (CQL) or searchJiraIssuesUsingJql (JQL) when you need a structured filter such as a title or type match. Example: This returns results from both Confluence pages and Jira issues. Option B: Targeted Confluence Search Use searchConfluence when specifically searching Confluence: When to use: User specifically mentions "in Confluence" or "in our docs" Cross system search returns too many Jira results Looking for documentation rather than tickets Example CQL patterns: Option C: Targeted Jira Search Use searchJiraIssuesUsingJql when specifically searching Jira: When to use: User mentions "tickets", "issues", or "bugs" Looking for historical problems or implementation details Cross system search returns mostly documentation Example JQL patterns: Search Strategy For most queries, use this sequence: 1. Start with search (cross system) always try this first 2. If results are unclear, follow up with targeted searches 3. If results mention specific pages/tickets, fetch them for details Step 3: Fetch Detailed Content After identifying relevant sources, fetch full content for comprehensive answers. For Confluence Pages When search results reference Confluence pages: Returns: Full page content in Markdown format When to fetch: Search result snippet is too brief Need complete context Page seems to be the primary documentation For Jira Issues When search results reference Jira issues: Returns: Full issue details including description and status. getJiraIssue does not return comment bodies — it only reports how many comments the issue has. When the discussion matters, fetch the comments separately. listJiraIssueComments is not a primary tool, so run it through execute , and paginate with startAt / maxResults until you have the comments you need: When to fetch: Need to understand a reported bug or issue Search result doesn't show full context Issue contains important implementation notes Prioritization Fetch in this order: 1. Official documentation pages (Confluence pages with "guide", "documentation", "overview" in title) 2. Recent/relevant issues (Jira tickets that are relevant and recent) 3. Additional context (related pages mentioned in initial results) Don't fetch everything be selective based on relevance to user's question. Step 4: Synthesize Results Combine information from multiple sources into a coherent answer. Synthesis Guidelines Structure your answer: 1. Direct Answer First Start with a clear, concise answer to the question "Stratus minions are..." 2. Detailed Explanation Provide comprehensive details from all sources Organize by topic, not by source 3. Source Attribution Note where each piece of information comes from Format: "According to [source], ..." 4. Highlight Discrepancies If sources conflict, note it explicitly Example: "The Confluence documentation states X, however Jira ticket PROJ 123 indicates that due to bug Y, the behavior is actually Z" 5. Provide Context Mention if information is outdated Note if a feature is deprecated or in development Synthesis Patterns Pattern 1: Multiple sources agree Pattern 2: Sources provide different aspects Pattern 3: Conflicting information Pattern 4: Incomplete information Step 5: Provide Citations Always include links to source materials so users can explore further. Citation Format For Confluence pages: For Jira issues: Complete citation section: Search Best Practices Effective Search Terms Do: ✅ Use specific technical terms: "OAuth authentication flow" ✅ Include system names: "Stratus minions" ✅ Use acronyms if they're common: "API rate limiting" ✅ Try variations if first search fails: "deploy process" → "deployment pipeline" Don't: ❌ Be too generic: "how things work" ❌ Use full sentences: Use key terms instead ❌ Include filler words: "the", "our", "about" Search Result Quality Good results: Recent documentation (< 1 year old) Official/canonical pages (titled "Guide", "Documentation", "Overview") Multiple sources confirming same information Detailed implementation notes Questionable results: Very old tickets ( 2 years, may be outdated) Duplicate or conflicting information Draft pages or work in progress docs Personal pages (may not be official) When results are poor: Try different search terms Expand search to include related concepts Search for specific error messages or codes Ask user for more context Handling Common Scenarios Scenario 1: No Results Found If searches return no results: Scenario 2: Too Many Results If search returns 50+ results: Focus on most recent and most relevant (top 10 15) Prioritize official documentation over random tickets Group similar results: "I found 15 tickets related to authentication bugs..." Offer to narrow search: "Would you like me to focus on [specific aspect]?" Scenario 3: Ambiguous Query If the user's question is vague: Scenario 4: Outdated Information If you find information is old: Scenario 5: Restricted/Private Content If search returns inaccessible content: Examples Example 1: Clear Documentation Available User: "What are Stratus minions?" Process: 1. Search: search(cloudId="...", query="Stratus minions") 2. Find: Confluence page "Stratus Architecture" + 3 Jira tickets 3. Fetch: Get full Confluence page content 4. Synthesize: Combine architectural overview with implementation details from tickets 5. Cite: Provide links to all sources Answer: Example 2: Conflicting Information User: "How long is our session timeout?" Process: 1. Search across Confluence and Jira 2. Find: Docs say 30 min, but ticket reports actual timeout is 15 min 3. Fetch both sources for complete context 4. Clearly note the discrepancy Answer: Example 3: Partial Information User: "Explain our deployment process" Process: 1. Search finds some information but not complete 2. Synthesize what is available 3. Note gaps in documentation Answer: Tips for High Quality Answers Do: ✅ Always search before answering (don't rely on general knowledge) ✅ Cite all sources with links ✅ Note discrepancies explicitly ✅ Mention when information is old ✅ Provide context and examples ✅ Structure answers clearly with headers ✅ Link to related documentation Don't: ❌ Assume general knowledge applies to this company ❌ Make up information if search returns nothing ❌ Ignore conflicting information ❌ Quote entire documents (summarize instead) ❌ Overwhelm with too many sources (curate top 5 10) ❌ Forget to fetch details when snippets are insufficient When NOT to Use This Skill This skill is for internal company knowledge only . Do NOT use for: ❌ General technology questions (use your training knowledge) ❌ External documentation (use web search) ❌ Company agnostic questions ❌ Questions about other companies ❌ Current events or news Examples of what NOT to use this skill for: "What is machine learning?" (general knowledge) "How does React work?" (external documentation) "What's the weather?" (not knowledge search) "Find a restaurant" (not work related) Quick Reference Primary tool: search(cloudId, query) Use this first, always Follow up tools: getConfluenceContent(cloudId, content id, content format, detail="full") Get full page content getJiraIssue(cloudId, issueIdOrKey) Get full issue details searchConfluence(cloudId, cql) Targeted Confluence search searchJiraIssuesUsingJql(cloudId, jql) Targeted Jira search Answer structure: 1. Direct answer 2. Detailed explanation 3. Source attribution 4. Discrepancies (if any) 5. Citations with links Remember: Parallel search Sequential search Synthesize, don't just list Always cite sources Note conflicts explicitly Be clear about gaps in documentation

search-company-knowledge