agentsclimarketplace

Team memory maintenance

Skill meharajM/context-machine/plugins/team-project-memory/skills/team-memory-maintenance

Token-efficient shared project memory skills for developers and AI coding agents.

Install
npx -y skills add meharajM/context-machine --skill team-memory-maintenance

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

One thing to look at

  • 0 stars0 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

Initialize or maintain a git-backed shared project-memory store, including policy, layout, deduplication, contradictions, staleness, retention, and conflict-safe publishing.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.5 KB, 267 tokens by cl100k_base, as published. Nobody here has run it

Team Memory Maintenance

Use for setup or cleanup, not normal debugging.

Default Layout

.agents/project-memory/
├── policy.md
├── entries/<topic>/<entry-id>.md
├── drafts/
└── archive/

Use one learning per file. Do not make every agent rewrite a shared index.

Policy Minimum

Define:

  • memory location and repository scope;
  • review mode: draft-only, PR allowed, or explicitly controlled auto-publish;
  • permitted data classification;
  • owners/reviewers;
  • retention and archive rules;
  • branch and conflict behavior.

Without a policy, use draft-only.

Maintenance

  • Find duplicates by normalized signature plus overlapping scope; merge evidence instead of duplicating.
  • Preserve conflicting findings separately; add contradicts links and narrow scope.
  • Use supersedes for a better replacement; mark the old entry stale.
  • Archive low-value stale entries; search archive only as a last resort.
  • Never move private-repo knowledge into a public or broader memory store without approval.
  • Prefer agent-specific branches and reviewable PRs; never auto-merge unless separately authorized.

Use $team-memory-capture for entry format and $team-memory-search to test retrieval after maintenance.

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.