host-file-editing

Guide safe use of text_editor_remote for reading, writing, and patching files on the connected A0 CLI host. Use when the user asks to inspect or edit files on their computer, local files, CLI host files, or files that are explicitly not Docker/server files.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

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

A tight, well-structured instruction skill that assumes competence and gives specific tool-mode guidance. Its main weakness is the missing post-edit verification step in a destructive workflow, which caps workflow clarity.

Suggestions

Add a post-edit verification step to Editing Flow, e.g. "After a write or patch, re-read the affected region to confirm the change applied as intended."

Include one concrete patch_text example hunk showing the @@ anchor with + and - lines so the format is copy-paste ready.

Make the stale-patch feedback loop explicit as a validate -> reread -> retry cycle rather than a single inline mention.

Dimension	Reasoning	Score
Conciseness	Lean bullet-pointed guidance that assumes Claude knows the tool; no padding or explanation of basic concepts, and every line is actionable.	5 / 5
Actionability	Concrete, specific guidance on tool modes and patch-text rules, but the patch_text hunk format is described in prose without a copy-paste-ready example showing the @@ / + / - layout.	4 / 5
Workflow Clarity	Editing Flow gives a clear sequence and a stale-patch feedback loop, but as a destructive file-editing skill it lacks an explicit post-edit verification checkpoint, so the destructive-operation cap applies.	3 / 5
Progressive Disclosure	Under 50 lines with no need for external references and clearly organized into well-named sections (Boundary, Access Modes, Editing Flow, Patch Text Rules, Failure Handling), satisfying the simple-skill exception.	5 / 5
	Total	17 / 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 description that clearly answers what the skill does and when to use it, with a well-drawn boundary that distinguishes it from server-side file tools. Minor specificity and synonym gaps keep it just short of perfect.

Dimension	Reasoning	Score
Specificity	Names the tool and three concrete actions ("reading, writing, and patching files") but does not enumerate the sub-modes the body covers (write, patch, patch_text, edits), leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states both the what ("Guide safe use of text_editor_remote for reading, writing, and patching files on the connected A0 CLI host") and the when ("Use when the user asks to inspect or edit files...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ("inspect or edit files", "their computer", "local files", "CLI host files", "not Docker/server files") but misses a few common synonyms like "open" or "modify".	4 / 5
Distinctiveness Conflict Risk	The CLI-host boundary and the explicit "not Docker/server files" carve-out give it a clear niche with distinct triggers and minimal conflict risk against server-side file skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: agent0ai/agent-zero
Path: plugins/_a0_connector/skills/host-file-editing/SKILL.md
Commit: b22a144

Reviewed: 4 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.