file-handler

Save, fetch, and search files within a .skillz directory tree.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill file-handler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-handler
Source: https://github.com/paulnsorensen/skillz-that-grillz/tree/main/skills/file-handler
Command: npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill file-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It solves the problem of scattered, inconsistent scratch files by giving skills a predictable on-disk convention for saving and retrieving their working notes, plans, and artifacts.

Core Features & Use Cases

  • Predictable artifact storage layout: Persists files under a consistent .skillz/<type>/<slug> tree so users and skills can reliably locate prior outputs.
  • Simple retrieval and discovery: Fetches saved content by type+slug and searches across both titles (slug names) and bodies (full text) to find what was written earlier.
  • Safety guardrails for slugs: Enforces a strict slug format to prevent path traversal and accidental misuse, keeping artifacts scoped to the intended directory buckets.

Quick Start

Use the file-handler skill to save a plan by telling it: “Save this as a todo note with slug release-cut.”

Frequently Asked Questions about file-handler

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

FAQPage Schema
How do I save scratch notes and plans generated during a workflow to the local filesystem?

To save scratch notes and plans to the local filesystem, you can use a skill that persists inline content or stdin into a predictable directory tree. This ensures later workflow turns can reliably reference earlier artifacts.

What is the best way to organize and find skill artifacts like logs and transcripts in one place?

Organizing and finding skill artifacts in one place involves storing files under a consistent directory structure like .skillz/<type>/<slug>. You can then retrieve content by fetching saved files via type and slug or searching titles and bodies.

Can I search across saved plans and scratch notes by keyword to find what was written earlier?

Yes, you can search saved plans and scratch notes by keyword to find what was written earlier. The search functionality scans both slug names and full text bodies, returning results and using exit-code signaling for not-found cases.

How do I prevent path traversal when saving local files with user-defined slugs?

To prevent path traversal when saving local files with user-defined slugs, the system enforces strict slug validation. This keeps artifacts scoped to their intended directory buckets and prevents accidental misuse of the file structure.

Does saving local artifacts require passing content via stdin or can I use inline text?

Saving local artifacts supports both inline content and stdin input methods. When a file is saved, the system prints the resolved path to confirm where the artifact is stored within the directory tree.