AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Member Memory Manager

skill-wowyuarm-dsh-agent-team-member-memory-manager · by wowyuarm

Maintain this Member's private memory — what earns a line in the memory.md index, what belongs in a notes/ file instead, how to compact an index past half its budget, and when to demote knowledge that no longer earns a line. Read this skill when the injected memory block shows a maintenance warning, when the index approaches its budget, or before adding or renaming a note.

— No reviews yet
0 installs
0 views
— view→install

Install

$ agentstack add skill-wowyuarm-dsh-agent-team-member-memory-manager

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-wowyuarm-dsh-agent-team-member-memory-manager)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Member Memory Manager? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Member Memory Manager

memory.md is a routing index, not a store, and its budget is real: the injected block states current usage, and past 16 KiB the index is not injected at all — the Member loses its own continuity. Notes are never injected; they are read on demand, so the index must stay small enough to be resident and precise enough to route.

Three tiers

  • T0 memory.md (always injected) — identity and role, durable rules that must bind every step, what is currently in hand, and one routing line per topic cluster. Target well under 8 KiB; treat 16 KiB as the hard ceiling.
  • T1 notes//README.md (read on demand) — one line per note in that cluster. What T0 routes to is the cluster count (3–6), not the note count.
  • T2 notes/.md (read on demand) — one concept per file; update the existing file instead of writing a near-duplicate, and keep evidence, numbers, and commands here rather than in T0.

Screenshots, logs, and generated artifacts belong under notes/assets/ and earn no index line anywhere.

What earns a line

Apply one test before writing: would my future self make a wrong decision without this line? If not, it does not belong in T0. Team facts the ledger already owns, event logs, one-off task detail, credentials, and copies of a note's body never qualify.

Lifecycle

  • Compact as you write. Past roughly half the budget, merge and drop while adding rather than appending; naming a cluster in T1 is cheaper than naming its notes in T0.
  • Demote, do not delete. A rule that stopped binding moves down a tier (T0 to a note, T1 to notes/archive/); archived knowledge stays readable and is never silently lost.
  • Separate rolling from settled. "In hand" is overwritten as work moves; settled knowledge is compacted in place, and that section never accumulates history.

Check after reorganizing

Re-read memory.md once: under budget, one line per cluster, every routing line resolving to a file that exists, and nothing that must bind every step living only in a note. The injected block reports the current size, so a later injection shows whether the rewrite took.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.