manage-files

Read, write, list, and manage files within a plan directory.

4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/cuioss/plan-marshall --skill manage-files
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-files
Source: https://github.com/cuioss/plan-marshall/tree/main/marketplace/bundles/plan-marshall/skills/manage-files
Command: npx skills add https://github.com/cuioss/plan-marshall --skill manage-files

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires file_ops, input_validation, plan_logging, toon_parser, and includes scripts (resource) components.

What problem does it solve?

Plan-driven environments require reliable, generic file I/O operations within each plan directory without injecting domain-specific validation logic.

Core Features & Use Cases

  • Read, write, remove, and list files within a plan directory.
  • Create subdirectories, check existence, and atomically create-or-reference plan directories.
  • Operates independently of specific plan document formats; caller provides content.

Quick Start

Instruct the AI to read notes.md from a plan directory and return its contents.

Frequently Asked Questions about manage-files

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

FAQPage Schema
How do I read and write files in a plan directory without triggering domain-specific validation?

To read and write files in a plan directory without domain-specific validation, use generic file I/O operations that enforce input validation on plan_id and file paths while operating independently of specific document formats.

What is the best way to atomically create or update files within a plan directory?

The best way to atomically create or update files within a plan directory is to use generic file I/O operations that write atomically, check file existence, and create subdirectories while avoiding domain-specific logic.

How do I list and manage arbitrary plan files and subdirectories?

You list and manage arbitrary plan files and subdirectories by applying generic file operations to create, update, list, check existence, and remove files, returning plain outputs or structured statuses for tasks like existence checks.

Can I use generic file I/O for plan directories if I provide my own custom content?

Yes, you can use generic file I/O for plan directories with custom content because the operations operate independently of specific plan document formats, meaning the caller provides the content directly.

Does generic file management apply input validation to plan_id and file paths?

Generic file management applies input validation to plan_id and file paths to ensure safe read, write, list, and removal operations within the targeted plan directory structure.

What limitations exist when removing or checking the existence of plan files?

The limitation when removing or checking the existence of plan files is that generic file operations strictly avoid domain-specific validations, meaning the caller must handle any specialized content rules independently.