runbook-creator
Runbook Creator - Auto-activating skill for Technical Documentation. Triggers on: runbook creator, runbook creator Part of the Technical Documentation skill category.
33
Quality
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 severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It lacks any concrete actions, meaningful trigger terms, or usage guidance. The duplicate trigger term and reliance on category labeling instead of actual capability description makes this ineffective for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates operational runbooks with step-by-step procedures, troubleshooting guides, and escalation paths for technical systems.'
Include a 'Use when...' clause with natural trigger terms like 'runbook', 'operations documentation', 'incident response guide', 'SOP', 'playbook', or 'on-call procedures'.
Remove the duplicate trigger term and expand to include variations users would naturally say when needing runbook creation assistance.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Runbook Creator' and 'Technical Documentation' without describing any concrete actions. There are no specific capabilities listed like 'creates step-by-step operational procedures' or 'generates incident response documentation'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundantly listed as 'runbook creator, runbook creator' (duplicated). Missing natural variations users might say like 'runbook', 'operations guide', 'incident playbook', 'SOP', or 'operational documentation'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'runbook' is a somewhat specific term, the description is so vague that it could overlap with general documentation skills. The category 'Technical Documentation' is broad and doesn't help distinguish this from other documentation-related 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 essentially a placeholder with no actionable content. It describes what a runbook creator skill should do without providing any actual guidance, templates, examples, or concrete instructions for creating runbooks. The entire content could be replaced with a single sentence and would lose nothing of value.
Suggestions
Add a concrete runbook template with sections (title, purpose, prerequisites, steps, rollback procedures, contacts) that Claude can use as a starting point
Include at least one complete example runbook for a common scenario (e.g., service restart, deployment rollback, incident response)
Define a clear workflow: 1) Gather requirements, 2) Draft structure, 3) Fill sections, 4) Validate completeness, 5) Review with stakeholders
Add specific formatting guidelines and validation criteria (e.g., 'every step must have expected outcome', 'include estimated time for each step')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance on how to actually create runbooks. No code examples, no templates, no specific commands or formats - just abstract descriptions of what the skill supposedly does. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. The skill claims to provide 'step-by-step guidance' but contains no actual steps, sequences, or processes for creating runbooks. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, examples, or templates. There's nothing to progressively disclose because there's no substantive content. | 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
0c08951
- 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.