@adminforth/agent 1.52.2 → 1.52.4

package/build.log

@@ -63,5 +63,5 @@ custom/speech_recognition_frontend/voiceActivityDetection.ts
 custom/speech_recognition_frontend/types/
 custom/speech_recognition_frontend/types/voice-activity-detection.d.ts
 
-sent 1,682,869 bytes  received 940 bytes  3,367,618.00 bytes/sec
-total size is 1,678,641  speedup is 1.00
+sent 1,682,974 bytes  received 940 bytes  3,367,828.00 bytes/sec
+total size is 1,678,746  speedup is 1.00

package/custom/skills/fetch_data/SKILL.md

@@ -10,7 +10,7 @@ When you only need specific fields, pass `columns` with the exact resource colum
 
 # Instructions
 
-To find specific data record you should use filters. ILIKE filters are preferred when we are unsure the input is clear.You can combine filters with OR if you want to search multiple fields.If user queries one record you should try to fetch up to 5 records and if more then one returned return output them all to user and ask to select one. When you communicate about record with user, show its several most important fields.
+To find specific data record you should use filters. ILIKE filters are preferred when we are unsure the input is clear. Pass raw search text to LIKE and ILIKE filters; never wrap filter values in SQL wildcards such as `%`. You can combine filters with OR if you want to search multiple fields. If user queries one record you should try to fetch up to 5 records and if more then one returned return output them all to user and ask to select one. When you communicate about record with user, show its several most important fields.
 
 Every record summary must be based on one exact row returned by `get_resource_data`.
 

package/dist/custom/skills/fetch_data/SKILL.md

@@ -10,7 +10,7 @@ When you only need specific fields, pass `columns` with the exact resource colum
 
 # Instructions
 
-To find specific data record you should use filters. ILIKE filters are preferred when we are unsure the input is clear.You can combine filters with OR if you want to search multiple fields.If user queries one record you should try to fetch up to 5 records and if more then one returned return output them all to user and ask to select one. When you communicate about record with user, show its several most important fields.
+To find specific data record you should use filters. ILIKE filters are preferred when we are unsure the input is clear. Pass raw search text to LIKE and ILIKE filters; never wrap filter values in SQL wildcards such as `%`. You can combine filters with OR if you want to search multiple fields. If user queries one record you should try to fetch up to 5 records and if more then one returned return output them all to user and ask to select one. When you communicate about record with user, show its several most important fields.
 
 Every record summary must be based on one exact row returned by `get_resource_data`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adminforth/agent",
-  "version": "1.52.2",
+  "version": "1.52.4",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "module",
@@ -25,6 +25,7 @@
   "description": "AI agent plugin for AdminForth with tool-based workflows and persistent chat sessions",
   "devDependencies": {
     "@types/node": "latest",
+    "adminforth": "3.0.1",
     "semantic-release": "^24.2.1",
     "semantic-release-slack-bot": "^4.0.2",
     "typescript": "^5.7.3"
@@ -33,7 +34,6 @@
     "@langchain/core": "^1.1.40",
     "@langchain/langgraph": "^1.2.8",
     "@langchain/langgraph-checkpoint": "^1.0.1",
-    "adminforth": "2.72.0",
     "dayjs": "^1.11.20",
     "langchain": "^1.3.3",
     "multer": "^2.1.1",
@@ -65,5 +65,8 @@
       "name": "next",
       "prerelease": true
     }
-  ]
+  ],
+  "peerDependencies": {
+    "adminforth": "3.0.1"
+  }
 }