ziiagentmemory 0.1.0

package/plugin/skills/remember/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: remember
+description: Save an insight, decision, or learning to agentmemory's long-term storage with searchable concept tags. Use when the user says "remember this", "save this", "note that", "don't forget", or wants to preserve knowledge for future sessions.
+argument-hint: "[what to remember]"
+user-invocable: true
+---
+
+The user wants to save this to long-term memory: $ARGUMENTS
+
+## Quick start
+
+```json
+memory_save {
+  "content": "We rotate JWT refresh tokens on every use; the old token is revoked server-side in auth/refresh.ts.",
+  "concepts": "jwt-refresh-rotation, token-revocation, auth-flow",
+  "files": "src/auth/refresh.ts"
+}
+```
+
+Expected output:
+
+```text
+Saved memory abc12345 with 3 concepts: jwt-refresh-rotation, token-revocation, auth-flow.
+```
+
+## Why
+
+A memory is only as useful as the terms that retrieve it. Tag with specific
+concepts so a future `recall` finds it, and preserve the user's own phrasing.
+
+## Workflow
+
+1. Pull the core insight, decision, or fact out of `$ARGUMENTS`.
+2. Extract 2-5 lowercased concept phrases. Prefer specific over generic
+   (`jwt-refresh-rotation` beats `auth`).
+3. Extract referenced file paths (absolute or repo-relative). Empty if none.
+4. Call `memory_save` with `content`, `concepts` (comma-separated string), and
+   `files` (comma-separated string).
+5. Confirm the save and echo the concepts so the user knows the retrieval terms.
+
+## Anti-patterns
+
+WRONG: `concepts: "stuff, code, notes"` (generic tags nothing can find later).
+
+RIGHT: `concepts: "jwt-refresh-rotation, token-revocation"` (specific, retrievable).
+
+## Checklist
+
+- Content preserves the user's phrasing, not a paraphrase.
+- Concepts are specific, lowercased, 2-5 items.
+- File paths are real references, not guesses.
+- Confirmation echoes the exact concepts tagged.
+
+## See also
+
+- `recall`: retrieve what you save here (the pair to this skill).
+- `forget`: remove a memory you saved by mistake.
+
+## Troubleshooting
+
+See ../_shared/TROUBLESHOOTING.md if `memory_save` is not available.

package/plugin/skills/session-history/EXAMPLES.md

@@ -0,0 +1,59 @@
+# session-history worked examples
+
+## 1. Standard timeline
+
+User: "Show me the session history."
+
+Invocation:
+
+```json
+memory_sessions { "limit": 20 }
+```
+
+Response:
+
+```json
+{
+  "sessions": [
+    { "id": "7f3a9c21", "project": "app", "startedAt": "2026-06-07T09:00:00Z",
+      "status": "completed", "observationCount": 14,
+      "summary": "Reworked refresh rotation",
+      "highlights": [ { "type": "decision", "title": "Rotate refresh tokens on every use" } ] },
+    { "id": "b21d004e", "project": "app", "startedAt": "2026-06-05T14:00:00Z",
+      "status": "completed", "observationCount": 9,
+      "highlights": [ { "type": "code", "title": "limit.ts counts per-IP" } ] }
+  ]
+}
+```
+
+Present:
+
+> - `7f3a9c2` app, 2026-06-07 09:00, completed, 14 obs
+>   - decision: Rotate refresh tokens on every use (summary: Reworked refresh rotation)
+> - `b21d004` app, 2026-06-05 14:00, completed, 9 obs
+>   - code: limit.ts counts per-IP
+
+## 2. Session with no observations
+
+If a returned session has `observationCount: 0`, list it but say so:
+
+> - `c98f110` app, 2026-06-04 11:00, abandoned, 0 obs (no recorded work)
+
+## 3. Empty history
+
+User: "What did we do last time?"
+
+```json
+memory_sessions { "limit": 20 }
+```
+
+Response:
+
+```json
+{ "sessions": [] }
+```
+
+Present:
+
+> No recorded sessions yet for this project. Once you work with memory capture
+> on, they will show here. Use `remember` to save a note now.

package/plugin/skills/session-history/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: session-history
+description: Show what happened in recent past sessions on this project as a clean timeline. Use when the user asks "what did we do last time", "session history", "past sessions", or wants an overview of previous work.
+user-invocable: true
+---
+
+The user wants an overview of recent sessions on this project.
+
+## Quick start
+
+```json
+memory_sessions { "limit": 20 }
+```
+
+Expected output:
+
+```text
+7f3a9c2 · app · 2026-06-07 09:00 · completed · 14 obs
+  - decision: Rotate refresh tokens on every use
+b21d004 · app · 2026-06-05 14:00 · completed · 9 obs
+  - code: limit.ts counts per-IP
+```
+
+## Why
+
+Only show sessions and observations the tool returned. An empty history is a
+real answer, never a cue to invent past work.
+
+## Workflow
+
+1. Call `memory_sessions` with `limit: 20` for a meaningful window.
+2. Present in reverse chronological order: session id (first 8), project, start
+   time, status.
+3. For sessions with observations, show the key highlights (type plus title).
+4. Note the total observation count per session.
+5. When a session summary exists, surface its title and the key decisions.
+
+## Anti-patterns
+
+WRONG: the tool returns two sessions, you describe "several sessions of steady
+progress" and add ones you remember from the conversation.
+
+RIGHT: show exactly the two sessions returned, each with its real id, status, and
+observation count.
+
+## Checklist
+
+- Every session shown came from the tool response.
+- Order is reverse-chronological.
+- Per-session observation counts match the response.
+- No session or highlight was invented or merged.
+
+## See also
+
+- `recap`: same data grouped by date with highlights.
+- `handoff`: jump straight into the most recent session.
+- `recall`: search across all sessions by topic.
+
+## Troubleshooting
+
+See ../_shared/TROUBLESHOOTING.md if `memory_sessions` is not available.

package/plugin/skills/write-agentmemory-skill/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: write-agentmemory-skill
+description: The house format and rules for writing or updating an agentmemory skill. Use when adding a new skill, restructuring an existing one, or reviewing a skill contribution for consistency.
+user-invocable: false
+---
+
+agentmemory skills follow one tiered format so they stay skimmable, accurate, and current. Match it exactly.
+
+## Directory layout
+
+```text
+plugin/skills/<name>/
+  SKILL.md      (required, under 100 lines)
+  REFERENCE.md  (optional, dense facts; auto-generate data tables)
+  EXAMPLES.md   (optional, worked transcripts)
+```
+
+## SKILL.md rules
+
+- Frontmatter: `name`, `description`, optional `argument-hint`, and `user-invocable`. Set `user-invocable: true` only for skills the user runs as a slash command; reference and knowledge skills are `false`.
+- Description is two sentences and the only thing the agent sees when deciding to load the skill. Sentence one states the capability. Sentence two starts "Use when" and lists concrete triggers. Keep it distinct from sibling skills, under 1024 chars, third person.
+- Body order: Quick start (one concrete example), Why (the governing principle), Workflow (numbered steps with decision gates), Anti-patterns (a WRONG vs RIGHT callout for the top mistake), Checklist, See also (cross-link siblings), Reference or Troubleshooting pointer.
+- Stay under 100 lines. Move dense facts to REFERENCE.md and examples to EXAMPLES.md.
+- Cross-references link one level deep only. Shared recovery steps live in `../_shared/TROUBLESHOOTING.md`, never inlined.
+
+## Keep it current
+
+Facts that exist in source (tool names and parameters, REST endpoints, env vars, connect adapters, hook events) are generated, never hand-typed. Edit the source, then run `npm run skills:gen`. CI runs `npm run skills:check` and fails on drift, so generated tables cannot fall behind the code.
+
+## Style
+
+No external or competitor product names. No emojis. No em-dashes. No filler. State the thing and stop.
+
+## Checklist
+
+- Description has a "Use when" sentence with real triggers.
+- SKILL.md is under 100 lines.
+- No time-sensitive claims and no duplicated troubleshooting block.
+- Concrete example present; generated facts come from the generator.
+- Cross-links resolve and go one level deep.