malware-analyst

Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. Handles static/dynamic analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage, threat hunting, incident response, or security research.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/malware-analyst/SKILL.md

Quality

Content

50%Weight 40%Scale 1-3

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

The body is organized into relevant sections and contains some concrete commands and a usable YARA rule, but it is over-long with inline catalogs of concepts Claude already knows, has malformed code-fence markdown, and lacks validation feedback loops in its workflow. It would benefit from moving reference material into bundle files and tightening the inline content.

Suggestions

Move the tool catalogs, technique tables, and report template into reference files under ./references/ and link to them from a lean SKILL.md overview to improve progressive disclosure and conciseness.

Fix the broken code fences so commands are properly fenced and remove numbered/prose content from inside code blocks, making guidance copy-paste ready.

Add explicit validation/verification checkpoints (e.g., confirm hashes, verify sandbox snapshots before/after execution, validate extracted IOCs) and complete the phase numbering (add Phase 1/2) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body contains large inline catalogs of well-known concepts (persistence mechanisms, evasion techniques, C2 channels, tool descriptions like Wireshark/Process Monitor) that Claude already knows, padding the token budget unnecessarily. Not a 1 because it still includes concrete commands rather than pure prose explanation.	2 / 3
Actionability	Concrete commands exist (file, sha256sum, strings, rabin2, FLOSS, a real YARA rule), but the markdown is malformed — commands sit outside opened fences and numbered lists are wrongly placed inside code fences — so guidance is incomplete and not copy-paste ready. Not a 1 because executable content is present; not a 3 because of the broken formatting and mixed prose-in-fences.	2 / 3
Workflow Clarity	A phased sequence (Static/Dynamic) and a numbered Response Approach exist, but phases are incomplete (no Phase 1/2) and there are no validation checkpoints or error-recovery feedback loops for risky sandbox operations. Meets the anchor for steps present with validation gaps; not a 1 because a sequence exists.	2 / 3
Progressive Disclosure	No bundle files exist and the ~235-line body is monolithic, with large inline reference catalogs (tools, techniques, report template) that should be split into separate files. Not a 1 because content is organized into clear sections rather than an unstructured wall; not a 3 because nothing is split out and there is no overview-to-detail navigation.	2 / 3
	Total	8 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, complete, and distinct, naming concrete capabilities and providing an explicit trigger clause in third-person voice. A minor buzzword ("Masters") is present but does not undermine the concrete action list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as "sandbox analysis, behavioral analysis, and malware family identification" and "static/dynamic analysis, unpacking, and IOC extraction", matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Clearly answers both what (the analysis capabilities) and when (explicit "Use PROACTIVELY for..." trigger clause), satisfying the top anchor.	3 / 3
Trigger Term Quality	"Use PROACTIVELY for malware triage, threat hunting, incident response, or security research" covers natural terms a user would say, providing good keyword coverage.	3 / 3
Distinctiveness Conflict Risk	"Expert malware analyst" defines a clear niche with distinct triggers unlikely to collide with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/malware-analyst/SKILL.md
Commit: e63f7dd

Reviewed: 13 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.