agentsclimarketplace

Local file memory

Skill wchen02/cursor-agent-learning/.cursor/skills/local-file-memory

A hands-on project to learn Cursor’s agent customization: rules, skills, subagents, commands, hooks, and AGENTS.md. Everything is set up with examples and docs so you can try things and tweak them.

Install
npx -y skills add wchen02/cursor-agent-learning --skill local-file-memory

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use a Markdown file in the repo as persisted agent memory across chats. Use when the user wants session-spanning context, a decision log, or to resume work without re-pasting history.

SKILL.md

1.7 KB, as published. Nobody here has run it

Local file memory

Teach and apply the local file pattern for agent memory: read before work, update after.

Steps

  1. Resolve path — Default: .cursor/agent-memory/MEMORY.md. If missing, copy the starter from examples/agent-frameworks/local-file-memory-template/MEMORY.md and create the directory.

  2. Read first — Open the memory file and summarize Current focus, Decisions, and Open questions in chat (or use them silently if the user only asked for edits).

  3. Do the task — Follow the user’s request; align with Do not forget and past Decisions.

  4. Update memory — After substantive work, edit the file: refresh Current focus, append dated lines under Decisions, check off or add Open questions, extend Do not forget if new constraints appeared. Optionally add a line under Session log.

  5. Stay safe — Do not store secrets (keys, tokens) in memory files. See local-file-memory.md.

Reference

Gives 0 of the 12 instructions most memory context skills give

Counted across 674 of the 847 authors here whose files we hold, read 2026-08-06

  • inform the user when setup is completein 21 of 674, across 6 files
  • confirm the draft with the user before writingin 21 of 674, across 6 files
  • update the agent skills block in place if it existsin 21 of 674, across 6 files
  • present findings to the userin 20 of 674, across 5 files
  • write the three docs files from seed templatesin 20 of 674, across 5 files
  • ask the user about each decision one at a timein 19 of 674, across 4 files
  • edit CLAUDE.md if it existsin 18 of 674, across 3 files
  • explore current repo statein 18 of 674, across 3 files
  • do not overwrite user edits to surrounding sectionsin 18 of 674, across 3 files
  • back up the original file before overwritingin 16 of 674, across 8 files
  • keep the memory index under 200 linesin 15 of 674
  • Provide actionable steps and verificationin 13 of 674, across 2 files

Said here and by no other author read

  • summarize current focus and decisions
  • align work with saved constraints
  • update memory after substantive work
  • refresh current focus on update
  • append dated lines under decisions
  • check off or add open questions

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.