CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ti-yara-hunting

YARA rule writing from behavioral observations and TI report analysis — sample-to-rule conversion, condition optimization, performance tuning, and retrohunting on VirusTotal and ANY.RUN. Covers YARA/YARA-X syntax, yarGen automated generation, and production rule deployment.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, dense skill body with concrete executable commands, complete rule examples, explicit validation checkpoints, and strong decision-gate routing. Its weaknesses are mild padding (MITRE table, duplicated install commands) and a monolithic single-file layout where the YARA syntax reference and lookup tables would serve better as separate reference files.

Suggestions

Move the YARA string types / condition essentials syntax reference and the tools, signatures, and error tables into references/ files (e.g. references/yara-syntax.md, references/retrohunt-platforms.md), keeping SKILL.md as an overview with clearly signaled links.

Remove the MITRE ATT&CK mapping table and the duplicated YARA-X install lines from Section 7 — they duplicate the Quick Reference without adding actionable value.

Trim the Detection Signatures table to entries not already derivable from Sections 1 and 4.

DimensionReasoningScore

Conciseness

The body is almost entirely commands, code, and lookup tables with minimal explanation of concepts Claude already knows, but minor padding exists: the MITRE ATT&CK mapping table, the duplicated 'cargo install yara-x' between Quick Reference and Section 7, and the Detection Signatures table that partially overlaps earlier sections. Efficient overall with a few tokens that could be trimmed.

4 / 5

Actionability

Fully executable throughout: install commands, strings/xxd/pefile extraction pipelines, yarGen invocations with flags, complete VT Retrohunt/LiveHunt and ANY.RUN curl API calls with JSON bodies, complete YARA rule examples, and a concrete problem/cause/solution error table. Copy-paste ready and covers the common cases.

5 / 5

Workflow Clarity

The Decision Gate routes each situation to a numbered section; sample-to-rule is a 5-step pipeline; the yarGen review checklist and the end-to-end retrohunt sequence include explicit validation checkpoints ('must match known sample, must NOT match goodware', 'Expect 0 matches') with feedback loops for false positives and YARA-X rejections.

5 / 5

Progressive Disclosure

No bundle files exist and the ~430-line body is monolithic. Sections are clearly headed and navigable, but reference material that belongs in separate files — the YARA string-type and condition-syntax references, and the tools/signatures/error tables — is inlined in SKILL.md. Fits 'some structure but content that should be separate is inline' better than the minor-gaps anchor.

3 / 5

Total

17

/

20

Passed

Description

75%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 highly specific, well-scoped description that clearly communicates concrete capabilities across the full rule-development lifecycle. Its one structural weakness is the absence of an explicit 'Use when...' trigger clause in the description itself, which caps completeness; a couple of common synonyms (livehunt, threat hunting) would round out trigger coverage.

Suggestions

Append an explicit trigger clause to the description, e.g. 'Use when writing or optimizing YARA rules, retrohunting on VirusTotal or ANY.RUN, or generating rules with yarGen' (the existing metadata.when_to_use list is not read as part of the description).

Add one or two natural trigger synonyms such as 'livehunt', 'threat hunting', or 'malware detection rules' to broaden the terms users would naturally say.

Consider mentioning the YARA-X rewrite's stricter validation explicitly as a trigger for users debugging rule syntax.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'sample-to-rule conversion, condition optimization, performance tuning, and retrohunting on VirusTotal and ANY.RUN' plus 'yarGen automated generation, and production rule deployment' — with comprehensive coverage of the skill's scope. No minor gaps; every clause names a distinct concrete action.

5 / 5

Completeness

The 'what' is clearly and comprehensively answered, but the description field contains no 'Use when...' clause or equivalent explicit trigger guidance — only implied triggers — which caps completeness at 3 per the judging guidelines. Not a 2 because the 'what' is explicit and concrete.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'YARA rule writing', 'retrohunting', 'VirusTotal', 'ANY.RUN', 'yarGen'. A few natural terms are missing ('livehunt', 'threat hunting', 'malware detection/signatures'), so coverage is good but not fully comprehensive with synonyms.

4 / 5

Distinctiveness Conflict Risk

'YARA rule writing... retrohunting on VirusTotal and ANY.RUN' defines a clear niche with distinct triggers; minimal overlap risk with other skills (e.g., general TI report skills).

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/analyst/ti-yara-hunting/SKILL.md

Reviewed

Table of Contents

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.