Agent memory
Skill kimtth/agent-skill-100-lines-or-less/skills/agent-memory
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill agent-memoryAssembled 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.
- 2 stars2 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 when: persist and recall context across coding sessions so the agent stops re-learning the same stack, bugs, and decisions.
The file declares its own license as Apache-2.0. 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.6 KB, as published. Nobody here has run it
Goal: give the agent searchable long-term memory — capture what happened, compress it to facts, and inject the right context into the next session.
Use for:
- avoiding re-explaining architecture, preferences, and prior decisions each session
- recalling why a choice was made (e.g. jose over jsonwebtoken for Edge compatibility)
- handing off context between agents or teammates
Pipeline:
- Capture observations from tool use; strip secrets and API keys before storing.
- Compress raw observations into structured facts, concepts, and a short narrative.
- Consolidate across four tiers: working (raw) -> episodic (session summaries) -> semantic (facts) -> procedural (workflows).
- Index for hybrid search: BM25 keywords + vector similarity + knowledge-graph traversal, fused with reciprocal rank fusion.
- On session start, load the project profile and inject top results under a token budget.
Lifecycle:
- Memories decay over time; frequently accessed ones strengthen, stale ones auto-evict.
- Detect and resolve contradictions; trace any memory back to its source observation.
Operations:
- remember (save) | recall / smart-search | session-history | handoff | forget
Rules:
- Inject a bounded budget (~2k tokens), not the whole store — keep context lean.
- Keep capture passive and privacy-filtered; never persist credentials.
- Memory augments reading current files; it does not replace verifying them.