CtrlK
BlogDocsLog inGet started
Tessl Logo

batch

Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use `/batch` followed by operation and file pattern.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/core/src/skills/bundled/batch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete templates and clear sequencing, but it carries redundancy (a duplicated constraints table), lacks a verification feedback loop for a batch operation, and is monolithic rather than progressively disclosed.

Suggestions

Add a post-batch verification step (e.g., re-run lint/typecheck or confirm files still parse) before reporting success, creating a validate→fix→retry loop for this destructive/batch operation.

Remove the 'Constraints and Limits' table or replace it with a one-line pointer to Step 2, since it duplicates the chunking and size limits already stated there.

Move the worker-agent prompt template, full usage examples, and dry-run block into reference files (e.g., references/prompt-template.md, examples.md) and link to them from the overview to enable progressive disclosure.

DimensionReasoningScore

Conciseness

The content is instruction-dense and not padded with basic concepts, but the 'Constraints and Limits' table duplicates Step 2 rules and the three full usage-example flows add length that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready guidance — a concrete chunking table, a full worker-agent prompt template, explicit glob/exclusion lists, and an exact output format — well beyond pseudocode.

3 / 3

Workflow Clarity

The 5-step sequence is clear with discovery checkpoints (empty-batch abort, 50/100-file warnings), but as a batch/destructive operation it lacks a post-modification validation/verification feedback loop, capping it at 2.

2 / 3

Progressive Disclosure

Sections are well-organized, but the ~295-line skill is monolithic with no bundle files — content like the prompt template, exclusions, and examples is all inline rather than split into one-level-deep references.

2 / 3

Total

9

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinct, naming several concrete actions and occupying a clear niche, but it provides invocation syntax rather than explicit 'use when' trigger guidance and lacks coverage of natural phrasing variations.

Suggestions

Add an explicit 'Use when...' clause with scenario-based triggers, e.g. 'Use when applying an operation across many files at once or when the user asks to batch-process files.'

Broaden trigger terms to include natural variations users would say, such as 'apply to all files', 'across many files', or 'in bulk'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'discovers files, splits into chunks, and processes with parallel worker agents' — matching the top anchor for listing several specific concrete actions.

3 / 3

Completeness

Clearly states what the skill does, but the 'when' is given only as invocation syntax ('Use `/batch` followed by operation and file pattern') rather than an explicit scenario-based trigger, capping completeness at 2 per the missing-'Use when' guideline.

2 / 3

Trigger Term Quality

Has relevant natural terms ('batch operations', 'files in parallel') but is tied to the `/batch` invocation syntax and lacks common variations like 'apply to all files' or 'across many files'.

2 / 3

Distinctiveness Conflict Risk

The parallel-worker-agent framing plus the explicit `/batch` invocation carve a clear niche unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
QwenLM/qwen-code
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.