write_file

Create or overwrite workspace files after validating paths against .parallxignore rules.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/mufarosean/Parallx --skill write-file
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write_file
Source: https://github.com/mufarosean/Parallx/tree/main/.parallx/skills/write_file
Command: npx skills add https://github.com/mufarosean/Parallx --skill write-file

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing files directly in a shared workspace can lead to accidental data loss or unsafe changes. This Skill automates safe creation or overwriting of workspace files by validating target paths against .parallxignore sandbox rules and requiring explicit user approval before executing the write.

Core Features & Use Cases

  • Safe file writes: create or overwrite files only after path validation against sandbox rules.
  • Sandbox protection: prevents writes that would violate workspace sandbox constraints.
  • Approval gating: requires explicit user approval before performing the write operation.
  • Use Case: generate configuration files, templates, or logs within a project directory while maintaining safety.

Quick Start

Provide the relative path and the full content, and then approve the operation to write the file.

Frequently Asked Questions about write_file

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

FAQPage Schema
How do I safely create or overwrite files in a workspace sandbox?

To safely write workspace files, the Skill validates target paths against .parallxignore sandbox rules and requires explicit user approval before executing the file overwrite or creation.

Can I generate configuration files and templates without risking accidental data loss?

Yes, generating configuration files and templates is safe because the Skill enforces sandboxed path validation and approval gating to prevent accidental data loss during file creation.

How do I update log or output files within a controlled project directory?

Updating log or output files requires providing the relative path and full content, then explicitly approving the workspace write operation after sandbox path validation succeeds.

Does the file write operation bypass sandbox constraints if I provide the full content?

No, providing full content does not bypass constraints; the Skill enforces .parallxignore path checks to ensure the file write complies with workspace sandbox rules before approval.

What happens if a target file path violates the .parallxignore sandbox rules?

If a target file path violates .parallxignore sandbox rules, the write operation is blocked to maintain workspace protection and prevent unsafe changes to the file system.

Do I need explicit approval every time I want to write to a workspace file?

Yes, explicit user approval is required before performing every file write operation, ensuring that no workspace files are created or overwritten without direct user confirmation.