Standardize operational runbooks and infrastructure documentation across wiki namespace zones.
npx skills add https://github.com/zoraxl/team-brain --skill wiki-runbook
Please help me install this Agent Skill. Skill: wiki-runbook Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/wiki-runbook Command: npx skills add https://github.com/zoraxl/team-brain --skill wiki-runbook
This skill eliminates tribal knowledge silos and inconsistent documentation by providing a structured framework for capturing, organizing, and maintaining operational runbooks and infrastructure procedures.
Use the wiki-runbook skill to document the recovery procedure for the current production database connection timeout incident in the platform zone.
High-intent search queries and answers about installing and using this skill.
Standardize operational runbooks by routing technical knowledge into defined wiki namespace zones to ensure consistency across product and platform domains. This framework enforces structured templates and lifecycle metadata to maintain a durable, searchable team knowledge base.
Eliminate tribal knowledge silos by using a structured framework that captures and organizes operational procedures into standardized runbook templates. This ensures every procedure includes critical sections like symptoms, recovery steps, and prevention strategies.
Document incident recovery steps by using a structured runbook template that routes the technical knowledge into the appropriate platform wiki zone. This ensures the team can replicate the fix in the future by capturing symptoms, recovery steps, and prevention strategies.
Zone-based routing works for infrastructure documentation by automatically classifying technical knowledge into product namespaces, platform infrastructure, or general team workflows. It requires adherence to established wiki-zone boundaries and lifecycle metadata to maintain consistency.
Standardized runbooks should include critical sections for symptoms, recovery steps, and prevention strategies. This ensures operational procedures are captured consistently to help teams replicate fixes for production incidents like database connection timeouts.
Avoid multi-repo wiki architectures if your team cannot enforce adherence to established wiki-zone boundaries and lifecycle metadata. Without this structural discipline, the framework cannot maintain a durable, searchable knowledge base across product and platform domains.
ai-ecoverseCompile raw sources into an interlinked markdown wiki with ingest, query, and lint workflows.
lloydchangGenerate standardized multi-cloud runbook documentation from operational procedures.
Azeem-2Automate IT operations decisions with AIOps patterns for monitoring and incident response.
novatech2210-cmdAutomate GitHub Actions workflow generation and CI/CD orchestration across multi-repo projects.
