Agent skill

File Ops

by amd in amd/gaia

Read, write, and edit files on disk safely — locate the right file, change only what was asked, and confirm before anything destructive.

MITAuto-check passed

Install File Ops

skills CLI
$ npx skills add amd/gaia --skill file-ops -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install amd/gaia file-ops --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/amd/gaia.git skills-src && mkdir -p .claude/skills && cp -r skills-src/hub/skills/file-ops .claude/skills/file-ops && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
file-ops
GitHub stars
1.6k
Token cost
~926 tokens
SKILL.md length
492 words
Files
1
Skills in repo
44
Repo updated
First seen
Licence
MIT

At a glance

Read, write, and edit files on disk safely — locate the right file, change only what was asked, and confirm before anything destructive.

  • Works in 6 steps: Find it before you touch it. Don't guess… → Read before you write or edit.… → Prefer edit_file over write_file for… → …
  • The user wants a file read
  • SKILL.md covers Procedure, Guardrails are not bugs, What this skill does not cover and Fork this
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

File Ops is an agent skill from amd/gaia. Read, write, and edit files on disk safely — locate the right file, change only what was asked, and confirm before anything destructive. Use when the user wants a file read, created, modified, or searched for by name or content.

Its SKILL.md is about 930 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Build AI agents for your PC. The licence is MIT.

When your agent uses it

  • The user wants a file read
  • Searched for by name

Example prompts

  • “/file-ops”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Find it before you touch it. Don't guess a path from memory or the
  2. Read before you write or edit. read_file(file_path) first, every
  3. Prefer edit_file over write_file for existing files. edit_file
  4. When edit_file fails with "content not found," re-read the file.
  5. Confirm before anything destructive. Overwriting a file whose existing
  6. Report what actually changed. State the path, and for edits, name what

What it can do on your machine

Read from SKILL.md and the folder at commit 6c3bb5c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

File Ops loads about 926 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 492 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~926

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from amd/gaia at commit 6c3bb5c, republished under its MIT licence (© amd). 492 words, ~926 tokens.

Download SKILL.mdSave it as .claude/skills/file-ops/SKILL.md (or your agent's skills folder).
name
file-ops
description
Read, write, and edit files on disk safely — locate the right file, change only what was asked, and confirm before anything destructive. Use when the user wants a file read, created, modified, or searched for by name or content.
license
MIT
version
1.0.0

File Ops

Touching a file on someone's disk is not like answering a question — a wrong guess doesn't just look bad, it overwrites something they cannot get back. Slow down in proportion to how hard the change is to undo.

Procedure

  1. Find it before you touch it. Don't guess a path from memory or the user's description. Use find_files(query) for "the report from last week" style requests, or search_file_content(pattern) when you know a string that must be inside the file but not which file it's in. Confirm the exact path with get_file_info before acting on it — a near-miss filename is easy to write to by accident.
  2. Read before you write or edit. read_file(file_path) first, every time — even for a file you edited two turns ago. It may have changed since, and edit_file only succeeds against the file's current exact content.
  3. Prefer edit_file over write_file for existing files. edit_file replaces one exact string (old_content → new_content); it only changes what you targeted. write_file replaces the entire file — reach for it only when creating a new file or when you genuinely mean to replace everything.
  4. When edit_file fails with "content not found," re-read the file. Do not retry with a guessed variation of the string. The failure means your copy of the file is stale or the whitespace doesn't match byte-for-byte — rewriting from memory to force it through is how you silently discard whatever changed since you read it.
  5. Confirm before anything destructive. Overwriting a file whose existing content is unrelated to the new content, replacing most of a file in one edit_file call, or writing to a path that already holds something important — stop and ask with request_user_input first. A backup gets created automatically on overwrite/edit, but "recoverable with effort" is not the same as "the user expected this."
  6. Report what actually changed. State the path, and for edits, name what changed rather than pasting the whole diff back at the user unless they ask for it.
Show full SKILL.md (161 more words)Show less

Guardrails are not bugs

write_file and edit_file refuse system directories, credential-bearing dotfiles such as environment files and SSH key directories, and anything above a 10 MB size limit — these are the platform's sandbox, not something to route around. If a write is denied, that is the answer; report it and ask the user where they'd actually like the file, don't look for another tool that skips the check.

What this skill does not cover

read_file is for text — Python, Markdown, config, plain text. It refuses binary document formats (PDF, DOCX, XLSX, and similar) outright, because reading them raw produces garbage the model then reasons over as if it were real content. Those need index_document + query_documents instead — see the document-brief skill.

Fork this

Pin step 1 to a project's actual file layout (config always lives at X, generated output always goes to Y) and the search step collapses to a direct path, turning this into a fast in-place editor for one codebase.

© amd, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in hub/skills/file-ops of amd/gaia.

Open the folder on GitHubat commit 6c3bb5c

Compare with similar skills

File Ops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

File Ops compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
File Ops this skillamd/gaia1.6k—~926Automated safety check: PassMIT
Email Opsaffaan-m/ECC274k1 repos~1.1kAutomated safety check: PassMIT
Knowledge Opsaffaan-m/ECC274k2 repos~1.7kAutomated safety check: PassMIT
Research Opsaffaan-m/ECC274k2 repos~902Automated safety check: PassMIT
Terminal Opsaffaan-m/ECC274k2 repos~750Automated safety check: PassMIT
Messages Opsaffaan-m/ECC274k1 repos~724Automated safety check: PassMIT

Similar skills

  • Email Ops

    affaan-m/ECC

    Evidence-first mailbox triage, drafting, send verification, and sent-mail-safe follow-up workflow for ECC.

    274k GitHub starsUsed in 1 repo~1.1k tokens
    Writing & ContentAuto-check passed
  • Knowledge Ops

    affaan-m/ECC

    Knowledge base management, ingestion, sync, and retrieval across multiple storage layers (local files, MCP memory, vector stores, Git repos).

    274k GitHub starsUsed in 2 repos~1.7k tokens
    Knowledge ManagementAuto-check passed
  • Research Ops

    affaan-m/ECC

    Evidence-first current-state research workflow for ECC. An agent skill from affaan-m/ECC.

    274k GitHub starsUsed in 2 repos~902 tokens
    Research & ScienceAuto-check passed
  • Terminal Ops

    affaan-m/ECC

    Evidence-first repo execution workflow for ECC. An agent skill from affaan-m/ECC.

    274k GitHub starsUsed in 2 repos~750 tokens
    Testing & QAAuto-check passed
  • Messages Ops

    affaan-m/ECC

    Evidence-first live messaging workflow for ECC. An agent skill from affaan-m/ECC.

    274k GitHub starsUsed in 1 repo~724 tokens
    Productivity & AutomationAuto-check passed
  • GitHub Ops

    affaan-m/ECC

    GitHub repository operations, automation, and management. An agent skill from affaan-m/ECC.

    274k GitHub starsUsed in 2 repos~1.5k tokens
    DevelopmentAuto-check: warnings

More from amd/gaia

All 44 skills in this repo
  • Adds a release eval scorecard to a GAIA hub agent by writing a harness adapter, running a real eval, and wiring the result into the agent's README and release gate.

    1.6k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Walks through releasing a GAIA sidecar agent as a frozen binary plus npm client through the tag-triggered Agent Hub CI pipeline, with a human gate before publishing.

    1.6k GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Mines local Claude Code session transcripts with a deterministic Python pipeline to show what the agent is actually used for, how often it fails and what it costs.

    1.6k GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Benchmarks AMD's GAIA agent against Claude Code and across models on quality, honesty, steps, tokens, time and real cost, using gaia eval tasks.

    1.6k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Guides safe code changes by finding the right file with grep or semantic search, reading before editing, reproducing bugs first, and proving a fix with a real test run.

    1.6k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Walks through scaffolding, writing and testing a new GAIA agent as a Python class with the SDK, from the base Agent subclass to registered tool methods.

    1.6k GitHub stars~1.5k tokensUpdated today
    Auto-check passed

Questions about File Ops

What does File Ops do?

Read, write, and edit files on disk safely — locate the right file, change only what was asked, and confirm before anything destructive. File Ops is an agent skill from amd/gaia. Read, write, and edit files on disk safely — locate the right file, change only what was asked, and confirm before anything destructive.

When should I use File Ops?

File Ops fits situations like: the user wants a file read; searched for by name.

How do I install File Ops in Claude Code?

Run `npx skills add amd/gaia --skill file-ops -a claude-code`. Or copy the skill folder (hub/skills/file-ops in amd/gaia) into .claude/skills/file-ops in your project. Claude Code loads it when a task matches its description.

How do I install File Ops in Codex?

Run `npx skills add amd/gaia --skill file-ops -a codex`. Or copy the skill folder (hub/skills/file-ops in amd/gaia) into .agents/skills/file-ops in your project. Codex loads it when a task matches its description.

Can I use File Ops in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amd/gaia --skill file-ops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/file-ops, .gemini/skills/file-ops, .github/skills/file-ops and .opencode/skills/file-ops in your project.

What does File Ops need to run?

SKILL.md names no scripts, command-line tools or credentials: File Ops is instructions for the agent only.

Does File Ops access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is File Ops safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does File Ops use?

File Ops is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does File Ops use?

About 926 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to File Ops?

Skills that share tags, products or a category with File Ops: Email Ops (affaan-m/ECC, 274k stars), Knowledge Ops (affaan-m/ECC, 274k stars), Research Ops (affaan-m/ECC, 274k stars) and Terminal Ops (affaan-m/ECC, 274k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains File Ops?

amd (a GitHub organization) maintains it in amd/gaia, which has 1,580 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 6, 2026.

Source: amd/gaia on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.