SkillCurated by metahubEval warningsprompts

agent-memory-curator

Name: agent-memory-curator
Author: oxbshw

Use after a session to promote useful episodic notes from logs/episodic/ into distilled, dated entries in MEMORY.md and memory/semantic/.

pinned to #7f8ee3cupdated 3 months ago

7/11Verified publisherCurated by MetaHubActively maintainedLicensedDocumentedStructuredClean repo

Ask your AI client: “install skills/agent-memory-curator”.

Requires the metahub MCP server installed in your client. Set up MCP.

mh install skills/agent-memory-curator

metahub onboarded this repo on the author's behalf.

If you own github.com/oxbshw/LLM-Agents-Ecosystem-Handbook on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.

Claim this repo

Stars

533

Last commit

3 months ago

7f8ee3c

Latest release

published

3 months ago

#ai
#ai-agent
#ai-agents
#fine-tuning
#finetuning-llms
#freamework
#llm
#llmops
#local-development
#mcp-server
#memory
#rag
#rag-chatbot
#voice-agent

Evaluation report

WarningsView full report

Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.7f8ee3c· 3 months ago

Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.

Documentation

4 passed1 warning

README has usage / example sectionswarn
README has no Usage / Example / Quick start / Installation heading at any level
Add a `# Usage`, `## Quick start`, or similar section so end users can copy/paste a working invocation. Code blocks alone work too if there are several.
Description quality
19 words · 137 chars — "Use after a session to promote useful episodic notes from logs/episodic/ into di…"
README is present and substantial
19,199 chars · 20 sections · 2 code blocks
Tags / topics declared
14 total — ai, ai-agent, ai-agents, fine-tuning, finetuning-llms, freamework (+8)
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking

Release history

releasecurrent7f8ee3cwarn3 months ago

View on GitHub

When to use

End of a working session
After resolving an incident worth remembering
When MEMORY.md has grown stale or contradictory

When NOT to use

During a session (don't write memory mid-flight from low-confidence signals)
For raw transcripts (those stay in logs/)

Inputs

Name	Type	Required	Notes
`since`	date	no	default: last curation time
`categories`	list	no	restrict to e.g. `[user, project, decision]`

Workflow

Read new episodic logs in logs/episodic/ since since
Distill each notable event into a one-line dated entry
Categorize into: user / project / decision / feedback / open question
Reconcile: if a new entry contradicts an existing one, update the existing one rather than appending; move the old fact to "Outdated"
Apply rules from references/memory-distillation-rules.md
Write to MEMORY.md (index) and memory/semantic/<topic>.md (details)
Verify no PII / secrets leaked into memory
Report summary of additions / updates / deletions

References

references/memory-distillation-rules.md

Success criteria

Every new entry is dated
No duplicate entries (search before adding)
No PII / secret values
Outdated entries moved, not deleted in-place

Failure modes

Conflicting evidence → mark as "Open question" rather than guessing
Source untrusted (e.g., from MCP/web fetch) → require human confirm before promotion