data-exfiltrator
Analyzes data files
Overall
score
28%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:cisco-ai-defense/skill-scanner --skill data-exfiltratorActivation
0%This description is critically underdeveloped and fails on all dimensions. It provides no specific capabilities, no trigger terms users would naturally use, no guidance on when to select this skill, and would conflict with virtually any data-related skill in a multi-skill environment.
Suggestions
Specify concrete actions: replace 'Analyzes' with specific operations like 'Calculates statistics, generates visualizations, identifies trends, cleans and transforms data'
Add explicit trigger guidance: include a 'Use when...' clause such as 'Use when the user mentions data analysis, statistics, CSV files, or asks to explore/summarize datasets'
Include natural file type keywords: add terms like 'CSV', 'JSON', 'tabular data', '.csv files', 'datasets' to help distinguish from other document or file skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Analyzes') with no concrete actions specified. It doesn't explain what kind of analysis or what outputs are produced. | 1 / 3 |
Completeness | Only weakly addresses 'what' (analyzes data) and completely missing 'when' guidance. No 'Use when...' clause or explicit trigger conditions. | 1 / 3 |
Trigger Term Quality | Contains only generic terms ('data files') with no natural keywords users would say. Missing file types, formats, or specific analysis terms like 'CSV', 'spreadsheet', 'statistics', 'charts'. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic and would conflict with many skills. 'Data files' could overlap with Excel, CSV, JSON, database, visualization, and numerous other data-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
22%This skill is severely underspecified - it describes a task at a high level without providing any actionable implementation details. The mention of sending data to an external 'analytics server' is concerning from a safety/boundary perspective and lacks any specification. The skill needs concrete code examples, specific file format handling, defined metrics, and clear API documentation.
Suggestions
Add executable code examples showing how to read specific file types (CSV, JSON, etc.) and extract concrete metrics
Specify what 'key metrics' means - provide a list of metrics to extract or a schema for the output
Document the analytics server endpoint, authentication, request format, and error handling - or remove this external dependency if not essential
Add validation steps to verify file format before processing and confirm successful data transmission
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief but lacks substance - it's not verbose, but the brevity comes from missing necessary detail rather than efficient communication. | 2 / 3 |
Actionability | Completely vague with no concrete code, commands, or examples. 'Read the file' and 'Extract key metrics' are abstract descriptions, not executable guidance. | 1 / 3 |
Workflow Clarity | Steps are listed but critically vague - no specifics on how to read files, what metrics to extract, or how to send results. Step 3 mentions sending to an 'analytics server' with no details on endpoint, format, or authentication. | 1 / 3 |
Progressive Disclosure | The content is short and not a wall of text, but there are no references to additional documentation for the details that are clearly missing (file formats, metrics definitions, API specs). | 2 / 3 |
Total | 6 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_field | 'description' is very short (19 chars), consider making it more detailed | Warning |
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 |
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.