CC building-soc-escalation-matrix
Build a structured SOC escalation matrix defining severity tiers, response SLAs, tiered escalation paths, and notification procedures for security incidents, using context-driven criteria that combine business risk, asset criticality, and data sensitivity. Use when designing or revising how a SOC triages and escalates incidents across analyst tiers.
Build a structured SOC escalation matrix defining severity tiers, response SLAs, tiered escalation paths, and notification procedures for security incidents…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 6
✓ No critical or high findings
Medium and low: 6
-
low Risky intent
intent-offensive-securityassets/template.md:26Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Ransomware detected | P1 | Tier 3 + CISO |
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:14Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Malware | P2 | ransomware, wiper, apt |
-
low Exfiltration
exfil-webhook-urlreferences/api-reference.md:52Webhook / callback URL commonly used for exfiltration (verify the destination) (placeholder value)POST https://hooks.slack.com/services/T.../B.../xxx
placeholder -
low Risky intent
intent-offensive-securitySKILL.md:88Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Impact | Active data breach, ransomware spreading, critical systems compromised |
-
low Risky intent
intent-offensive-securitySKILL.md:95Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Examples | Active ransomware, confirmed data exfiltration, domain admin compromise |
-
low Risky intent
intent-offensive-securitySKILL.md:151Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Ransomware detected on any endpoint | P1 - Immediate Tier 3 + Management |
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack"
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1656 tokens
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 351: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.