filesystem_guide

Enforce workspace-only file access and require run_command for outside paths.

1.4k|169|Updated Mar 6, 2026

Search Tags:#guidance #safety #workspace #filesystem #shell #tools #restriction

Ready to run

npx skills add https://github.com/siddsachar/row-bot --skill filesystem-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: filesystem_guide
Source: https://github.com/siddsachar/row-bot/tree/main/tool_guides/filesystem_guide
Command: npx skills add https://github.com/siddsachar/row-bot --skill filesystem-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guidance helps teams avoid mixing workspace file operations with terminal commands, reducing accidental file access outside the workspace and promoting safer scripting within project environments.

Core Features & Use Cases

Enforces strict separation: workspace_read_file, workspace_list_directory, workspace_write_file, etc., can only operate inside the configured workspace folder.
Safe outside-workflow handling: When paths lie outside the workspace, the prescribed approach is run_command to perform actions without compromising local data security.
Use Case: In a multi-repo project, ensure scripts manipulating repository files never access user directories, preserving integrity and privacy.

Quick Start

Follow these rules by using workspace tools only inside the workspace folder and invoking run_command for any outside-path operation.

Frequently Asked Questions about filesystem_guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I restrict file operations to a local project workspace?▼

To restrict file operations to a local project workspace, use designated tools like workspace_read_file and workspace_write_file, which enforce strict path boundaries and prevent accidental access to outside directories.

What is the safe way to access files outside the workspace folder in a script?▼

The safe way to access files outside the workspace folder is to use run_command, ensuring that outside-path actions are executed securely without compromising local data integrity or privacy.

Can I use shell commands for listing directories inside the workspace?▼

You should not use shell commands for listing directories inside the workspace. Instead, use the dedicated workspace_list_directory tool to maintain safe usage boundaries.

Why should I separate workspace file tools from terminal commands in multi-repo projects?▼

Separating workspace file tools from terminal commands in multi-repo projects prevents scripts manipulating repository files from accidentally accessing user directories, preserving system integrity and data privacy.

When do I need to use run_command instead of workspace_write_file?▼

You need to use run_command instead of workspace_write_file whenever the target file path lies outside the configured workspace folder, ensuring external modifications are handled safely.