runbook-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill runbook-creatorRunbook Creator - Auto-activating skill for Technical Documentation. Triggers on: runbook creator, runbook creator Part of the Technical Documentation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%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 guidance on when to use the skill. The duplicate trigger term and generic category label provide almost no value for skill selection.
Suggestions
Add specific capabilities describing what the skill does, e.g., 'Creates operational runbooks with step-by-step procedures, troubleshooting guides, and incident response workflows'
Include a 'Use when...' clause with natural trigger terms like 'runbook', 'operations documentation', 'incident playbook', 'SOP', 'on-call guide', or 'troubleshooting procedures'
Remove the duplicate trigger term and expand with 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 procedures' or 'documents incident response workflows'. | 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 'standard operating procedure'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'runbook' is somewhat specific terminology, the vague 'Technical Documentation' category could overlap with many documentation skills. The lack of specific use cases makes it unclear when this should be chosen over other documentation tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder with no actionable information. It describes what a runbook creator skill would do without providing any actual guidance on creating runbooks - no templates, no structure examples, no step-by-step process, and no concrete code or commands.
Suggestions
Add a concrete runbook template with sections (Purpose, Prerequisites, Steps, Rollback, Verification) and example content for each
Include executable examples showing how to structure runbook steps with commands, expected outputs, and error handling
Provide a clear workflow: 1) Identify the procedure, 2) Document prerequisites, 3) Write numbered steps with validation, 4) Add rollback procedures, 5) Test the runbook
Remove all meta-description content ('This skill provides...', 'Capabilities include...') and replace with actual runbook creation guidance
| 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 - no code, no commands, no specific steps, no examples of actual runbook content or structure. The skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for creating a runbook, no validation checkpoints, and no process to follow. The content is entirely meta-description. | 1 / 3 |
Progressive Disclosure | The content is a flat, unhelpful structure with no references to detailed materials, no examples, and no navigation to actual runbook creation guidance or templates. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.