incident-debrief

Post-incident LEARNING debrief for an infrastructure engineer growing their skills. Use when the user, after an incident or debugging session is resolved, asks to walk through what happened, how the investigation went, what the agent did and why, what the dead ends were, what they should learn, or says things like "explain what you did", "debrief me", "teach me from this incident", "how did you figure that out". Also use when the user points to a recent incident-log-*.md from the incident-response skill and asks for debrief or learning review. This is NOT root cause analysis or a formal postmortem document; the deliverable is the user's improved debugging skill.

Ir a la instalación

Repositorio: delicb/dotfiles
Última actividad en el origen: 7 de julio de 2026 a las 21:58
Idioma detectado de SKILL.md: inglés
Estrellas: 0
Forks: 0

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/delicb/dotfiles --skill incident-debrief

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

incident-response

Live production incident investigation mode for infrastructure engineers. Use only when the user explicitly asks you to handle, investigate, or respond to an incident, or explicitly invokes the incident-response skill. Do not trigger only because the user reports a production issue, alert, error, stack trace, slow service, failed workload, or other incident-like signal.

2026-07-30

finicky-config

Interpret, explain, write, and update Finicky v4 configuration for macOS URL routing. Use when working with ~/.finicky.js or ~/.finicky.ts, reading an existing Finicky setup, authoring rewrite or handler rules, choosing browsers or profiles, debugging rule order, or migrating routing logic into Finicky.

2026-06-29

work-on

Work on a Linear issue by ID. Fetch issue details, classify it as a bug, task, or unclear request, gather the right context, create the Linear branch from latest master, implement simple changes, and verify with tests, lint, and typecheck. Bugs require root cause analysis and production evidence when useful. Tasks require clarified requirements, acceptance criteria, constraints, and tradeoffs.

2026-05-29

Ver todos los de este repositorio

Incident Debrief (learning mode)

The user is an infrastructure engineer building fluency with their systems and observability stack. An incident just ended. Turn the investigation into a teaching session. The output is understanding in the user's head, not a document for stakeholders. Do not produce a formal postmortem, action items, or blameless-RCA boilerplate unless explicitly asked.

Source material

In priority order:

A timestamped incident-log-*.md written by the incident-response skill during the incident. Look in the working directory and ~/.local/state/incident-logs/ if the user did not provide a path. If multiple logs exist, ask which one to use. Do not assume a stale log is the current incident.

The current conversation history, if the investigation happened in this session.

The user's own account. If neither log nor history exists, interview them briefly: what was the signal, what did they check, in what order, what did they conclude. Then debrief their process the same way you would your own.

Ground every claim in this material. If you cannot reconstruct why a step was taken, say so plainly instead of inventing a retroactive rationale. A debrief that rewrites history teaches the wrong lessons.

Debrief structure

Walk through these five parts in order. Conversational prose, not a wall of headers. Keep each part tight; depth goes where the user asks questions.