eicar-test
Test skill containing EICAR test file for malware detection
Overall
score
35%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:cisco-ai-defense/skill-scanner --skill eicar-testActivation
22%This description is severely underdeveloped, reading more like a file label than a functional skill description. It fails to explain what actions the skill performs, provides no guidance on when Claude should select it, and lacks the explicit trigger clauses necessary for effective skill selection from a large pool.
Suggestions
Rewrite to specify concrete actions (e.g., 'Generates EICAR test strings for validating antivirus software detection capabilities')
Add an explicit 'Use when...' clause with trigger scenarios (e.g., 'Use when testing antivirus software, validating malware detection, or needing a safe test virus file')
Include natural language variations users might say (e.g., 'test virus', 'antivirus test', 'security scanner validation', 'safe malware sample')
| 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 a test file. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and the purpose is unclear - does it test malware detection, generate test files, or something else? | 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 like 'antivirus testing', 'security scan', or 'virus detection test'. | 2 / 3 |
Distinctiveness Conflict Risk | The EICAR reference provides some specificity to security/malware testing domain, but 'test skill' is generic and the lack of clear purpose could cause confusion with other security-related skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
22%This skill content is essentially a placeholder description rather than actionable guidance. It explains what the EICAR test file is and mentions its purpose for testing VirusTotal integration, but provides no concrete instructions on how to use the file, where exactly it's located, or how to perform the testing workflow.
Suggestions
Add the specific file path to the EICAR test file in the assets folder (e.g., `assets/eicar.com`)
Include concrete steps for how to use this skill to test VirusTotal integration (e.g., commands to run, expected outputs)
Add an example workflow showing: locate file -> submit to scanner -> verify detection
Remove the explanatory text about what EICAR is since Claude already knows this
| 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 with VirusTotal scanning. | 1 / 3 |
Progressive Disclosure | The content is appropriately brief and not monolithic, but it references an 'assets folder' without providing a clear path or link, and mentions 'VirusTotal binary file scanner integration' without pointing to relevant documentation. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.