OverviewHistoryStatsSecurity
npx skills add ...
Documentation
SKILL.md
npx skills add openai/plugins --skill search-company-knowledge
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.
npx skills add openai/plugins --skill search-company-knowledge
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
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.
Follow this 5-step process to provide comprehensive, well-cited answers:
Extract the core search terms from the user's question.
Examples:
Consider:
Search across all available knowledge sources simultaneously for comprehensive coverage.
Use the search tool (Rovo Search) to search across Confluence and Jira at once:
When to use:
Example:
This returns results from both Confluence pages and Jira issues.
Use searchConfluenceUsingCql when specifically searching Confluence:
When to use:
Example CQL patterns:
Use searchJiraIssuesUsingJql when specifically searching Jira:
When to use:
Example JQL patterns:
For most queries, use this sequence:
search (cross-system) - always try this firstAfter identifying relevant sources, fetch full content for comprehensive answers.
When search results reference Confluence pages:
Returns: Full page content in Markdown format
When to fetch:
When search results reference Jira issues:
Returns: Full issue details including description, comments, status
When to fetch:
Fetch in this order:
Don't fetch everything - be selective based on relevance to user's question.
Combine information from multiple sources into a coherent answer.
Structure your answer:
Direct Answer First
Detailed Explanation
Source Attribution
Highlight Discrepancies
Provide Context
Pattern 1: Multiple sources agree
Pattern 2: Sources provide different aspects
Pattern 3: Conflicting information
Pattern 4: Incomplete information
Always include links to source materials so users can explore further.
For Confluence pages:
For Jira issues:
Complete citation section:
Do:
Don't:
Good results:
Questionable results:
When results are poor:
If searches return no results:
If search returns 50+ results:
If the user's question is vague:
If you find information is old:
If search returns inaccessible content:
User: "What are Stratus minions?"
Process:
search(cloudId="...", query="Stratus minions")Answer:
User: "How long is our session timeout?"
Process:
Answer:
User: "Explain our deployment process"
Process:
Answer:
✅ 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
❌ 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
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:
Primary tool: search(cloudId, query) - Use this first, always
Follow-up tools:
getConfluencePage(cloudId, pageId, contentFormat) - Get full page contentgetJiraIssue(cloudId, issueIdOrKey) - Get full issue detailssearchConfluenceUsingCql(cloudId, cql) - Targeted Confluence searchsearchJiraIssuesUsingJql(cloudId, jql) - Targeted Jira searchAnswer structure:
Remember:
text ~ "Stratus minions"
summary ~ "authentication" AND type = Bug
text ~ "deployment" AND created >= -90dgetConfluencePage(
cloudId="...",
pageId="[page ID from search results]",
contentFormat="markdown"
)getJiraIssue(
cloudId="...",
issueIdOrKey="PROJ-123"
)Stratus minions are background worker processes that handle async tasks.
According to the Confluence documentation, they process jobs from the queue and
can be scaled horizontally. This is confirmed by several Jira tickets (PROJ-145,
PROJ-203) which discuss minion configuration and scaling strategies.The billing system has two main components:
**Payment Processing** (from Confluence "Billing Architecture" page)
- Handles credit card transactions
- Integrates with Stripe API
- Runs nightly reconciliation
**Invoice Generation** (from Jira PROJ-189)
- Creates monthly invoices
- Note: Currently has a bug where tax calculation fails for EU customers
- Fix planned for Q1 2024There is conflicting information about the authentication timeout:
- **Official Documentation** (Confluence) states: 30-minute session timeout
- **Implementation Reality** (Jira PROJ-456, filed Oct 2023): Actual timeout is
15 minutes due to load balancer configuration
- **Status:** Engineering team aware, fix planned but no timeline yet
Current behavior: Expect 15-minute timeout despite docs saying 30 minutes.Based on available documentation:
[What we know about deployment process from Confluence and Jira]
However, I couldn't find information about:
- Rollback procedures
- Database migration handling
You may want to check with the DevOps team or search for additional documentation.**Source:** [Page Title](https://yoursite.atlassian.net/wiki/spaces/SPACE/pages/123456)**Related Tickets:**
- [PROJ-123](https://yoursite.atlassian.net/browse/PROJ-123) - Brief description
- [PROJ-456](https://yoursite.atlassian.net/browse/PROJ-456) - Brief description## Sources
**Confluence Documentation:**
- [Stratus Architecture Guide](https://yoursite.atlassian.net/wiki/spaces/DOCS/pages/12345)
- [Minion Configuration](https://yoursite.atlassian.net/wiki/spaces/DEVOPS/pages/67890)
**Jira Issues:**
- [PROJ-145](https://yoursite.atlassian.net/browse/PROJ-145) - Minion scaling implementation
- [PROJ-203](https://yoursite.atlassian.net/browse/PROJ-203) - Performance optimization
**Additional Resources:**
- [Internal architecture doc link if found]I searched across Confluence and Jira but couldn't find information about "[topic]".
This could mean:
- The concept hasn't been documented yet
- It might be called something else (can you provide alternative names?)
- Documentation might be in a different system I don't have access to
Would you like me to:
1. Try searching with different terms?
2. Search for related concepts?
3. Look for mentions in recent Jira tickets?I found information about several topics related to "[term]":
1. [Topic A] - from Confluence page X
2. [Topic B] - from Jira tickets Y, Z
3. [Topic C] - from documentation W
Which aspect are you most interested in?I found documentation about [topic], but note that it's from [date] and may be outdated.
[Provide the information anyway]
You may want to verify this is still current, especially if it's from more than
a year ago.Search results mention [topic] in the following locations, but I don't have
access to view the full content:
- Confluence page: [title] (Space: [SPACE])
- Jira issue: PROJ-123
You may need to access these directly or check your permissions.Stratus minions are background worker processes that handle asynchronous task
processing in the Stratus system.
**Key Characteristics:**
- Run independently from web servers
- Process jobs from a Redis queue
- Can be scaled horizontally for increased throughput
- Handle tasks like email sending, report generation, and data processing
**Architecture:**
According to the Stratus Architecture documentation, minions follow a
worker-queue pattern where:
1. Web application enqueues tasks
2. Minions poll the queue for work
3. Tasks are processed asynchronously
4. Results are stored in the database
**Implementation Notes:**
From Jira ticket PROJ-203, the current deployment runs 5 minion instances,
with plans to scale to 10 for handling increased load.
## Sources
- [Stratus Architecture Guide](link)
- [PROJ-203](link) - Minion scaling implementationThere is a discrepancy between documented and actual behavior:
**Official Documentation** (Security Guidelines):
Session timeout is configured for 30 minutes of inactivity.
**Actual Behavior** (PROJ-456, reported Oct 2023):
Users are being logged out after 15 minutes due to a load balancer configuration
that overrides the application setting.
**Current Status:**
The engineering team is aware of this issue. The load balancer timeout needs to
be adjusted to match the application setting. No fix timeline has been set.
**Recommendation:** Plan for 15-minute timeout until this is resolved.
## Sources
- [Security Guidelines](link) - Official documentation
- [PROJ-456](link) - Timeout discrepancy bug reportBased on available documentation, here's what I found about the deployment process:
**Build Phase** (from Confluence "CI/CD Guide"):
1. Code pushed to main branch triggers GitHub Actions
2. Automated tests run (unit, integration)
3. Docker image built and pushed to registry
**Deployment Phase** (from Jira PROJ-789):
4. Staging deployment happens automatically
5. Manual approval required for production
6. Blue-green deployment strategy used
**Gaps in Documentation:**
I couldn't find documented information about:
- Rollback procedures
- Database migration handling
- Post-deployment verification steps
These details may exist in tribal knowledge or need to be documented.
## Sources
- [CI/CD Guide](link)
- [PROJ-789](link) - Deployment pipeline implementation
Would you like me to search for more specific aspects of deployment?