ctf-malware

Provides malware analysis and network traffic techniques for CTF challenges. Use when analyzing obfuscated scripts, malicious packages, custom crypto protocols, C2 traffic, PE/.NET binaries, RC4/AES encrypted communications, YARA rules, shellcode analysis, memory forensics for malware (Volatility malfind, process injection detection), anti-analysis techniques (VM/sandbox detection, timing evasion, API hashing, process injection, environment checks), or extracting malware configurations and indicators of compromise.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A terse, highly actionable quick-reference catalog with clean sectioning and good pivot guidance, but it relies on three reference files that are missing from the bundle and lacks validation checkpoints for risky dynamic malware analysis.

Suggestions

Ship the three referenced detail files (scripts-and-obfuscation.md, c2-and-protocols.md, pe-and-dotnet.md) alongside SKILL.md so the progressive-disclosure links resolve.

Add explicit validation/safety checkpoints for dynamic analysis (e.g. confirm sandbox isolation before executing samples, verify extracted config parses before reporting IOCs) to lift workflow clarity above the destructive-operation cap.

De-duplicate the network-indicators block (it appears in both Quick Start Commands and the final Network Indicators Quick Reference) and trim overlap between the Additional Resources descriptions and the body sections.

Dimension	Reasoning	Score
Conciseness	Largely lean one-liners and copy-paste commands that assume Claude's competence, but the "Additional Resources" index partially restates the later sections and the network-indicators block (lines 66-68) is duplicated at the end (lines 174-179), so not every token earns its place.	4 / 5
Actionability	Provides concrete, copy-paste-ready commands and code for the common cases (e.g. `python3 -c "import pefile; pe=pefile.PE('mal.exe'); print(pe.dump_info())"`, `vol3 windows.malfind`, `ar -x package.deb && tar -xf control.tar.xz`) with specific one-liners per technique.	5 / 5
Workflow Clarity	Quick Start groups commands into a rough static→PE→dynamic→network→YARA flow and offers "When to Pivot" decision guidance, but there are no validation/checkpoint steps for risky dynamic analysis of live malware, so the destructive/batch cap of 3 applies.	3 / 5
Progressive Disclosure	Structure and signaling are good (one-level-deep links from an "Additional Resources" index plus inline per-section links), but the three referenced files (scripts-and-obfuscation.md, c2-and-protocols.md, pe-and-dotnet.md) are not present in the bundle, so the disclosure targets are dead links and navigation breaks.	3 / 5
	Total	15 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely enumerates capabilities and provides an explicit, trigger-rich "Use when" clause scoped to a distinct CTF malware niche. It is comprehensive without padding.

Dimension	Reasoning	Score
Specificity	Lists many concrete analysis actions ("analyzing obfuscated scripts, malicious packages, custom crypto protocols, C2 traffic, PE/.NET binaries, RC4/AES encrypted communications, YARA rules, shellcode analysis, memory forensics...") with comprehensive coverage of the malware-analysis domain.	5 / 5
Completeness	Explicitly states what ("Provides malware analysis and network traffic techniques for CTF challenges") and when ("Use when analyzing obfuscated scripts... or extracting malware configurations and indicators of compromise") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a CTF malware analyst would actually say ("C2 traffic", "YARA rules", "shellcode analysis", "PE/.NET binaries", "memory forensics", "indicators of compromise") plus format/algorithm identifiers, giving comprehensive coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (malware and network analysis for CTF) with distinct triggers; the body's "When to Pivot" section further separates it from ctf-reverse/forensics/osint, minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 24 missing	Warning

	Total	14 / 16 Passed

Repository: ljagiello/ctf-skills
Path: ctf-malware/SKILL.md
Commit: 36c72e5

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.