Run any Skill in Manus with one click

knowledge-base-search

Stars0

Forks0

UpdatedJuly 11, 2026 at 11:55

Search historical GitHub issues and local troubleshooting docs for reusable fixes. Use when asked whether an incident happened before, when looking for similar failures, or when ranking likely known fixes before deeper diagnostics.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

alecsg77

alecsg77/elysium

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	knowledge-base-search
description	Search historical GitHub issues and local troubleshooting docs for reusable fixes. Use when asked whether an incident happened before, when looking for similar failures, or when ranking likely known fixes before deeper diagnostics.

Knowledge Base Search

When To Use

Use this skill before or during troubleshooting when pattern reuse might save time.
Use it when the user asks whether a failure has happened before.
Use it to search closed GitHub issues and /docs/troubleshooting/known-issues.md together.

Workflow

Extract component, error phrases, resource type, resource name, and symptoms.
Search closed issues with the tightest useful query first.
Search docs/troubleshooting/known-issues.md for local patterns.
Rank matches by error similarity, component, resource type, root cause, and symptom overlap.
Return high-confidence known fixes first; otherwise provide contextual references only.

Output Rules

State confidence clearly.
Separate exact or near-exact matches from weak analogies.
Avoid claiming a known fix when the evidence is thin.

References

/docs/troubleshooting/known-issues.md
/docs/troubleshooting/web-troubleshooting.md
.github/agents/troubleshooter.agents.md

More from this repository

same repository

coder-templates

alecsg77/elysium

Creates and updates Coder Registry workspace templates with agent setup, infrastructure provisioning, and module consumption

2026-07-110

deploy-application

alecsg77/elysium

Deploy a new application to this Flux GitOps cluster. Use when asked to add an app, scaffold base and overlay manifests, choose a Helm chart, wire ingress, or prepare deployment validation.

2026-07-110

generate-gitops-docs

alecsg77/elysium

Generate or update GitOps documentation for this repository. Use when asked to write application READMEs, runbooks, architecture notes, troubleshooting guides, or other docs tied to apps, infrastructure, monitoring, or cluster operations.

2026-07-110

gitops-implementation-planning

alecsg77/elysium

Create implementation plans for new applications, infrastructure changes, refactors, or rollout work in this GitOps repository. Use when the user asks for a plan, architecture impact, sequencing, dependencies, validation, or rollback steps before implementation.

2026-07-110

manage-sealed-secrets

alecsg77/elysium

Create, rotate, and wire Bitnami Sealed Secrets for this GitOps repository. Use when asked to add a secret, rotate credentials, seal secret values, or connect secret data to Flux and application manifests.

2026-07-110

review-gitops-config

alecsg77/elysium

Review Kubernetes manifests, HelmRelease values, Flux resources, and Kustomize overlays in this repository. Use when asked to review GitOps config, inspect YAML changes, audit manifests, or check Flux and security best practices.

2026-07-110

name	knowledge-base-search
description	Search historical GitHub issues and local troubleshooting docs for reusable fixes. Use when asked whether an incident happened before, when looking for similar failures, or when ranking likely known fixes before deeper diagnostics.

Knowledge Base Search

When To Use

Use this skill before or during troubleshooting when pattern reuse might save time.
Use it when the user asks whether a failure has happened before.
Use it to search closed GitHub issues and /docs/troubleshooting/known-issues.md together.

Workflow

Extract component, error phrases, resource type, resource name, and symptoms.
Search closed issues with the tightest useful query first.
Search docs/troubleshooting/known-issues.md for local patterns.
Rank matches by error similarity, component, resource type, root cause, and symptom overlap.
Return high-confidence known fixes first; otherwise provide contextual references only.

Output Rules

State confidence clearly.
Separate exact or near-exact matches from weak analogies.
Avoid claiming a known fix when the evidence is thin.

References

/docs/troubleshooting/known-issues.md
/docs/troubleshooting/web-troubleshooting.md
.github/agents/troubleshooter.agents.md