batch-operations

Apply operations across multiple files simultaneously. Pattern-based bulk modifications, search-and-replace across codebases, consistent changes to many files at once.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-5

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

The content is a model lean batch-operation skill: executable commands, a clear preview→execute→verify workflow with validation feedback loops, and clean section structure with no padding or nested references. Every token earns its place.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — a four-step protocol, copy-ready shell snippets, and a compact patterns table, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides copy-paste-ready executable commands (grep/find/sed, PowerShell pipeline, npm test/build) and a concrete template (What/Replace/Scope/Exclude) covering the common batch cases.	5 / 5
Workflow Clarity	Clear four-step sequence (Define → Preview → Execute → Verify) with explicit validation checkpoints and a feedback loop ('Should return empty' confirms no missed instances, then build+tests catch breakage), which is exactly the cap-lifting pattern required for batch operations.	5 / 5
Progressive Disclosure	A single self-contained SKILL.md under 50 lines with well-organized sections (When to Use, Protocol, Patterns, Safety) and no bundle files, so no nested references to navigate — well-structured for a simple skill.	5 / 5
	Total	20 / 20 Passed

Description

83%Weight 40%Scale 1-5

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 concise, concrete, third-person, and clearly answers both what the skill does and when to use it, with an explicit exclusion clause that sharply distinguishes it from single-file editing. Minor missing synonyms keep trigger_term_quality and specificity just below full marks.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('bulk modifications, search-and-replace across codebases, consistent changes to many files at once') naming the domain and multiple specific operations, with only minor coverage gaps (no file extensions or exact pattern syntax).	4 / 5
Completeness	Both 'what' (apply operations across multiple files / pattern-based bulk modifications) and 'when' (when the user needs to change multiple files with the same pattern, plus an explicit NOT-for exclusion) are clearly and explicitly answered with concrete triggers.	5 / 5
Trigger Term Quality	The when_to_use clause supplies natural phrases users say ('rename across a codebase, add imports to many files, update versions'), with good coverage but a few synonyms/extensions missing.	4 / 5
Distinctiveness Conflict Risk	A clear niche (multi-file pattern-based batch edits) with an explicit negative boundary ('NOT for single-file edits') minimizing conflict with single-file editing skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: vudovn/ag-kit
Path: .agents/skills/batch-operations/SKILL.md
Commit: 549ba3d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.