SKILLEMALL.ai
GitHub ↗ RU Sign in

AF oncall-runbook

Write an on-call runbook for a service — covering alert definitions, escalation paths, common incident responses, and on-call handoff procedures. Use when asked to write an on-call guide, create alert runbooks, document escalation procedures, or prepare an on-call handoff document. Produces a structured on-call runbook with per-alert response procedures, escalation matrix, diagnostic commands, and handoff template.

mohitagw15856/pm-claude-skills Agent Skills author: mohitagw15856 MIT 1 file body ≈ 3 281 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Write an on-call runbook for a service — covering alert definitions, escalation paths, common incident responses, and on-call handoff procedures.

As a process F 63/100 · Will not run — References files that are not bundled: ../../docs/craft/incident-response.md

ProcedureSlackInfrastructureCustomer supporttype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
100
Quality 40%
81
Run on models
none yet
Process rating
F
63/100
Will not run
References files that are not bundled: ../../docs/craft/incident-response.md
Tools and files w 18
0
Running it twice w 4
30
When it triggers w 12
50
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: oncall-runbook (mohitagw15856/pm-claude-skills)

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../../docs/craft/incident-response.md

Process rating: all ten parameters 63/100

Will not run. References files that are not bundled: ../../docs/craft/incident-response.md
  • 0Tools and files. 1 referenced file(s) missing: ../../docs/craft/incident-response.md
  • 30Running it twice. 3 mutating operations with no state check
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 27 steps, 1 vague phrases
  • 100Result and completion. Output format and completion criterion are stated
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3281 tokens
  • 100Progress reporting. Reports progress
  • low 14 top-level sections: this looks like several domains in one skill

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +1No license
  • +2Single-language instructions
  • +3Description length 418: enough signal without eating the budget
  • +4Structure: 21 headings
  • +3Step-by-step instructions: 27 items
  • +3Output format is stated explicitly
  • +4Has examples (16 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.