firefrost-gaming/claude-skills-reference

Files

Reza Rezvani 2f57ef8948 feat(agenthub): add AgentHub plugin with cross-domain examples, SEO optimization, and docs site fixes

- AgentHub: 13 files updated with non-engineering examples (content drafts,
  research, strategy) — engineering stays primary, cross-domain secondary
- AgentHub: 7 slash commands, 5 Python scripts, 3 references, 1 agent,
  dry_run.py validation (57 checks)
- Marketplace: agenthub entry added with cross-domain keywords, engineering
  POWERFUL updated (25→30), product (12→13), counts synced across all configs
- SEO: generate-docs.py now produces keyword-rich <title> tags and meta
  descriptions using SKILL.md frontmatter — "Claude Code Skills" in site_name
  propagates to all 276 HTML pages
- SEO: per-domain title suffixes (Agent Skill for Codex & OpenClaw, etc.),
  slug-as-title cleanup, domain label stripping from titles
- Broken links: 141→0 warnings — new rewrite_skill_internal_links() converts
  references/, scripts/, assets/ links to GitHub source URLs; skills/index.md
  phantom slugs fixed (6 marketing, 7 RA/QM)
- Counts synced: 204 skills, 266 tools, 382 refs, 16 agents, 17 commands,
  21 plugins — consistent across CLAUDE.md, README.md, docs/index.md,
  marketplace.json, getting-started.md, mkdocs.yml
- Platform sync: Codex 163 skills, Gemini 246 items, OpenClaw compatible

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-03-17 12:10:46 +01:00

2.4 KiB

Raw Blame History

title, description

title	description
Runbook Generator — Agent Skill for Codex & OpenClaw	Runbook Generator. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw.

Runbook Generator

:material-rocket-launch: Engineering - POWERFUL :material-identifier: `runbook-generator` :material-github: Source

Install: claude /plugin install engineering-advanced-skills

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.

2.4 KiB Raw Blame History