ワンクリックで
file-modify-skill
Write new files or edit existing files with string replacement.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Write new files or edit existing files with string replacement.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Drive the user's real Chrome over raw CDP by writing Python against browser-harness helpers - screenshot, coordinate clicks, JS evaluation, form fill, tabs. For tasks needing full freedom or the user's own logins.
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
Deploy sites and apps to Vercel, inspect deployments, stream logs, and manage projects/env/domains via the Vercel CLI. Deploy a directory and get back the live deployment URL; everything else the CLI supports is available through the custom command passthrough.
Use this skill to generate well-branded interfaces and assets for MachinaOS (zeenie.ai), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.
Run AI-generated Python in a hard sandbox (Pydantic Monty) with enforced time + memory limits and opt-in capabilities. Use for untrusted code; supports a Python subset.
Interactive browser automation - navigate, click, type, fill forms, take screenshots, get accessibility snapshots. Supports system Chrome/Edge via auto-detection.
| name | file-modify-skill |
| description | Write new files or edit existing files with string replacement. |
| allowed-tools | file_modify |
| metadata | {"author":"machina","version":"1.0","category":"filesystem"} |
Write new files or edit existing files with exact string replacement. Uses deepagents filesystem backend.
Path sandbox: all paths resolve inside the per-workflow workspace root. Use workspace-relative paths (e.g. reports/summary.md); .. and ~ segments are rejected, and absolute paths are remapped into the workspace.
| Field | Type | Required | Description |
|---|---|---|---|
| operation | string | Yes | write (create or wholesale-replace the file) or edit (surgical find-and-replace inside an existing file) |
| file_path | string | Yes | Path to the file |
| content | string | If write | Full file content to write — overwrites any existing file at this path |
| old_string | string | If edit | Exact text to find and replace |
| new_string | string | If edit | Replacement text |
| replace_all | boolean | No | Replace all occurrences (default: false, old_string must be unique) |
Write a new file:
{
"operation": "write",
"file_path": "/path/to/new_file.py",
"content": "print('hello world')"
}
Edit an existing file:
{
"operation": "edit",
"file_path": "/path/to/file.py",
"old_string": "def old_name():",
"new_string": "def new_name():"
}
Replace all occurrences:
{
"operation": "edit",
"file_path": "/path/to/file.py",
"old_string": "TODO",
"new_string": "DONE",
"replace_all": true
}
Write:
{"operation": "write", "file_path": "/path/to/file.py"}
Edit:
{"operation": "edit", "file_path": "/path/to/file.py", "occurrences": 1}
write to create a new file or replace an existing file's contents wholesale. Provide the full new contents in content; any existing file at file_path is replaced.edit for surgical string replacement inside an existing file — it is the right choice when you want to change a small portion of a file rather than rewrite the whole thing.old_string must be unique in the file unless replace_all is true.edit over write when changing only part of an existing file — it produces a smaller diff and is less destructive.