agentleFS
ai-workspace-labai-workspace-lab/xworkspace-core-skills/skills/operations-management/service-catalog-and-runbook-standard/SKILL.md

service-catalog-and-runbook-standard

Skill8 starsChanged 5 months agoMITView on GitHub

Create or review service catalog records, ownership metadata, dependency maps, operational runbooks, deployment records, backup and recovery references, and retirement documentation. Use when onboarding a service, changing ownership or dependencies, writing an operational procedure, or auditing operational readiness.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every production service must have an operational record that lets a qualified responder identify ownership, impact, deployment path, …

    line 10

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Service Catalog and Runbook Standard

涉及 Agent 团队执行记录、handoff 或归档引用时,按Agent Team Harness维护稳定 service/task/run 关联;本技能仍拥有服务元数据、依赖与 Runbook 的权威定义。

Every production service must have an operational record that lets a qualified responder identify ownership, impact, deployment path, dependencies, health, recovery, and safe escalation without tribal knowledge.

涉及 Ansible Pull、Doco CD 或 Flux CD 的接管、运行验收和回退时,读取Unified GitOps 运行与验收。

1. Minimum service record

Maintain a versioned record with: service name and purpose; business and technical owner; environment; repository and deploy entrypoint; immutable artifact/revision convention; public/internal endpoints; data classification; dependencies and dependency owners; SLO/dashboard/alerts; Vault role/path owner without secret values; CMDB/resource identity; backup/RPO/RTO; migration and retirement owner; and links to runbooks and recent incidents.

生产抽查时关联声明版本、实际运行身份与可用的应用版本信号。若只能取得健康响应或声明,按已验证的层级记录,账户权限、写入和恢复各自引用实际证据。

The record is metadata, not a second configuration source. Link to Terraform, CMDB, GitOps, workflow, and playbook sources rather than copying mutable IPs, credentials, or node lists.

2. Runbook requirements

Each operational action needs purpose, owner, trigger, prerequisites, exact target selection, least-privilege access path, commands/workflow link, expected output, validation, abort/rollback point, communication requirement, and evidence to retain. Mark whether the action is read-only, mutating, destructive, emergency-only, or legacy/manual.

Runbooks for restore, migration, DNS cutover, credential rotation, and deletion must name the explicit confirmation input and the recovery point. Do not hide a destructive action behind an ambiguous command such as cleanup or reset.

3. Keep records trustworthy

Update the service record in the same PR as a material ownership, endpoint, dependency, deployment, SLO, backup, or runbook change. Review records during incidents and quarterly operational reviews. A runbook that has not been exercised, whose target no longer resolves from CMDB, or whose owner is absent is stale and must be marked accordingly.

Link postmortem action items to the service record and runbook changes that prevent recurrence.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.