search-company-knowledge

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 6f7e14ad6755 · 20 Oct 2026Report an issue or request a re-scan

• Publisheratlassian GitHub organizationOwner of the repository this skill is read from
• Source folderatlassian/atlassian-mcp-server/skills/search-company-knowledgeThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdict6f7e14ad6755A new audit runs when the source changes
• Repository statusNot archivedLast push 9 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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,…

---
name: search-company-knowledge
description: "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, or technical concepts, (2) Search internal documentation, knowledge base, company docs, or our docs, (3) Explain what something is, how it works, or look up information, or (4) Synthesize information from multiple sources. Searches in parallel and provides cited answers."
---

# 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:

```
search(
  cloudId="...",
  query="[extracted search terms]"
)
```

**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:**
```
search(
  cloudId="...",
  query="Stratus minions"
)
```

This returns results from both Confluence pages and Jira issues.

#### Option B: Targeted Confluence Search

Use **`searchConfluence`** when specifically searching Confluence:

```
searchConfluence(
  cloudId="...",
  cql="text ~ 'search terms' OR title ~ 'search terms'"
)
```

**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:**
```
text ~ "Stratus minions"
text ~ "authentication" AND type = page
title ~ "deployment guide"
```

#### Option C: Targeted Jira Search

Use **`searchJiraIssuesUsingJql`** when specifically searching Jira:

```
searchJiraIssuesUsingJql(
  cloudId="...",
  jql="text ~ 'search terms' OR summary ~ 'search terms'"
)
```

**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:**
```
text ~ "Stratus minions"
summary ~ "authentication" AND type = Bug
text ~ "deployment" AND created >= -90d
```

#### 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:

```
getConfluenceContent(
  cloudId="...",
  content_id="[page ID from search results]",
  content_format="markdown",
  detail="full"
)
```

**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:

```
getJiraIssue(
  cloudId="...",
  issueIdOrKey="PROJ-123"
)
```

**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:

```
executeRead(   # or execute(...) if your client exposes a single execute tool
  name="listJiraIssueComments",
  cloudId="...",
  inputs={"issueIdOrKey": "PROJ-123", "maxResults": 50}
)
```

**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 pa

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/atlassian/atlassian-mcp-server
git -C atlassian-mcp-server checkout 6f7e14ad6755

Works in

1. 2026-10-20
   ✓SAFE B 89 / 100

   first audit · source 6f7e14ad6755

Questions about search-company-knowledge

• github.com/atlassian/atlassian-mcp-server/tree/main/skills/searc — the audited source at commit 6f7e14ad6755 and every finding aboveObserved · 20 Oct 2026

Spotted something wrong? Report a correction · Methodology