file-system

File System Skill

This built-in skill handles workspace path operations and plain text files only.

Capabilities

1. List Paths: Explore workspace files and directories.
2. Read Plain Text: Strictly decode and page through .txt, .md, .json, source code, logs, and similar text files up to 10 MiB.
3. Apply Text Patches: Create, update, move, or delete up to 100 plain-text files with one exact patch.
4. Rename Paths: Rename or move files and directories without parsing contents.
5. Delete Paths: Delete files or directories after confirmation.

Boundaries

• text_file_read and apply_patch refuse DOCX, PPTX, XLSX, XLS, and PDF paths.
• To read Office/PDF documents, use the bundled document-reader capability and document_read. If it was explicitly disabled, enable it in the capability store.
• To create or modify Office/PDF documents, use run_python_code with the appropriate document library.
• Path search is owned by command-tools through glob and grep.
• User confirmation is owned by interaction; delete confirmation uses the shared interaction bridge internally.
• With God Mode off, trusted reads can use paths outside the workspace. New files and edits within this run's artifact directory are allowed; changes elsewhere require an execution-layer approval for the exact operation. Use the artifact directory from the runtime context, not another run's directory. God Mode preserves existing access and delete confirmations. Write paths still reject symbolic links and directory junctions, and existing-file integrity checks always apply.

Usage Guidelines

• Prefer relative workspace paths.
• Use glob to discover paths and grep to locate matching lines. Neither tool returns the complete ordered file or grants a write credential.
• Before changing existing content, call text_file_read with offset=1 and no limit. A paged read never grants write audit even when it reaches the end of the file.
• Files with a recognized Unicode BOM or valid UTF-8 need no encoding argument. Other encodings must be explicit; decode failures are returned and never replaced or ignored.
• Use apply_patch for every plain-text creation or content change. The patch must start with *** Begin Patch, end with *** End Patch, and contain *** Add File, *** Update File, *** Delete File, optional *** Move to, and exact @@ hunks. Pure EOF additions require *** End of File.
• Use enough unchanged context to make each hunk unique. Matching is exact: whitespace and Unicode variants are not normalized.
• All deletes in one patch are confirmed together after preflight. Rejection or timeout leaves the entire patch unapplied.
• Multiple independent plain-text reads can be grouped through parallel_tools.
• Patches, renames, and deletes must stay as direct single-tool calls.