SKILLEMALL.ai
GitHub ↗ RU Sign in

CC building-malware-incident-communication-template

Build structured communication templates for malware incidents (ransomware, wiper, trojan, worm), covering internal stakeholder notifications, executive briefings, technical advisories for IT teams, customer notifications, and regulatory disclosures, with severity-based escalation procedures. Use when drafting or standardizing incident communications and notification workflows for a malware outbreak.

mukul975/Anthropic-Cybersecurity-Skills Agent Skills author: mukul975 Apache-2.0 8 files · 2 scripts body ≈ 2 334 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Build structured communication templates for malware incidents (ransomware, wiper, trojan, worm), covering internal stakeholder notifications, executive…

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches

GeneratorInfrastructureSecuritytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
87/100
safety, quality, tests
Safety 60%
95
Quality 40%
75
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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 · 5

    ✓ No critical or high findings

    Medium and low: 5
    • low Risky intent intent-offensive-security references/api-reference.md:14
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | Ransomware | Data encryption, ops disruption | Isolate hosts, disable shares |
    • low Risky intent intent-offensive-security references/workflows.md:10
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      |-- P1: Critical (ransomware, wiper, widespread)
    • low Risky intent intent-offensive-security SKILL.md:3
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      description: Build structured communication templates for malware incidents (ransomware,
    • low Risky intent intent-offensive-security SKILL.md:37
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      Effective communication during malware incidents is critical for coordinated response, stakeholder management, and regulatory compliance. A structured communication framework ensures the right people
    • low Risky intent intent-offensive-security SKILL.md:60
      Offensive-security / dual-use content (legitimate for authorised testing; review intended use)
      | P1 - Critical | Ransomware, wiper, or widespread infection affecting business operations | Within 15 minutes | CISO, CEO, Legal, Board (if applicable) |

    Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"
    • note frontmatter-key unknown frontmatter key "subdomain"
    • note frontmatter-key unknown frontmatter key "mitre_attack"
    • note frontmatter-key unknown frontmatter key "nist_csf"

    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. 12 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 2334 tokens
    • low 11 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 403: enough signal without eating the budget
    • +4Structure: 15 headings
    • +3Step-by-step instructions: 12 items
    • +4Has examples (6 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.