context-fetcher

Search GitHub, Confluence, and Slack for incident-related configuration, documentation, and messages.

9|10|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/redhat-et/rhdp-rca-plugin --skill context-fetcher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-fetcher
Source: https://github.com/redhat-et/rhdp-rca-plugin/tree/main/skills/context-fetcher
Command: npx skills add https://github.com/redhat-et/rhdp-rca-plugin --skill context-fetcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide investigators and on-call engineers with a fast, consolidated way to find related configuration, code, documentation, and team messages for a job or incident so they can reduce time-to-diagnosis and avoid manual searches across multiple platforms.

Core Features & Use Cases

  • Cross-platform search: Query GitHub repositories, Atlassian Confluence pages, and Slack channels to find configuration files, runbooks, code references, and relevant messages.
  • Targeted retrieval: Locate specific config and IaC files (YAML, JSON, Helm, Terraform, Ansible) and fetch file contents for quick inspection.
  • Synthesized context: Organize results by relevance with summaries, excerpts, and links to speed root-cause analysis workflows.
  • Use case: When an automated job fails, use the skill to find the job's config in GitHub, associated runbooks in Confluence, and related troubleshooting discussion in Slack to produce an investigation brief.

Quick Start

Use the context-fetcher skill to search GitHub, Confluence, and Slack for job 123456 and return a synthesized summary of relevant files, pages, and messages.

Frequently Asked Questions about context-fetcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather configuration files and runbooks for an incident investigation across multiple platforms?

Gather configuration files and runbooks for incident investigation by searching GitHub repositories, Atlassian Confluence pages, and Slack channels in parallel to locate IaC files, documentation, and relevant messages. The skill synthesizes organized findings with excerpts and links to reduce time-to-diagnosis.

What is the best way to search GitHub, Confluence, and Slack simultaneously for root-cause analysis context?

Search GitHub, Confluence, and Slack simultaneously for root-cause analysis context by extracting keywords from a job or incident ID and querying connected MCP tools. The skill targets configuration files, code references, runbooks, and channel messages, then returns a consolidated investigation brief.

Can I retrieve specific YAML, JSON, Helm, Terraform, or Ansible files during an automated job failure investigation?

Retrieve specific YAML, JSON, Helm, Terraform, and Ansible files during job failure investigations by searching targeted GitHub repositories via MCP tools. The skill fetches file contents directly for quick inspection and includes them in a synthesized summary with relevant links.

Does context-fetcher work with Atlassian Confluence and Slack for finding troubleshooting discussions?

Context-fetcher works with Atlassian Confluence and Slack by reading channel history and page content via MCP tools. It locates runbooks, documentation, and troubleshooting discussions related to an incident, organizing results by relevance with summaries and excerpts for faster root-cause analysis.

How do I produce an investigation brief from scattered job failure context?

Produce an investigation brief from scattered job failure context by querying GitHub, Confluence, and Slack with extracted keywords. The skill locates configuration, code references, runbooks, and messages, then synthesizes organized findings with summaries, excerpts, and links to speed diagnosis.

What limitations should I expect when searching Slack channel history and Confluence pages for incident context?

Limitations when searching Slack channel history and Confluence pages for incident context depend on MCP tool access permissions and available API scopes. The skill organizes accessible files, pages, and messages by relevance, but cannot retrieve content from channels or spaces where the connected integration lacks access.