analyzing-malware-family-relationships-with-malpedia

Query the Malpedia API to look up malware family aliases and naming (platform.family_name), pull community/vendor YARA rules, link families to threat actors, and map family relationships such as loader-payload chains and shared authorship. Use when researching a malware family's aliases, lineage, or actor attribution, or when sourcing YARA rules for detection.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/analyzing-malware-family-relationships-with-malpedia/SKILL.md

Quality

Content

57%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.

The body provides concrete, mostly-executable code and a clear three-step sequence, but it is held back by verbosity that re-explains known concepts, missing in-workflow validation for batch API operations, and a bundle file that is never linked from the body.

Suggestions

Trim the Overview and Key Concepts to domain-specific facts Claude would not already know (e.g. keep the platform.family_name format, drop generic malware-classification explanation).

Add explicit validation checkpoints inside the workflow (e.g. verify API responses, validate compiled YARA with yara-python before writing) with fix-and-retry feedback loops.

Link references/api-reference.md from the body (e.g. an 'API reference' pointer in Step 1 or a References subsection) so the bundle's extra endpoints are discoverable instead of inlining the full client.

Dimension	Reasoning	Score
Conciseness	The Overview rehashes the description and explains what Malpedia is, and Key Concepts explains malware naming/data models Claude largely already knows; the code blocks are also fairly verbose with print debugging, so it is mostly efficient but could be tightened.	3 / 5
Actionability	Three complete, executable Python classes with concrete API calls are provided; a minor gap is that build_loader_payload_chain relies on a hardcoded known_chains dict rather than querying the API.	4 / 5
Workflow Clarity	Steps 1-3 are clearly sequenced, but there are no in-workflow validation checkpoints or error-recovery feedback loops for these batch API/compilation operations, so per the batch-operation cap it cannot exceed 3.	3 / 5
Progressive Disclosure	The bundle file references/api-reference.md exists and contains extra endpoints, but the body never references or links to it, and the bulk API client code is inlined rather than split out, so structure is present but references are not clearly signaled.	3 / 5
	Total	13 / 20 Passed

Description

92%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.

The description is specific, complete, and distinct, clearly stating both the concrete capabilities and the natural trigger conditions in third person. It is a strong, well-scoped skill description with only minor room for additional trigger synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'look up malware family aliases and naming', 'pull community/vendor YARA rules', 'link families to threat actors', and 'map family relationships such as loader-payload chains and shared authorship' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (query API, look up aliases, pull YARA, link actors, map relationships) and 'when' via 'Use when researching a malware family's aliases, lineage, or actor attribution, or when sourcing YARA rules for detection.'	5 / 5
Trigger Term Quality	Natural terms like 'malware family', 'aliases', 'lineage', 'actor attribution', 'YARA rules', and 'detection' are present, but a few synonyms (e.g. 'threat group', 'detection rules') are missing.	4 / 5
Distinctiveness Conflict Risk	A clear Malpedia-specific niche with distinct triggers (malware family aliases, lineage, actor attribution, YARA sourcing) minimizes conflict with other skills.	5 / 5
	Total	19 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: mukul975/Anthropic-Cybersecurity-Skills
Path: skills/analyzing-malware-family-relationships-with-malpedia/SKILL.md
Commit: 54a7988

Reviewed: ~3 hours 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.