@dhfpub/clawpool-admin 0.2.1 → 0.2.2

package/dist/index.js

@@ -295,11 +295,11 @@ function buildGroupDetailReadRequest(params) {
   };
 }
 function buildContactSearchRequest(params) {
-  const keyword = readRequiredStringParam(params, "keyword");
+  const id = readRequiredStringParam(params, "id");
   const limit = readOptionalInt(params, "limit");
   const offset = readOptionalInt(params, "offset");
   const query = {
-    keyword
+    id
   };
   if (limit != null) {
     query.limit = String(limit);
@@ -315,11 +315,11 @@ function buildContactSearchRequest(params) {
   };
 }
 function buildSessionSearchRequest(params) {
-  const keyword = readRequiredStringParam(params, "keyword");
+  const id = readRequiredStringParam(params, "id");
   const limit = readOptionalInt(params, "limit");
   const offset = readOptionalInt(params, "offset");
   const query = {
-    keyword
+    id
   };
   if (limit != null) {
     query.limit = String(limit);
@@ -1037,11 +1037,11 @@ var ClawpoolQueryToolSchema = {
       properties: {
         action: { const: "contact_search" },
         accountId: { type: "string", minLength: 1 },
-        keyword: { type: "string", minLength: 1 },
+        id: { type: "string", pattern: "^[0-9]+$" },
         limit: { type: "integer", minimum: 1 },
         offset: { type: "integer", minimum: 0 }
       },
-      required: ["action", "keyword"]
+      required: ["action", "id"]
     },
     {
       type: "object",
@@ -1049,11 +1049,11 @@ var ClawpoolQueryToolSchema = {
       properties: {
         action: { const: "session_search" },
         accountId: { type: "string", minLength: 1 },
-        keyword: { type: "string", minLength: 1 },
+        id: { type: "string", minLength: 1 },
         limit: { type: "integer", minimum: 1 },
         offset: { type: "integer", minimum: 0 }
       },
-      required: ["action", "keyword"]
+      required: ["action", "id"]
     },
     {
       type: "object",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dhfpub/clawpool-admin",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "OpenClaw admin tools plugin for ClawPool",
   "type": "module",
   "main": "./dist/index.js",

package/skills/clawpool-query/SKILL.md

@@ -28,20 +28,54 @@ For Clawpool query actions, always call:
 Rules:
 
 1. Pass query parameters with their exact typed field names.
-2. Use `keyword` for search actions.
+2. Use `id` for `contact_search` and `session_search`.
 3. Use `sessionId`, `beforeId`, and `limit` explicitly for message history.
 4. Never invent a `sessionId`. Resolve it from context, from a previous tool result, or ask the user.
 5. Keep one tool call per action for audit clarity.
 
+## Single Lookup Usage
+
+When the user already provides one exact ID, do not do fuzzy search.  
+Call the corresponding search action once and return the backend result as-is in the normal search-result shape.
+
+1. Single contact lookup:
+   use `action: "contact_search"` and pass `id`
+2. Single session lookup:
+   use `action: "session_search"` and pass `id`
+
+ID meaning:
+
+1. `contact_search.id`:
+   contact or Agent numeric ID, for example `1002` or `9992`
+2. `session_search.id`:
+   exact session ID string, for example `task_room_9083`
+
+Examples:
+
+```json
+{
+  "action": "contact_search",
+  "id": "1002"
+}
+```
+
+```json
+{
+  "action": "session_search",
+  "id": "task_room_9083"
+}
+```
+
 ## Action Contracts
 
 ### contact_search
 
 Purpose: search the owner's Clawpool contact directory.
+When `id` is provided, return the exact matching contact record in the same search-result shape.
 
 Required input:
 
-1. `keyword` (non-empty string)
+1. `id` (contact ID, numeric string)
 
 Optional input:
 
@@ -50,16 +84,18 @@ Optional input:
 
 Guardrails:
 
-1. Use this when the user is trying to find a person or active agent by display name, remark, nickname, username, or agent name.
+1. Use this when the target contact ID is already known and you need the exact contact entry.
 2. Do not jump directly to session history from a vague contact hint; resolve the contact or session first.
+3. `id` must be the current contact's numeric ID, not username, nickname, remark name, or session ID.
 
 ### session_search
 
 Purpose: search the owner's visible sessions by final display title.
+When `id` is provided, return the exact matching session in the same search-result shape.
 
 Required input:
 
-1. `keyword` (non-empty string)
+1. `id` (session ID)
 
 Optional input:
 
@@ -68,8 +104,9 @@ Optional input:
 
 Guardrails:
 
-1. Use this when the user describes a conversation by session title, group name, or known list title.
+1. Use this when the target session ID is already known and you need the exact session entry.
 2. If multiple sessions match, present the candidates and let the user choose before reading history.
+3. `id` must be the exact current `session_id`, not group name, title text, or contact ID.
 
 ### message_history