CB building-automated-malware-submission-pipeline
Builds an automated malware submission and analysis pipeline that collects suspicious files from endpoints and email gateways, submits them to sandbox environments and multi-engine scanners, and generates verdicts with IOCs for SIEM integration. Use when SOC teams need to scale malware analysis beyond manual sandbox submissions for high-volume alert triage.
Builds an automated malware submission and analysis pipeline that collects suspicious files from endpoints and email gateways, submits them to sandbox…
As a process B 70/100 · Nearly there — weak spots: 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:499Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)Registry: HKCU\Software\Microsoft\Windows\CurrentVersion\Run\Update
security skill -
low Risky intent
intent-offensive-securitySKILL.md:6Offensive-security / dual-use content (legitimate for authorised testing; review intended use)Use when SOC teams need to scale malware analysis beyond manual sandbox submissions
-
low Risky intent
intent-offensive-securitySKILL.md:368Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"""Send malware analysis verdict to Splunk HEC"""
quoted -
low Risky intent
intent-offensive-securitySKILL.md:416Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)"""Execute full malware analysis pipeline"""
quoted -
low Risky intent
intent-offensive-securitySKILL.md:461Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- **Cuckoo Sandbox**: Open-source automated malware analysis platform with behavioral analysis and network capture
detector -
low Risky intent
intent-offensive-securitySKILL.md:478Offensive-security / dual-use content (legitimate for authorised testing; review intended use)MALWARE ANALYSIS REPORT — Pipeline Submission
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 "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack"
Process rating: all ten parameters 70/100
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4541 tokens
- 100Steps. 20 steps
- 100Consistency. Name and required fields are in place
- 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
- -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 359: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 20 items
- +3Output format is stated explicitly
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.