runbook-creator
Runbook Creator - Auto-activating skill for Technical Documentation. Triggers on: runbook creator, runbook creator Part of the Technical Documentation skill category.
33
3%
Does it follow best practices?
Impact
83%
0.95xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/17-technical-docs/runbook-creator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak across all dimensions. It reads as an auto-generated boilerplate with no substantive information about what the skill does, what outputs it produces, or when it should be selected. The duplicate trigger term and lack of any concrete actions or 'Use when' clause make it nearly useless for skill selection among multiple options.
Suggestions
Add concrete actions the skill performs, e.g., 'Creates step-by-step operational runbooks including incident response procedures, escalation paths, troubleshooting steps, and recovery checklists.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create a runbook, operations guide, incident playbook, SOP, on-call documentation, or troubleshooting guide.'
Remove the duplicate trigger term and expand with varied natural keywords users would actually say, such as 'runbook', 'ops guide', 'incident response doc', 'standard operating procedure', 'operational playbook'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names a category ('Technical Documentation') and a label ('Runbook Creator') but does not describe any concrete actions like 'creates step-by-step operational procedures' or 'generates incident response guides'. It is entirely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the label 'Runbook Creator' and provides no explicit 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'runbook creator' repeated twice. There are no natural variations a user might say such as 'runbook', 'operations guide', 'incident playbook', 'SOP', 'standard operating procedure', or 'on-call documentation'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'runbook' is somewhat niche and distinguishes it from generic documentation skills, but the lack of specificity about what kind of runbooks or what actions it performs means it could overlap with other technical documentation or template-generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of auto-generated boilerplate that describes what a runbook creator skill would do without actually providing any instructions, templates, examples, or actionable guidance for creating runbooks. It fails on every dimension of the rubric.
Suggestions
Add a concrete runbook template with sections (title, purpose, prerequisites, step-by-step procedures, rollback steps, escalation contacts) and a filled-out example.
Include executable guidance such as a markdown template or script that generates a runbook skeleton, with specific formatting conventions and validation criteria.
Define a clear workflow for creating a runbook: gather requirements → draft procedure steps → add validation checkpoints → review for completeness → test the runbook.
Add references to related files or examples (e.g., 'See RUNBOOK_TEMPLATE.md for a starter template' or 'See EXAMPLES/ for sample runbooks') to support progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no concrete steps, no code, no commands, no examples of runbook structure or templates. The 'capabilities' section describes what it could do but never actually does it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed materials, no links to examples or templates, and no meaningful structural organization beyond boilerplate headings. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.