it-knowledge-runbook

Creates IT knowledge articles, SOPs, runbooks, and recovery procedures with validation and rollback steps.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/lwokeray/cowork-plugins --skill it-knowledge-runbook-lwokeray
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: it-knowledge-runbook
Source: https://github.com/lwokeray/cowork-plugins/tree/main/plugins/it-operations-cowork/skills/it-knowledge-runbook
Command: npx skills add https://github.com/lwokeray/cowork-plugins --skill it-knowledge-runbook-lwokeray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? IT teams often lose critical operational knowledge in chat threads, one-off fixes, and outdated documents, making recurring incidents slow to resolve and handovers risky. This Skill turns verified operational practice into complete, safe, and maintainable documentation. ## Core Features & Use Cases - Multiple Document Types: Produces knowledge articles, SOPs, operational runbooks, known-error records, recovery procedures, and support handovers from a single workflow. - Safety-First Structure: Enforces prerequisites, permissions, checkpoints, decision branches, validation criteria, rollback steps, and escalation paths in every document. - Source Quality Control: Separates verified steps from draft content, replaces secrets and tenant-specific IDs with placeholders, and requires SME or service-owner review before publishing. - Use Case: After resolving a recurring VPN outage, ask the Skill to document the fix as a runbook with exact commands, expected results, stop conditions, and a rollback plan so any on-call engineer can execute it safely. ## Quick Start Write an IT runbook for restarting the production application server, including prerequisites, validation checks, and rollback steps.

Frequently Asked Questions about it-knowledge-runbook

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

FAQPage Schema
How do I write an IT runbook for an operational procedure?▼

Define the operational outcome, collect verified sources and tested commands, then write ordered imperative steps with checkpoints, expected results, decision branches, and rollback triggers. Finish with validation criteria, escalation paths, and owner and review metadata.

What is the difference between a runbook, an SOP, and a knowledge article?▼

A runbook executes an operational procedure with commands, checkpoints, and rollback. An SOP standardizes a repeatable business or IT process and its responsibilities. A knowledge article diagnoses or answers a recurring user or support question.

Can I document a fix that was only verified once in a chat conversation?▼

No. Unverified conversations or one-off workarounds must be labeled as draft and should not become authoritative procedure. Use current documentation, tested commands, and successful incident or change records as sources, then obtain SME review.

How should runbooks handle credentials and tenant-specific values?▼

Never embed live secrets, passwords, tokens, or environment-specific identifiers in the document. Replace them with named placeholders plus resolution instructions so readers can discover the correct values in their own environment.

Why does a documented procedure fail when another engineer runs it?▼

Procedures often work only for the original author because they lack prerequisites, target-resolution rules, expected results, and failure paths. Add explicit permissions, environment scope, and stop conditions so anyone qualified can execute them.

When should a known-error record be used instead of a fix article?▼

Use a known-error record when the root cause is confirmed but only a workaround exists. Record the cause, symptoms, workaround, and permanent-fix status separately so the workaround is not mistaken for a resolution.