CC performing-dynamic-analysis-with-any-run
Perform interactive dynamic malware analysis using the ANY.RUN cloud sandbox to detonate samples, observe real-time execution behavior, interact with malware prompts such as dialogs and CAPTCHAs, and capture process trees, network traffic, and system changes. Use when a suspicious file or URL needs live, interactive behavioral detonation in a cloud sandbox rather than static analysis alone.
Perform interactive dynamic malware analysis using the ANY.RUN cloud sandbox to detonate samples, observe real-time execution behavior, interact with malware…
As a process C 63/100 · Has gaps — weak spots: failures and branches, running it twice, progress reporting
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Risky intent
intent-offensive-securitySKILL.md:3Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)description: 'Perform interactive dynamic malware analysis using the ANY.RUN cloud sandbox
quoted -
low Risky intent
intent-offensive-securitySKILL.md:44Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Interactive malware analysis is needed where the analyst must click dialogs, enter credentials, or navigate installer screens
-
low Risky intent
intent-offensive-securitySKILL.md:107Offensive-security / dual-use content (legitimate for authorised testing; review intended use)3. UAC Prompts: Click "Yes" to allow elevation (observe privilege escalation)
-
low Risky intent
intent-offensive-securitySKILL.md:152Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Geographic visualization of C2 server locations
-
low Risky intent
intent-offensive-securitySKILL.md:215Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (documentation table row)| **Behavioral Tags** | ANY.RUN classification labels automatically applied based on observed behavior (e.g., "trojan", "stealer", "ransomware") |
table
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 "d3fend_techniques" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack" - note
edit-residuethe text marks something as outdated (lines 32): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 63/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 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. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2528 tokens
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 393: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 26 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.