CB conducting-malware-incident-response
Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradication, and recovery procedures aligned to MITRE ATT&CK. Use when responding to a confirmed or suspected malware infection, including trojan/worm/ransomware outbreaks, malware triage, or infected endpoint remediation.
Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing…
As a process B 66/100 · Nearly there — weak spots: failures and branches, progress reporting
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
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
-
medium Dangerous commands
cmd-persistenceSKILL.md:121Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)- HKCU\Software\Microsoft\Windows\CurrentVersion\Run\{random} (backup persistence)security skill -
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use)description: Respond to malware infections across enterprise endpoints by identifying the malware family, determining infection vectors, assessing spread, and executing containment, analysis, eradicat
-
low Risky intent
intent-offensive-securitySKILL.md:44Offensive-security / dual-use content (legitimate for authorised testing; review intended use)**Do not use** for analyzing malware samples in a research context; use dedicated malware analysis procedures for reverse engineering.
-
low Risky intent
intent-offensive-securitySKILL.md:108Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Malware Analysis Summary - Qakbot Variant
-
low Risky intent
intent-offensive-securitySKILL.md:132Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Clear browser credential stores if credential harvesting was confirmed
-
low Risky intent
intent-offensive-securitySKILL.md:153Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Beacon** | Periodic network communication from malware to its C2 server, typically with a set interval and jitter for detection evasion |
Files scanned: 4. 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 "mitre_attack" - note
frontmatter-keyunknown frontmatter key "d3fend_techniques" - note
frontmatter-keyunknown frontmatter key "nist_csf"
Process rating: all ten parameters 66/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2258 tokens
- 100Running it twice. Mutating operations check current state
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 401: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 56 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.