@bamdra/bamdra-user-bind 0.1.11 → 0.1.13

package/dist/openclaw.plugin.json

@@ -3,10 +3,13 @@
   "type": "tool",
   "name": "Bamdra User Bind",
   "description": "Identity resolution, user profile binding, and admin profile tools for OpenClaw channels.",
-  "version": "0.1.0",
+  "version": "0.1.13",
   "main": "./index.js",
+  "skills": [
+    "./skills"
+  ],
   "configSchema": {
     "type": "object",
     "additionalProperties": true
   }
-}
+}

package/dist/package.json

@@ -1,12 +1,41 @@
 {
   "name": "@bamdra/bamdra-user-bind",
-  "version": "0.1.0",
-  "private": true,
+  "version": "0.1.13",
+  "description": "Identity resolution, user profile binding, and admin-safe profile tools for OpenClaw channels.",
+  "license": "MIT",
+  "homepage": "https://www.bamdra.com",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/bamdra/bamdra-user-bind.git"
+  },
+  "bugs": {
+    "url": "https://github.com/bamdra/bamdra-user-bind/issues"
+  },
   "type": "commonjs",
   "main": "./index.js",
   "types": "./dist/index.d.ts",
+  "files": [
+    "dist",
+    "skills",
+    "openclaw.plugin.json",
+    "README.md",
+    "LICENSE"
+  ],
+  "keywords": [
+    "openclaw",
+    "openclaw-plugin",
+    "identity",
+    "user-profile",
+    "feishu",
+    "memory"
+  ],
+  "engines": {
+    "node": ">=22"
+  },
   "scripts": {
-    "bundle": "node ../../scripts/run-local-bin.mjs tsup && node ../../scripts/prepare-plugin-dist.mjs bamdra-user-bind"
+    "bundle": "node ../bamdra-openclaw-memory/scripts/run-local-bin.mjs tsup && node -e \"const fs=require('node:fs');const path='./dist/index.js';const text=fs.readFileSync(path,'utf8').replace(/require\\\\(\\\"sqlite\\\"\\\\)/g,'require(\\\"node:sqlite\\\")');fs.writeFileSync(path,text);\" && node ./scripts/prepare-plugin-dist.mjs",
+    "prepublishOnly": "pnpm run bundle",
+    "package:release": "node ./scripts/package-release.mjs"
   },
   "openclaw": {
     "id": "bamdra-user-bind",
@@ -22,8 +51,11 @@
       "default": "./dist/index.js"
     }
   },
+  "publishConfig": {
+    "access": "public"
+  },
   "dependencies": {},
   "devDependencies": {
     "@types/node": "^24.5.2"
   }
-}
+}

package/openclaw.plugin.json

@@ -3,7 +3,7 @@
   "type": "tool",
   "name": "Bamdra User Bind",
   "description": "Identity resolution, user profile binding, and admin profile tools for OpenClaw channels.",
-  "version": "0.1.10",
+  "version": "0.1.13",
   "main": "./dist/index.js",
   "skills": ["./skills"],
   "configSchema": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bamdra/bamdra-user-bind",
-  "version": "0.1.11",
+  "version": "0.1.13",
   "description": "Identity resolution, user profile binding, and admin-safe profile tools for OpenClaw channels.",
   "license": "MIT",
   "homepage": "https://www.bamdra.com",
@@ -33,7 +33,7 @@
     "node": ">=22"
   },
   "scripts": {
-    "bundle": "node ../bamdra-openclaw-memory/scripts/run-local-bin.mjs tsup && node -e \"const fs=require('node:fs');const path='./dist/index.js';const text=fs.readFileSync(path,'utf8').replace(/require\\\\(\\\"sqlite\\\"\\\\)/g,'require(\\\"node:sqlite\\\")');fs.writeFileSync(path,text);\"",
+    "bundle": "node ../bamdra-openclaw-memory/scripts/run-local-bin.mjs tsup && node -e \"const fs=require('node:fs');const path='./dist/index.js';const text=fs.readFileSync(path,'utf8').replace(/require\\\\(\\\"sqlite\\\"\\\\)/g,'require(\\\"node:sqlite\\\")');fs.writeFileSync(path,text);\" && node ./scripts/prepare-plugin-dist.mjs",
     "prepublishOnly": "pnpm run bundle",
     "package:release": "node ./scripts/package-release.mjs"
   },

package/skills/bamdra-user-bind-admin/SKILL.md

@@ -30,7 +30,7 @@ Use the admin tools in natural language:
 ## Good Requests
 
 - “查询 user:u_123 的画像和绑定关系”
-- “把 user:u_123 的称呼改成老板，时区改成 Asia/Shanghai”
+- “把 user:u_123 的称呼改成老板，时区改成 Europe/Berlin”
 - “把 user:u_123 的默认称呼改成丰哥”
 - “合并 user:u_old 到 user:u_new”
 - “列出最近的绑定失败问题”
@@ -42,3 +42,5 @@ Use the admin tools in natural language:
 - if a request is ambiguous, narrow it before making changes
 - remember that every admin action is auditable
 - do not expose unrelated users when answering a narrow admin query
+- do not use admin tools as a shortcut for answering the current user's own profile or address preference
+- if the issue is that the current session cannot resolve the user, repair the binding first, then let the normal self-profile flow continue

package/skills/bamdra-user-bind-profile/SKILL.md

@@ -28,6 +28,7 @@ Keep per-user address preferences in the bound profile instead of `USER.md`. `US
 
 ## Behavior Rules
 
+- before replying, quietly fetch the current bound profile and use it as a soft personalization hint rather than announcing the lookup
 - personalize naturally when the stored profile clearly helps
 - use the stored nickname if the user has not asked for a different form of address in the current turn
 - respect the stored timezone for scheduling, reminders, dates, and time-sensitive explanations
@@ -35,6 +36,90 @@ Keep per-user address preferences in the bound profile instead of `USER.md`. `US
 - if the profile contains a preferred address, treat it as the default greeting and do not duplicate it in workspace-level `USER.md`
 - if the current turn conflicts with the stored profile, follow the current turn
 - do not invent profile traits that are not present
+- if the current open id fails to match a bound user, first try the identity refresh and channel resolution path to recover the real uid before treating the profile as missing
+- remember that one real user may correspond to multiple open ids across apps or accounts; prefer repairing the binding over creating parallel personas
+- if the identity is recovered but the profile is sparse, create only a lightweight default profile and continue naturally
+- when a lightweight default profile is in use, ask at most one or two brief, human questions such as how to address the user or what communication style they prefer
+- phrase onboarding naturally, for example as a first-time acquaintance check, not as a database form or a profile interrogation
+- once the user gives a stable preference like preferred address or collaboration style, update their bound profile immediately instead of leaving it in `USER.md`
+
+## Tool Actions
+
+Use the profile tools as an action loop, not as a passive reference.
+
+1. Before replying, call `bamdra_user_bind_get_my_profile`.
+2. If current identity looks missing or stale, call `bamdra_user_bind_refresh_my_binding` first, then read the profile again.
+3. If the user clearly reveals stable profile information in the current turn, first do a semantic interpretation of what belongs in the user's profile, then call `bamdra_user_bind_update_my_profile` in the same turn.
+4. After a successful update, reply naturally as if you have already absorbed the preference. Do not say that you "might" remember it later.
+
+When the user reveals stable profile information, do not stop at "我记住了" in prose. Actually write it back through the tool.
+
+Do not surface internal profile-write failures in the user-facing reply unless the user explicitly asks about the profile system itself. Avoid lines like "系统画像更新遇到了一点技术问题". If the write path needs repair in the background, keep the reply natural and continue serving the user.
+
+## Semantic Extraction Rule
+
+Do not rely on phrase matching or a tiny list of trigger sentences.
+
+Use model judgment to read the user's natural language and decide whether the message contains stable profile traits that should persist beyond the current turn.
+
+Think in terms of profile slots, not keywords:
+
+- how the user prefers to be addressed
+- how the user prefers answers to be structured
+- tone and communication style
+- role, responsibility, or identity in the collaboration
+- timezone or durable location context
+- durable dislikes, boundaries, or collaboration constraints
+- long-lived private notes that help future cooperation
+
+The same user intent may appear in many surface forms. Treat all of these as equivalent if they carry the same stable meaning:
+
+- direct statements
+- soft suggestions
+- casual side remarks
+- corrections to how you addressed them
+- "by the way" comments
+- complaints about prior reply style
+- self-descriptions embedded inside a larger request
+
+Extract semantically. Do not wait for the user to say exactly "remember this" or "update my profile".
+
+If a message contains both a task request and profile information, do both:
+
+- first update the profile with the stable traits you inferred
+- then continue handling the user's actual task
+
+Field mapping for `bamdra_user_bind_update_my_profile`:
+
+- preferred form of address -> `nickname`
+- communication style or formatting preference -> `preferences`
+- personality or tone preference -> `personality`
+- role or identity in collaboration -> `role`
+- timezone -> `timezone`
+- durable private notes worth remembering -> `notes`
+
+When mapping, summarize the stable meaning instead of copying noisy raw text when helpful.
+
+Examples of semantic normalization:
+
+- "以后别整那么官腔" -> `personality` or `preferences`, not raw transcript dumping
+- "我比较喜欢你先说判断，再展开原因" -> `preferences`
+- "我是这个项目最后拍板的人" -> `role`
+- "别老叫我老师，直接叫我名字就行" -> `nickname` or `notes`, depending on what is clearest
+- "我不喜欢太长铺垫" -> `preferences` or `notes`
+
+Examples:
+
+- "以后叫我阿丰" -> call `bamdra_user_bind_update_my_profile` with `nickname: "阿丰"`
+- "你先给结论，再展开" -> call `bamdra_user_bind_update_my_profile` with `preferences: "偏好先给结论，再展开"`
+- "说话直接一点，但别太冲" -> call `bamdra_user_bind_update_my_profile` with `personality: "偏好直接、克制、不生硬"`
+- "我常驻 Berlin" -> call `bamdra_user_bind_update_my_profile` with `timezone: "Europe/Berlin"`
+- "我是这个项目的负责人" -> call `bamdra_user_bind_update_my_profile` with `role: "项目负责人"`
+
+If one user message contains both service intent and stable profile facts, do both in the same turn:
+
+- first update the profile
+- then continue handling the actual request
 
 ## Privacy Rules
 
@@ -42,6 +127,7 @@ Keep per-user address preferences in the bound profile instead of `USER.md`. `US
 - do not describe the private profile store unless the user asks
 - do not treat profile storage as a global contact directory
 - do not ask for profile data that already exists in the bound profile unless it is stale or clearly insufficient
+- do not force explicit profile talk when the information can stay implicit in the response style
 
 ## Updating Profile Information
 
@@ -50,12 +136,22 @@ When the user clearly provides a stable preference or asks to remember how to wo
 Good examples:
 
 - “以后叫我老板”
-- “我在 Asia/Shanghai 时区”
+- “我在 Europe/Berlin 时区”
 - “我偏好幽默一点，但别太浮夸”
 - “我更喜欢先给结论，再展开”
+- “应该叫我阿丰，不用太正式”
+- “第一次配合的话，你可以先简短一点”
+- “别太像客服，直接一点”
+- “我是这个项目的负责人”
+- “我不喜欢很长的铺垫”
 
 Do not update the profile for transient moods, one-off formatting requests, or unstable short-term details.
 
+Use this stability test:
+
+- if it is likely to still help in later conversations, it probably belongs in the profile
+- if it only matters for this single reply, it probably does not
+
 ## Storage Boundary
 
 Treat profile-style facts as private-by-default.