padz-for-agents

Save and retrieve agent notes and tasks in .padz/ stores with JSON output.

Updated May 1, 2026
One-click install
npx skills add https://github.com/arthur-debert/release --skill padz-for-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: padz-for-agents
Source: https://github.com/arthur-debert/release/tree/main/skills/padz-for-agents
Command: npx skills add https://github.com/arthur-debert/release --skill padz-for-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

padz-for-agents helps agents persist important notes, decisions, and task progress across turns and future sessions without losing context or relying on ephemeral chat messages.

Core Features & Use Cases

  • Capture memory as pads: Record structured notes and tasks into a project .padz/ store (or global store) so they can be listed and retrieved later.
  • Agent-safe retrieval: Read pads with full structured JSON output for reliable downstream reasoning and rendering.
  • Stable cross-session references: Use UUIDs to ensure links and references remain correct even when display indexes shift.
  • Handoff between agents/sessions: Export selected pads into a tar.gz archive and import them elsewhere with metadata preserved.

Quick Start

Tell the agent to save what you just said as a note in this repo by running: padz create "Title for what should be remembered" --no-editor.

Frequently Asked Questions about padz-for-agents

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

FAQPage Schema
How do I persist agent memory and notes across sessions?

Agent session continuity works by saving notes and tasks as structured pads in a project .padz/ directory or global store. Reads use JSON output for reliable downstream reasoning, ensuring context survives across turns and future sessions.

What is the best way to hand off notes between different agents?

Handing off notes between agents is done by exporting selected pads into a tar.gz archive and importing them elsewhere with metadata preserved. This ensures the receiving agent gets the full structured context of the previous session.

How do I save a note without opening an editor from the command line?

To save a note without an editor, run the padz create command with the --no-editor flag. This allows agents to programmatically capture memory and record structured notes without requiring interactive input.

Why should I use UUIDs instead of display indexes for referencing notes?

You should use UUIDs instead of display indexes because UUIDs ensure stable cross-session references. Display indexes can shift between turns, but UUIDs keep links and references correct even when the list order changes.

Can I retrieve agent tasks in JSON format for downstream processing?

Yes, you can retrieve agent tasks and notes with full structured JSON output by using the --output json flag. This provides reliable structured data for downstream reasoning and rendering in automated workflows.

What are the limitations of relying on chat messages for agent memory?

Relying on ephemeral chat messages for agent memory risks losing context and task progress across turns. Storing structured notes in a persistent .padz/ directory solves this by keeping memory compaction and handoff data safe.