CtrlK
BlogDocsLog inGet started
Tessl Logo

apply-patch

Apply multi-file or tricky edits atomically with git apply instead of many fragile edit_file calls. Use when changing several files at once or when edit_file fails to match.

76

Quality

93%

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

SKILL.md
Quality
Evals
Security

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.

An exemplar short-form skill: executable commands, an explicit validation step, and an error-recovery feedback loop packed into a well-organized body with no wasted tokens. The only minor note is the trailing reference to a 'verify-changes skill' that is not part of this bundle.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: the single-paragraph intro only states what edit_file lacks and why git apply is the alternative, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides copy-paste-ready commands (`git apply --check changes.patch`, `git apply changes.patch`, the `-p0` caveat) plus a concrete unified-diff template, covering the common cases fully.

5 / 5

Workflow Clarity

A clearly numbered sequence with an explicit validation checkpoint (step 2, `--check`) and a feedback loop in step 4 (reject → re-read lines → regenerate diff → retry) for an atomic batch operation.

5 / 5

Progressive Disclosure

Under 50 lines with no external references needed; content is organized into well-signaled sections (Procedure, When to prefer this), meeting the simple-skill exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

87%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.

A strong, concise description that clearly states both capability and trigger conditions with concrete, natural-language phrasing. Minor keyword/coverage gaps keep specificity and trigger_term_quality just below the top anchor.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Apply multi-file or tricky edits atomically with git apply', 'instead of many fragile edit_file calls' — with only minor coverage gaps (e.g., no mention of re-applying external patches, which appears only in the body).

4 / 5

Completeness

Explicitly answers both what ('Apply multi-file or tricky edits atomically with git apply') and when ('Use when changing several files at once or when edit_file fails to match') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say such as 'changing several files at once' and 'edit_file fails to match', plus the keyword 'git apply'; a few common synonyms (e.g. 'patch', 'diff') are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — atomic multi-file patch application via git — with distinct triggers that are unlikely to fire for unrelated editing skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
agentscope-ai/agentscope-java
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.