chore: import upstream snapshot with attribution

plugin/skills/remember/EXAMPLES.md

@@ -0,0 +1,67 @@
+# remember worked examples
+
+## 1. Saving a decision
+
+User: "Remember that we decided to drop Redis and use the iii-engine state store for session caching."
+
+Invocation:
+
+```json
+memory_save {
+  "content": "We decided to drop Redis and use the iii-engine state store for session caching to remove a moving part.",
+  "concepts": "session-caching, iii-state-store, dropped-redis",
+  "files": ""
+}
+```
+
+Response:
+
+```json
+{ "id": "7f3a9c21", "concepts": ["session-caching", "iii-state-store", "dropped-redis"], "saved": true }
+```
+
+Present:
+
+> Saved. Tagged it `session-caching`, `iii-state-store`, `dropped-redis`, so a
+> later recall on caching or Redis will surface this decision.
+
+## 2. Saving a code-specific gotcha
+
+User: "Save this: the rate limiter in middleware/limit.ts counts per-IP, not per-user, so logged-in users on shared IPs collide."
+
+Invocation:
+
+```json
+memory_save {
+  "content": "The rate limiter in middleware/limit.ts counts per-IP, not per-user, so logged-in users on shared IPs collide.",
+  "concepts": "rate-limiter, per-ip-bug, shared-ip-collision",
+  "files": "src/middleware/limit.ts"
+}
+```
+
+Response:
+
+```json
+{ "id": "b21d004e", "concepts": ["rate-limiter", "per-ip-bug", "shared-ip-collision"], "saved": true }
+```
+
+Present:
+
+> Saved memory `b21d004e` referencing `src/middleware/limit.ts`. Concepts:
+> `rate-limiter`, `per-ip-bug`, `shared-ip-collision`.
+
+## 3. Vague request, no files
+
+User: "Remember this for later."
+
+Ask once for the substance, then save:
+
+```json
+memory_save {
+  "content": "Staging deploys must run the migration job before the app rollout, never after.",
+  "concepts": "staging-deploy, migration-ordering, rollout-sequence",
+  "files": ""
+}
+```
+
+Present the confirmation with the concepts echoed back.

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.