pudap/skills

puda-memory

Maintains project.md as the single source of truth for a project. Use after creating or updating protocols, or after running protocols, to record protocol runs, links, and history with timestamps.

First seen Apr 14, 2026

Installation

$ npx skills add pudap/skills --skill puda-memory

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from pudap/skills · top by installs.

npx skills add pudap/skills

Browse all from pudap/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,843 B
  • docs SUMMARY.md 215 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 78 installs

SKILL.md

Puda Memory

Goal

Maintain project.md as the source of truth for each project: protocol links, and a chronological history so runs are reproducible and auditable.

CRITICAL: Persist all project-related state so runs are reproducible and auditable.

Each project folder has project.md as the single place to record everything about that project for long-term memory. Paths below are relative to the project folder (which contains protocols/).

When to Update

  • After creating a protocol file
  • After updating or deriving a new protocol
  • After every protocol run

What to Record in project.md

  • Protocols: Use explicit markdown links to protocol files under protocols/. In the "Protocols" section, list each as [<protocolid>](protocols/<protocolid>.json) with an optional short description after the link (e.g. [<protocolid>](protocols/<protocolid>.json) — <summary>).
  • History: A chronological log of actions with ISO 8601 timestamps. MUST use a real timestamp—never guess or use a placeholder. Get the timestamp from the relevant file: for "ran" entries use the first line of the log file; for "created"/"updated" entries use the timestamp key in the protocol JSON file. Use explicit markdown links for all file paths. Append one line per action in this form:

- <timestamp> created [<protocolid>](protocols/<protocolid>.json) - <timestamp> updated [<oldprotocolid>](protocols/<oldprotocolid>.json) to [<newprotocolid>](protocols/<newprotocolid>.json) - `<timestamp> ran [<protocolid>](protocols/<protocolid>.json)