write-mode

Remove the .gemini_readonly marker to enable write mode after user authorization.

18|3|Updated Nov 13, 2025

Search Tags:#automation #authorization #safety #filesystem #read-only #write-mode #marker-file

Ready to run

npx skills add https://github.com/mystilleef/gemini-cli-modes --skill write-mode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-mode
Source: https://github.com/mystilleef/gemini-cli-modes/tree/main/skills/write-mode
Command: npx skills add https://github.com/mystilleef/gemini-cli-modes --skill write-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

When explicit user authorization is provided, this skill enables write mode by removing the read-only safety marker so subsequent actions can modify files.

Core Features & Use Cases

Enables targeted write access by deleting the .gemini_readonly marker only after explicit consent.
Maintains a safety-first workflow by keeping read-only restrictions until authorization is granted.
Scales to lightweight automation that requires temporary write permissions during a task.

Quick Start

After the user authorizes changes, invoke the enable script to remove the marker and enable write mode.

Frequently Asked Questions about write-mode

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

FAQPage Schema

How do I enable write access for filesystem automation after authorizing changes?▼

To enable write access for filesystem automation, you must invoke the enable script to remove the .gemini_readonly marker file after providing explicit user authorization for the task.

What is the purpose of a read-only marker file in safety-first automation workflows?▼

A read-only marker file maintains safety-first workflows by keeping filesystem restrictions active until explicit consent is granted, ensuring authorized tasks only receive temporary write permissions during execution.

How do I safely disable read-only filesystem restrictions for targeted automation tasks?▼

You safely disable read-only filesystem restrictions by explicitly authorizing changes and invoking the enable script, which removes the marker file and enables deterministic write access for the targeted task.

When do I need to remove the .gemini_readonly marker file during a task?▼

You need to remove the .gemini_readonly marker file when explicit user authorization is provided to disable safety restrictions and allow subsequent actions to modify files during lightweight automation.

Does enabling write mode permanently disable filesystem safety restrictions?▼

No, enabling write mode by removing the marker file applies to authorized tasks requiring temporary write permissions, maintaining a safety-first workflow by keeping read-only restrictions active until explicit consent is granted.

Can I use write-mode automation for lightweight tasks requiring temporary write permissions?▼

Yes, write-mode automation scales to lightweight tasks requiring temporary write permissions, deleting the read-only safety marker only after explicit consent to ensure authorized actions can modify files.