playbook-lookup skillA
playbook-lookup is agent-read markdown (skill) from papadopouloskyriakos/agentic-chatops: Query past incident resolutions from the knowledge base. Use when asked about prior incidents, what fixed a host/alert before, or playbooks for similar alerts. Searches by hostname or alert rule name..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Incident Playbook Lookup Queries the incident knowledge base for past resolutions. Use this skill when: - "what fixed CPU high on nl-pve01?" - "past incidents for CiliumAgentNotReady" - "playbook for disk space alerts" - "what was the resolution for IFRNLLEI01PRD-109?" - "has this alert happened before?" - Any question about prior incident resolutions or playbooks ## HOW to use Run the lookup script with a search term (hostname, alert rule name, or issue ID): ```bash ./skills/playbook-lookup/playbook-lookup.sh nl-pve01 ./skills/playbook-lookup/playbook-lookup.sh CiliumAgentNotReady ./skills/playbook-lookup/playbook-lookup.sh IFRNLLEI01PRD-109 ``` The script queries the `incident_knowledge` SQLite table on app-user and returns matching past resolutions with: - Issue ID and date - Hostname and alert rule - Resolution summary - Confidence score ## CRITICAL RULES 1. **RUN THE TOOL FIRST.** Do not answer from memory about past incidents. 2. **Present the results clearly.** Include the issue ID, date, and confidence. 3. **Note if no results found.** The knowledge base only contains resolved infra sessions.
Read the whole file at its exact version.
How to install
mdr add papadopouloskyriakos/agentic-chatops/playbook-lookup@git:20260919.c129a05mdr add papadopouloskyriakos/agentic-chatops/playbook-lookup@sha256:d2b5f7781fb43080Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_a5holoaaccd5jktb)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1452 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
papadopouloskyriakos/agentic-chatops · 107 stars · license none · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a5holoaaccd5jktb GET https://markdownregistry.com/api/v1/resolve?ref=papadopouloskyriakos/agentic-chatops/playbook-lookup GET https://markdownregistry.com/api/v1/blob/d2b5f7781fb43080b279ba2b1072e222d578f04eaa06236e45d407babf23313d
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.