Test skill containing EICAR test file for malware detection
50
Quality
22%
Does it follow best practices?
Impact
100%
1.17xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./evals/test_skills/malicious/eicar-test/SKILL.mdQuality
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is severely lacking in actionable information. It reads more like a label or file note than a functional skill description. It fails to explain what actions the skill performs, provides no guidance on when to use it, and doesn't help Claude distinguish this skill from others in a large skill library.
Suggestions
Add specific actions the skill performs (e.g., 'Generates EICAR test strings for validating antivirus software' or 'Tests malware detection capabilities').
Include an explicit 'Use when...' clause with trigger scenarios (e.g., 'Use when testing antivirus software, validating malware scanners, or when the user mentions EICAR, security testing, or AV validation').
Clarify the skill's purpose - is it for generating test files, validating detection systems, or something else entirely?
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Test skill containing') without describing any concrete actions. It doesn't explain what the skill does beyond mentioning it contains something. | 1 / 3 |
Completeness | The description only vaguely hints at what it contains but doesn't explain what actions it performs or when Claude should use it. No 'Use when...' clause or equivalent guidance is present. | 1 / 3 |
Trigger Term Quality | Contains some relevant technical terms ('EICAR test file', 'malware detection') that users familiar with security testing might use, but lacks common variations or natural language triggers. | 2 / 3 |
Distinctiveness Conflict Risk | The EICAR and malware detection terms provide some specificity, but 'test skill' is generic and the purpose is unclear, which could cause confusion with other security or testing-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder description rather than actionable guidance. It explains what the EICAR test file is and mentions its purpose for VirusTotal testing, but provides no concrete instructions on how to use the file, where exactly it's located, or what commands/code to run for the integration test.
Suggestions
Add the explicit path to the EICAR test file in the assets folder (e.g., `assets/eicar.com`)
Include concrete usage instructions or code example showing how to use this file with the VirusTotal scanner
Add a simple workflow: 1. Locate file, 2. Run scanner command, 3. Verify detection result
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but includes some unnecessary explanation about what EICAR is that Claude would already know. The description of EICAR being 'NOT a virus but detected by all antivirus software' is common knowledge for Claude. | 2 / 3 |
Actionability | The skill provides no concrete guidance, commands, or examples. It only describes what the skill contains and its purpose without any executable instructions on how to use it or what to do with the EICAR file. | 1 / 3 |
Workflow Clarity | There are no steps, processes, or workflows defined. The skill merely states its purpose without explaining how to actually use the test file or integrate it with VirusTotal scanning. | 1 / 3 |
Progressive Disclosure | The content is appropriately brief and not monolithic, but it mentions an 'assets folder' without providing a clear reference or path to it. For such a simple skill, the structure is acceptable but navigation could be clearer. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
c0a625f
Table of Contents
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.