Filesystem logo

Filesystem

Community
Mathews-Tom
filesystem

File and directory operations via Claude Code built-in tools, replacing the Filesystem MCP server. Triggers on: "read this file", "write to file", "edit file", "find files matching", "search for text in files", "list directory", "show directory tree", "rename file".

Overview

PublisherMathews-Tom
Repositoryarmory
Skill namefilesystem
Stars
318
Forks
47
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Mathews-Tom on GitHub. Read the source before you install it.

Installation

Install the Filesystem AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Mathews-Tom/armory.git /tmp/armory
mkdir -p .claude/skills
cp -r /tmp/armory/skills/filesystem .claude/skills/filesystem
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Filesystem in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Filesystem on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Filesystem is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Filesystem

All file and directory operations use Claude Code's built-in tools. No MCP server needed — native tools are faster, more capable, and cost zero context tokens when idle.

Quick Reference

Filesystem MCP ToolReplacementNotes
read_file(path)Read toolSupports line offset and limit
read_multiple_files(paths)Multiple parallel Read callsFaster than sequential MCP calls
write_file(path, content)Write toolOverwrites entire file
edit_file(path, edits)Edit toolExact string replacement; surgical edits
list_directory(path)Glob or Bash lsGlob for patterns, ls for simple listing
directory_tree(path)Bash fd or Glob **/*fd is fastest; Glob for pattern filtering
search_files(pattern, path)Grep toolFull regex, file type filters, context lines
create_directory(path)Bash mkdir -p-p creates intermediate directories
move_file(src, dst)Bash mvAlso handles renames
get_file_info(path)Bash stat or Bash ls -laSize, permissions, timestamps
list_allowed_directoriesN/AClaude Code operates in the working directory; no sandbox restrictions

Reading Files

Read a Single File

Use the Read tool with an absolute path:

text
Read: /path/to/file.py

For large files, use offset and limit to read specific sections:

text
Read: /path/to/file.py (offset: 100, limit: 50)

This reads 50 lines starting from line 100. Use this for files with thousands of lines to avoid flooding context.

Read Multiple Files in Parallel

Issue multiple Read calls in a single response. Claude Code executes them concurrently:

text
Read: /path/to/file1.py
Read: /path/to/file2.py
Read: /path/to/file3.py

Parallel reads are faster than the MCP's read_multiple_files which serialized internally.

Read Images and PDFs

The Read tool handles binary formats:

  • Images (PNG, JPG, SVG): displayed visually
  • PDFs: extracted text; use pages: "1-5" for large documents (max 20 pages per call)

Writing and Editing Files

Write a New File

Use the Write tool to create a file or overwrite an existing one:

text
Write: /path/to/new-file.py
Content: <full file content>

The Write tool requires reading the file first if it already exists. For new files, write directly.

Edit an Existing File

Use the Edit tool for surgical modifications — replace exact string matches:

text
Edit: /path/to/file.py
old_string: "def old_function():"
new_string: "def new_function():"

The Edit tool fails if old_string is not unique in the file. Provide enough surrounding context to make the match unique, or use replace_all: true for find-and-replace across the entire file.

Prefer Edit over Write for existing files. Edit preserves everything outside the changed region and shows a clear diff. Write replaces the entire file.


Finding Files

By Name Pattern (Glob)

text
Glob: **/*.py           → all Python files recursively
Glob: src/**/*.ts       → TypeScript files under src/
Glob: *.md              → Markdown files in current directory
Glob: **/test_*.py      → test files anywhere in the tree

Results are sorted by modification time (most recent first).

By Content (Grep)

text
Grep: pattern="def process_data" type="py"
Grep: pattern="TODO|FIXME" glob="*.py"
Grep: pattern="class.*Controller" output_mode="content" -C=2
Grep ParameterPurpose
patternRegex pattern to match
typeFile type filter (py, js, ts, rust, go, etc.)
globGlob pattern filter (*.tsx, src/**/*.py)
output_modefiles_with_matches (default), content, count
-C, -A, -BContext lines: around, after, before matches
-iCase-insensitive search

Directory Listing

Simple listing:

bash
ls -la /path/to/directory

Recursive tree with fd:

bash
fd . /path/to/directory --type f

Tree with depth limit:

bash
fd . /path/to/directory --type f --max-depth 2

Filter by extension:

bash
fd -e py /path/to/directory

File Operations

Create Directory

bash
mkdir -p /path/to/new/directory

The -p flag creates all intermediate directories. Always verify the parent path exists first with ls.

Move / Rename

bash
mv /path/to/source.py /path/to/destination.py

Rename a file (same directory):

bash
mv /path/to/old-name.py /path/to/new-name.py

Move a directory:

bash
mv /path/to/source-dir /path/to/destination-dir

Copy

bash
cp /path/to/source.py /path/to/destination.py
cp -r /path/to/source-dir /path/to/destination-dir

Delete

bash
rm /path/to/file.py
rm -r /path/to/directory

Always confirm with the user before deleting files or directories.

File Metadata

bash
stat /path/to/file.py
ls -la /path/to/file.py
wc -l /path/to/file.py
CommandReturns
statSize, permissions, timestamps, inode
ls -laPermissions, owner, size, modification date
wc -lLine count
fileMIME type detection

Common Workflows

Find and Replace Across Files

bash
# Find all files containing the old string
Grep: pattern="old_function_name" type="py" output_mode="files_with_matches"

# Then Edit each file
Edit: /path/to/file1.py (old_string → new_string, replace_all: true)
Edit: /path/to/file2.py (old_string → new_string, replace_all: true)

Explore an Unfamiliar Codebase

  1. Check project structure: fd . --type f --max-depth 2
  2. Read configuration: Read: package.json or Read: pyproject.toml
  3. Find entry points: Grep: pattern="def main|if __name__" type="py"
  4. Read key files identified above

Find Large Files

bash
fd --type f --exec stat -f '%z %N' {} \; | sort -rn | head -20

Error Handling

ErrorCauseResolution
Read: file not foundPath incorrect or file deletedVerify with ls or Glob
Edit: old_string not uniqueMultiple matches in the fileAdd more surrounding context to make it unique
Edit: old_string not foundContent changed since last readRe-read the file, then retry with current content
Write: file not read firstAttempting to overwrite without readingRead the file first, then Write
Permission deniedInsufficient OS permissionsCheck with ls -la; use chmod if appropriate
Glob: no files foundPattern too restrictiveBroaden the pattern; check path spelling

Limitations

  • Read returns up to 2000 lines by default. Use offset/limit for larger files.
  • Read truncates lines longer than 2000 characters.
  • Edit requires exact string matching — whitespace and indentation must match precisely.
  • Write overwrites the entire file. No append mode. To append, read first, then write the combined content.
  • Glob only matches files, not directories. Use Bash ls or fd to list directories.
  • PDF reading is limited to 20 pages per call. Specify page ranges for large documents.

Calibration Rules

  1. Read before Edit. Always read a file before editing it. The Edit tool enforces this.
  2. Edit over Write for existing files. Edit is surgical and shows diffs. Write is a full replacement — use it only for new files or complete rewrites.
  3. Glob over Bash for file search. Glob is optimized for pattern matching. Only fall back to fd or find for queries Glob cannot express (size filters, date filters).
  4. Grep over Bash for content search. Grep is optimized for ripgrep-based search with proper permissions. Never use grep or rg via Bash.
  5. Parallel reads for multiple files. Issue all Read calls in a single response for concurrent execution.
  6. Always use absolute paths. Claude Code tools require absolute paths. Never pass relative paths to Read, Write, or Edit.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Filesystem AI skill do?

File and directory operations via Claude Code built-in tools, replacing the Filesystem MCP server. Triggers on: "read this file", "write to file", "edit file", "find files matching", "search for text in files", "list directory", "show directory tree", "rename file".

Why use Filesystem on TypingMind?

Because you install it once and use it with any model. Filesystem is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Filesystem in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Mathews-Tom/armory/tree/main/skills/filesystem. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Filesystem?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Filesystem?

As many as you like. As long as a model supports skills, you can use Filesystem with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Filesystem AI skill free?

Yes. It is published on GitHub by Mathews-Tom under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇