@agenr/openclaw-plugin 0.11.3 → 0.12.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@agenr/openclaw-plugin",
3
- "version": "0.11.3",
3
+ "version": "0.12.1",
4
4
  "description": "agenr memory plugin for OpenClaw — lightweight plugin-only package without the CLI",
5
5
  "license": "AGPL-3.0",
6
6
  "author": "agenr-ai",
@@ -24,8 +24,8 @@
24
24
  "README.md"
25
25
  ],
26
26
  "dependencies": {
27
- "@libsql/client": "^0.17.0",
28
- "@mariozechner/pi-ai": "^0.55.3",
27
+ "@libsql/client": "^0.17.2",
28
+ "@mariozechner/pi-ai": "^0.61.1",
29
29
  "@sinclair/typebox": "^0.34.48"
30
30
  },
31
31
  "openclaw": {
package/skills/SKILL.md CHANGED
@@ -5,7 +5,27 @@ description: Use when storing new knowledge (decisions, preferences, lessons, to
5
5
 
6
6
  ## agenr_store
7
7
 
8
- Use proactively. Call immediately after any decision, user preference, lesson learned, important event, or fact worth remembering. Do not ask first.
8
+ Use proactively for durable knowledge - decisions, preferences, lessons, and facts that future sessions need to make better decisions.
9
+
10
+ **The future-session test:** Before storing, ask: "If I woke up in a fresh session and recalled this, would it change how I act?" If the answer is just "it tells me something that already happened and is done" - do not store it.
11
+
12
+ **Store:**
13
+ - Architecture decisions and design rationale
14
+ - Workflow constraints and operational rules
15
+ - Lessons learned from problems (recurring bugs, what worked, what did not)
16
+ - User preferences and working-style observations
17
+ - Durable facts about systems, environments, people, projects
18
+ - Important open risks or unresolved hazards
19
+
20
+ **Do not store:**
21
+ - Version or release shipping events ("v1.2.3 shipped") - changelogs are the system of record
22
+ - Issue or PR filing records ("filed #123, #124") - the issue tracker is the system of record
23
+ - Phase plans or release packaging decisions - transient coordination artifacts, stale within a session
24
+ - Progress snapshots ("3 of 5 tasks done") - stale within minutes
25
+ - Prompt file paths or internal build logistics - look-up-able, not memory-worthy
26
+ - Anything whose only value is duplicating files, the issue tracker, or git history
27
+
28
+ Do not ask before storing - but do ask whether future-you needs it.
9
29
 
10
30
  Required: `type`, `content`, `importance`.
11
31
  Optional: `subject` (short label), `tags` (array), `scope` (`private`|`personal`|`public`), `project`, `platform`, `source`.
@@ -21,6 +41,7 @@ Do not store secrets/credentials, temporary state, or verbatim conversation.
21
41
  - **7**: Default. Project facts, decisions, preferences, milestones. No signal fired.
22
42
  - **6**: Routine dev observations (verified X, tests passing). Cap here unless the result is surprising.
23
43
  - **5**: Borderline. Only store if clearly durable beyond today.
44
+ - **Importance is not recency.** Something that just happened is not automatically important. A shipping event is importance 5-6 at best unless it teaches a lesson. A recurring operational hazard is importance 7-8 because it affects future decisions.
24
45
 
25
46
  Entries at 7 are saved silently. Use 8+ only if other active sessions need to know NOW.
26
47