incident-response-planner
Incident Response Planner - Auto-activating skill for Security Advanced. Triggers on: incident response planner, incident response planner Part of the Security Advanced skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill incident-response-plannerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely lacking in all key areas. It provides no information about what the skill actually does, contains redundant and limited trigger terms, and fails to guide Claude on when to select this skill. The description reads more like metadata than a functional description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates incident response plans, defines escalation procedures, documents containment strategies, generates post-incident review templates'
Add a 'Use when...' clause with diverse trigger terms like 'security incident', 'breach response', 'incident playbook', 'security emergency', 'incident handling'
Remove the redundant trigger term and replace boilerplate metadata with actual capability descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states it's an 'Auto-activating skill for Security Advanced' without describing what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' entirely and provides no explicit 'when to use' guidance beyond the redundant trigger phrase. Both components are missing or very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'incident response planner' repeated twice. This is extremely limited coverage with no natural variations users might say like 'security incident', 'breach response', 'incident plan', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'incident response planner' is somewhat specific to security domain, the lack of detail about what it actually does makes it unclear how it differs from other potential security-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty shell with no actual content. It consists entirely of meta-descriptions about what the skill claims to do without providing any incident response planning guidance, procedures, checklists, or actionable information. For a security-critical domain like incident response, this complete lack of substance is particularly problematic.
Suggestions
Add concrete incident response phases (Preparation, Detection, Containment, Eradication, Recovery, Lessons Learned) with specific actions for each phase
Include a checklist or decision tree for incident classification and severity assessment
Provide templates for incident documentation, communication plans, and escalation procedures
Add validation checkpoints such as 'Confirm containment before proceeding to eradication' with specific verification steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual incident response content. | 1 / 3 |
Actionability | Contains zero concrete guidance, no code, no commands, no specific steps, and no actual incident response procedures. The entire skill describes what it claims to do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined whatsoever. For incident response planning—which inherently requires clear sequenced steps, escalation paths, and validation checkpoints—this complete absence of process guidance is a critical failure. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed materials, no links to runbooks, checklists, or templates that would be essential for incident response planning. | 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.