file_operations
Skill17 starsChanged 4 months agoMITView on GitHub
Create, read, write, edit, move, copy, and delete files and directories
In this repository12 other files it gives its agents.
- app_controlSkill
- aws_opsSkill
- code_executionSkill
- desktop_automationSkill
- docker_deploySkill
- gitlab_apiSkill
- gitlab_pages_ciSkill
- ops_dns_regruSkill
- ops_reverse_proxySkill
- ops_tmux_remote_deploySkill
- system_infoSkill
- vps_host_sshSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use shell commands for file and directory work.
- Distinctive: line 133
Use absolute paths or paths relative to the working directory.
- Very specific: line 134
After creating files, verify with ls -la.
- Very specific: line 135
Use mkdir -p for nested directories.
- Distinctive: line 136
Before deleting, confirm with the user what will be removed.
- Very specific: line 137
Use cat for small files; head/tail for large ones.
- Very specific: line 138
Prefer cat << 'EOF' (single-quoted EOF) to avoid accidental variable expansion.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
File operations
Use shell commands for file and directory work.
Create
Single line:
echo "content" > /path/to/file.txtHere-doc:
cat > /path/to/file.txt << 'EOF'
Line 1
Line 2
Line 3
EOFEmpty file:
touch /path/to/file.txtRead
Whole file:
cat /path/to/file.txtFirst N lines:
head -n 10 /path/to/file.txtLast N lines:
tail -n 10 /path/to/file.txtWrite / append
Overwrite:
echo "new content" > /path/to/file.txtAppend:
echo "more content" >> /path/to/file.txtDirectories
Create:
mkdir -p /path/to/new/directoryList:
ls -la /path/to/directoryCopy / move / delete
Copy file:
cp /source/file.txt /destination/file.txtCopy tree:
cp -r /source/dir /destination/dirMove or rename:
mv /old/path/file.txt /new/path/file.txtDelete file:
rm /path/to/file.txtDelete directory:
rm -r /path/to/directoryFind
By name:
find /search/path -name "*.txt" -maxdepth 3By content:
grep -r "search text" /search/path --include="*.txt"Rules
- Use absolute paths or paths relative to the working directory.
- After creating files, verify with
ls -la. - Use
mkdir -pfor nested directories. - Before deleting, confirm with the user what will be removed.
- Use
catfor small files;head/tailfor large ones. - Prefer
cat << 'EOF'(single-quoted EOF) to avoid accidental variable expansion.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

