Source profileQuality 62/100

nexu-io/open-design/design-templates/eng-runbook/SKILL.md

eng-runbook

Use it for engineering and operations tasks; the detail page covers purpose, installation, and practical steps.

Source repository stars
82,073
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Produce a single-page engineering runbook.

Best for

  • Use when the brief mentions "runbook", "ops doc", "on-call guide", "SRE doc", or "运维手册".

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "design-templates/eng-runbook"
Safe inspection promptEditorial

Inspect the Agent Skill "eng-runbook" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/design-templates/eng-runbook/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Read DESIGN.md. 2. Identify the service from the brief. 3. Layout: - Header: service name, owner team, severity tier, version. - Service summary paragraph + dependency list. - Alerts table: alert name / severity / what it means / first response. - Dashboards & links list. - C…

    Read DESIGN.md.Identify the service from the brief.Layout:
  2. 02

    Output contract

    Review the “Output contract” section in the pinned source before continuing.

    Review and apply the “Output contract” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score62/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars82,073SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
nexu-io/open-design
Skill path
design-templates/eng-runbook/SKILL.md
Commit
89d6d4ef21baf80f871595abdf6f7de6e941dd44
License
Apache-2.0
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Engineering Runbook Skill

Produce a single-page engineering runbook.

Workflow

  1. Read DESIGN.md.
  2. Identify the service from the brief.
  3. Layout:
    • Header: service name, owner team, severity tier, version.
    • Service summary paragraph + dependency list.
    • Alerts table: alert name / severity / what it means / first response.
    • Dashboards & links list.
    • Common procedures block (3–4) with code blocks (deploy, rollback, rotate keys).
    • On-call rotation table (week / primary / secondary / backup).
    • Incident response checklist (5 numbered steps).
  4. One inline <style>, semantic HTML, monospace for code blocks.

Output contract

<artifact identifier="runbook-name" type="text/html" title="Service Runbook">
<!doctype html>...</artifact>

Alternatives

Compare before choosing