Is runbook-generator safe to install?

SaferSkills independently audited runbook-generator (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

engineering/skills/runbook-generator/SKILL.md · 1 file

engineering/skills/runbook-generator/SKILL.md2.1 KB · Markdown

name: "runbook-generator"

description: "Generate operational runbooks from a service name — deployment, incident response, maintenance, and rollback workflows. Templated structure customizable per environment. Use when documenting on-call procedures for a new service, standardizing incident response across teams, or producing runbooks before launching to production."

Runbook Generator

Tier: POWERFUL Category: Engineering Domain: DevOps / Site Reliability Engineering

Overview

Generate operational runbooks quickly from a service name, then customize for deployment, incident response, maintenance, and rollback workflows.

Core Capabilities

Runbook skeleton generation from a CLI
Standard sections for start/stop/health/rollback
Structured escalation and incident handling placeholders
Reference templates for deployment and incident playbooks

When to Use

A service has no runbook and needs a baseline immediately
Existing runbooks are inconsistent across teams
On-call onboarding requires standardized operations docs
You need repeatable runbook scaffolding for new services

Quick Start

# Print runbook to stdout
python3 scripts/runbook_generator.py payments-api

# Write runbook file
python3 scripts/runbook_generator.py payments-api --owner platform --output docs/runbooks/payments-api.md

Recommended Workflow

Generate the initial skeleton with scripts/runbook_generator.py.
Fill in service-specific commands and URLs.
Add verification checks and rollback triggers.
Dry-run in staging.
Store runbook in version control near service code.

Reference Docs

references/runbook-templates.md

Common Pitfalls

Missing rollback triggers or rollback commands
Steps without expected output checks
Stale ownership/escalation contacts
Runbooks never tested outside of incidents

Best Practices

Keep every command copy-pasteable.
Include health checks after every critical step.
Validate runbooks on a fixed review cadence.
Update runbook content after incidents and postmortems.

runbook-generator— agent skill

Is runbook-generator safe to install?

Runbook Generator

Overview

Core Capabilities

When to Use

Quick Start

Recommended Workflow

Reference Docs

Common Pitfalls

Best Practices

Audit the pieces. Scan the whole. Decide.