batch-file-processor
Batch File Processor - Auto-activating skill for Business Automation. Triggers on: batch file processor, batch file processor Part of the Business Automation skill category.
31
0%
Does it follow best practices?
Impact
86%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/batch-file-processor/SKILL.mdQuality
Discovery
0%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 essentially a placeholder with no substantive content. It fails on all dimensions: it names no concrete actions, provides no natural trigger terms, lacks both 'what' and 'when' guidance, and is indistinguishable from any generic file or automation skill. The duplicate trigger term suggests auto-generated boilerplate rather than a thoughtfully crafted description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Renames, moves, converts, or transforms multiple files in bulk based on user-defined rules.'
Include a 'Use when...' clause with natural trigger terms like 'process multiple files', 'bulk rename', 'batch convert', 'automate file operations', 'process files in a folder'.
Differentiate from other automation or file-handling skills by specifying the unique scope, such as supported file types, batch operations, or the automation context (e.g., 'Use when the user needs to apply the same operation across many files at once').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Batch File Processor' is a name, not a description of capabilities. There is no mention of what specific operations are performed on files. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is meaningfully answered. The description only states a category ('Business Automation') and repeats the skill name as a trigger, with no explicit use-case guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'batch file processor' repeated twice, which is not a natural phrase users would say. Missing natural terms like 'process multiple files', 'bulk operations', 'batch rename', or any specific file operations. | 1 / 3 |
Distinctiveness Conflict Risk | Extremely generic — 'batch file processor' and 'Business Automation' could overlap with virtually any file-handling or automation skill. There is nothing to distinguish this from other file processing or automation skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content. It consists entirely of meta-descriptions about what the skill supposedly does without providing any actual instructions, code, examples, or workflows for batch file processing. It reads like a template placeholder that was never filled in with real content.
Suggestions
Replace the abstract descriptions with concrete, executable code examples for common batch file processing tasks (e.g., renaming files, converting formats, processing CSVs in bulk).
Add a clear multi-step workflow with validation checkpoints, such as: enumerate files → validate inputs → process batch → verify outputs → handle errors.
Remove all meta-sections like 'When to Use', 'Example Triggers', and 'Capabilities' that describe the skill rather than teaching how to perform batch file processing.
Include specific tool/library recommendations with copy-paste ready code snippets (e.g., Python glob patterns, os.walk usage, parallel processing with concurrent.futures).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or concrete guidance. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero actionable content—no code, no commands, no specific steps, no examples of actual batch file processing. The 'Example Triggers' section just lists ways to ask for help rather than providing executable guidance. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to related files, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
c8a915c
- 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.