agentleFS
michelgroletmichelgrolet/people-memory-mcp/skills/upgrade-people-memory/SKILL.md

upgrade-people-memory

Skill1 starsChanged 3 months agoMITView on GitHub

Upgrade an installed People Memory plugin, MCP package, PostgreSQL/Supabase schema, optional API, web UI, and bundled skills; inspect release notes, back up data, apply ordered migrations, refresh uvx or local installs, preserve config and credentials, restart agents, and verify reads and writes. Use when the user says upgrade, update, migrate, install the latest release, schema migration, refresh the plugin, or repair a version mismatch.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the database recoverable and configuration private.

    line 8
  2. Very specific:

    Call graph_status and record counts.

    line 12
  3. Distinctive:

    Read release notes from the current version through the target version.

    line 14
  4. Very specific:

    Create a timestamped pg_dump in a private location.

    line 19
  5. Distinctive:

    Update plugin skills and MCP config without overwriting the user's environment file.

    line 28
  6. Distinctive:

    Start a new agent session so MCP and skill changes load.

    line 30
  7. Very specific:

    Call graph_status and compare counts.

    line 34
  8. Distinctive:

    Read a known synthetic or user-approved test record.

    line 35
  9. Distinctive:

    Create, retrieve, update, and archive-delete a synthetic record.

    line 36
  10. Distinctive:

    Verify login, search, edit, and graph rendering in the UI.

    line 37
  11. Distinctive:

    Remove the synthetic record and archive.

    line 38
  12. Distinctive:

    If a check fails, stop writes, preserve logs without contact data, and offer the tested restore path.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Upgrade People Memory

Keep the database recoverable and configuration private.

Preflight

  1. Call graph_status and record counts.
  2. Identify the installed package, plugin, schema migration level, and UI version.
  3. Read release notes from the current version through the target version.
  4. Flag breaking changes, new connector permissions, or required user choices before mutation.

Back up

Create a timestamped pg_dump in a private location. Verify the file is non-empty and record the restore command. Do not put the backup in Git or an agent artifact store.

Upgrade

  1. Pull or install the target release.
  2. Apply pending Supabase migrations in order. Never run db reset against a linked production project.
  3. Refresh the uvx package cache or local virtual environment.
  4. Update plugin skills and MCP config without overwriting the user's environment file.
  5. Rebuild or redeploy the static UI when its files changed.
  6. Start a new agent session so MCP and skill changes load.

Verify

  1. Call graph_status and compare counts.
  2. Read a known synthetic or user-approved test record.
  3. Create, retrieve, update, and archive-delete a synthetic record.
  4. Verify login, search, edit, and graph rendering in the UI.
  5. Remove the synthetic record and archive.

If a check fails, stop writes, preserve logs without contact data, and offer the tested restore path. Finish with old/new versions, migrations applied, verification results, and any manual login still needed. Do not print secrets or database URLs.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.