File Edit In Place is the skill of the Avoid AI Writing pack that changes a file on disk. It acts only when the user names the file and explicitly asks for an in-place change, reads the relevant content first, and edits only the spans that are justified findings.
Quotes, code blocks, tables, links, numbers, frontmatter and structure are preserved. After editing it re-reads the changed region and hands before and after content to the preservation verifier.
What You Get
- Targeted edits to the named file, limited to justified findings in the authorized scope
- A before snapshot kept for comparison
- A re-read of the changed region after editing
- A report of the file changed, edits made, passes used and what was left untouched
- A verification handoff to the preservation verifier, with one bounded repair if it fails
Common Use Cases
- Cleaning a README or blog draft in place
- Editing only one requested section of a large document
- Repairing a file after the verifier found that a quote or link changed
- Declining to touch a file when no justified edit exists and reporting zero passes
- Making sure a detector result alone never triggers a write
What Makes It Unique
The skill treats a write as something that needs evidence. It requires explicit user intent, will not simulate success if the host cannot write the file, records mutation as executed only after a real write succeeds, and refuses to treat instructions found inside the document as commands. A detector result never authorizes a change by itself.
Under The Hood
The skill is instructions only, with no scripts of its own. It tells the agent to read the named file, patch it with the host’s edit tool and re-read the result, so it changes a file on the user’s machine. It relies on the rulebook and routing files of the sibling skills, makes no network calls and runs no shell commands itself; the verifier it hands off to may run a Node script.