CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ti-anyrun-lookup

ANY.RUN Threat Intelligence Lookup workflow — query hashes, domains, IPs, and behavioral indicators against ANY.RUN's sandbox corpus. Covers TI Lookup query syntax, search operators, free tier constraints, result correlation with engagement findings, and integration with sandbox analysis.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/analyst/ti-anyrun-lookup/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 dense, highly actionable reference with executable API commands, complete Python extraction scripts, explicit error-recovery guidance, and a useful decision gate. Its weaknesses are token efficiency (duplicated curl boilerplate and repeated free-tier limits) and a monolithic structure that inlines a full query-field reference instead of splitting it into a references/ file.

Suggestions

Move the full field-based search reference, wildcard tables, and detection-signature tables into a references/query-syntax.md file and keep only a quick-start subset in SKILL.md — this would improve both progressive_disclosure and conciseness.

Deduplicate the curl command boilerplate: the Quick Reference repeats the same three API queries that reappear in section 4's workflows; one canonical set with parameterized placeholders would suffice.

Consolidate free-tier constraints into a single section (currently split between 'Free Tier Limitations' and the 'Submitting New Samples' free-tier block) and reconcile the MITRE technique lists between frontmatter and body.

DimensionReasoningScore

Conciseness

The body is mostly high-value domain-specific content (query syntax, free-tier limits, operator recipes) that Claude cannot know, but it could be tightened: the Quick Reference curl boilerplate is repeated verbatim in section 4's workflows, free-tier limits appear in both section 2 and the 'Submitting New Samples' block, and two MITRE tables (frontmatter T1590/T1592 vs body T1590/T1592/T1595/T1596) partially duplicate. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'.

3 / 5

Actionability

The content is fully executable: copy-paste-ready curl commands with correct headers and payload syntax, complete Python heredoc scripts using real response field names (task.get('uuid'), threatName, iocs.sha256), and concrete query examples with realistic values covering common cases (hash, domain, IP, LOLBin, persistence, Suricata). This matches the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

Multi-step workflows (sections 4 and 5) are explicitly numbered with embedded conditionals ('Step 3: If match found, open sandbox session...'), the Error Handling & Edge Cases table provides problem→cause→solution feedback loops, and the Decision Gate section acts as a routing checklist. Operations are read-only lookups, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is a well-sectioned monolith: no references/, scripts/, or assets/ files exist, and the ~430-line body inlines a full query-field reference, wildcard tables, detection-signature tables, and operator recipes that would fit one level deep in a references/ file. Section headers give it real structure, so it sits above the 'minimal structure' anchor but matches 'some structure... content that should be separate is inline'.

3 / 5

Total

16

/

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 states what the skill does with concrete actions and a distinct niche. Its main weakness is the absence of an explicit 'when to use' trigger clause within the description field itself, which caps completeness, and slightly thin synonym coverage for natural user phrasings.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when the user mentions ANY.RUN, TI Lookup, or wants to enrich hashes, domains, or IPs with sandbox intelligence' — this would raise completeness from 3.

Include natural synonyms users would say, such as 'IOC lookup' or 'malware lookup', alongside the existing brand and indicator terms to improve trigger-term coverage.

Consider trimming the 'Covers...' meta-sentence into direct action verbs ('Query...', 'Correlate...', 'Integrate...') for a more directive tone.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'query hashes, domains, IPs, and behavioral indicators against ANY.RUN's sandbox corpus' plus 'TI Lookup query syntax, search operators, free tier constraints, result correlation with engagement findings, and integration with sandbox analysis' — giving comprehensive coverage of the skill's capabilities. It exceeds the level-4 anchor ('several specific actions; minor gaps') because no meaningful capability is left out.

5 / 5

Completeness

The 'what' is clear and specific, but the description contains no 'Use when...' clause or equivalent explicit trigger guidance — the when-to-use terms live in the separate metadata.when_to_use field. Per the rubric guideline, a missing explicit 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural terms are present ('ANY.RUN', 'Threat Intelligence Lookup', 'hashes, domains, IPs', 'sandbox corpus', 'behavioral indicators'), matching the 'good keyword coverage; a few natural terms missing' anchor. It falls short of 5 because common user phrasings like 'IOC lookup', 'malware lookup', or synonyms beyond the ANY.RUN brand are absent (they exist only in metadata.when_to_use, not the description).

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (ANY.RUN's TI Lookup product specifically) with brand-distinct triggers, so it is easily distinguishable from generic threat-intel or sandbox skills. Conflict risk is minimal, matching the level-5 anchor.

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-anyrun-lookup/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.