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.
33
0%
Does it follow best practices?
Impact
97%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/04-security-advanced/incident-response-planner/SKILL.mdQuality
Discovery
0%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 essentially a placeholder with no substantive content. It repeats the skill name as a trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be nearly useless for skill selection among multiple available skills.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Creates incident response plans, defines escalation procedures, generates communication templates, and outlines containment strategies for security incidents.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about incident response planning, IR playbooks, breach response procedures, security incident handling, or creating escalation workflows.'
Diversify trigger terms beyond the skill name to include natural variations users would say, such as 'IR plan', 'security breach response', 'incident playbook', 'incident handling', 'containment strategy', etc.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only states the skill name and category ('Incident Response Planner', 'Security Advanced') without describing what the skill actually does—no verbs like 'creates', 'generates', 'analyzes', etc. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. There is no explanation of capabilities and no explicit 'Use when...' clause—only a redundant trigger phrase and a category label. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('incident response planner, incident response planner'). There are no natural user keywords like 'security incident', 'breach response', 'IR plan', 'incident playbook', 'response procedures', or other terms a user would naturally say. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it could overlap with any security-related skill. Without specific actions or clear scope, there is nothing to distinguish it from other security or incident-related skills. | 1 / 3 |
Total | 4 / 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 placeholder that provides no actual guidance on incident response planning. It contains only generic meta-descriptions of what the skill claims to do, with no actionable content, no concrete examples, no frameworks (like NIST SP 800-61), no templates, and no executable steps. It would provide zero value to Claude when handling incident response planning tasks.
Suggestions
Add concrete incident response planning content: include a structured IR plan template covering phases (Preparation, Detection/Analysis, Containment, Eradication, Recovery, Post-Incident Review) with specific actions for each phase.
Provide actionable artifacts such as an example incident classification matrix, escalation procedures, communication templates, and a runbook skeleton that Claude can adapt to specific scenarios.
Include a clear workflow with validation checkpoints, e.g., severity classification → containment strategy selection → evidence preservation checklist → stakeholder notification → remediation verification.
Reference relevant frameworks (NIST SP 800-61, SANS IR process) and provide concrete code/config examples for common IR tasks like log analysis queries, IOC extraction scripts, or firewall rule templates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic filler that tells Claude nothing it doesn't already know. Phrases like 'Provides step-by-step guidance' and 'Follows industry best practices' are vacuous. There is zero domain-specific information about incident response planning. | 1 / 3 |
Actionability | There are no concrete steps, commands, code, frameworks, templates, or specific guidance for incident response planning. The entire skill describes what it claims to do rather than actually instructing Claude how to do it. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequencing, no validation checkpoints. Incident response planning inherently involves multi-step processes (detection, containment, eradication, recovery, lessons learned) but none are mentioned. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no separation of overview from detailed content. No bundle files exist to support it either. | 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
13d35b8
- 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.