@adminforth/agent 1.18.6 → 1.19.0

package/build.log

@@ -32,5 +32,5 @@ custom/skills/fetch_data/SKILL.md
 custom/skills/mutate_data/
 custom/skills/mutate_data/SKILL.md
 
-sent 187,526 bytes  received 451 bytes  125,318.00 bytes/sec
-total size is 185,674  speedup is 0.99
+sent 188,483 bytes  received 451 bytes  377,868.00 bytes/sec
+total size is 186,631  speedup is 0.99

package/custom/skills/fetch_data/SKILL.md

@@ -10,6 +10,18 @@ You can use tool `get_resource_data` it returns one or more records and is capab
 
 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.
 
+Every record summary must be based on one exact row returned by `get_resource_data`.
+
+Never combine model/title/name, `_label`, primary key, link, or any field values from different rows.
+
+Never combine fields from different resources in one candidate.
+
+If results come from multiple resources, present them as separate groups with the resource label or resourceId.
+
+If several rows look similar, do not guess which one is "the same" record. Show them separately and ask user to choose.
+
 For long texts show only several first words and add "..." at the end (only if user did not request this field specifically).
 
 Also when you communicate with user about record, add related link to this record. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
+
+Before sending the link, verify that the `resourceId`, `{primary key}`, `_label`, and shown fields come from the same exact returned row.

package/custom/skills/mutate_data/SKILL.md

@@ -20,9 +20,13 @@ Use `start_custom_action` and `start_custom_bulk_action` for resource actions.
 
 Before performing any state mutation including action calls edit/delete please fetch record which is going to be edited/deleted and show user record in format field → value (show several most important fields which can help user to understand what exactly record he is going to edit or delete). 
 
+Every confirmation must describe one exact fetched row. Never combine `_label`, primary key, link, or field values from different rows or different resources in one confirmation.
+
 For field values with long texts show only several first words and add "..." at the end.
 Also please add related link to record with will be changed. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
 
+Before sending the confirmation, verify that the `resourceId`, `{primary key}`, `_label`, and all shown fields come from the same exact fetched row.
+
 And in the same message ask user for final confirmation.
 
 When creating new record, show user all data which you gona create and in same message ask for confirmation.

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

@@ -10,6 +10,18 @@ You can use tool `get_resource_data` it returns one or more records and is capab
 
 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.
 
+Every record summary must be based on one exact row returned by `get_resource_data`.
+
+Never combine model/title/name, `_label`, primary key, link, or any field values from different rows.
+
+Never combine fields from different resources in one candidate.
+
+If results come from multiple resources, present them as separate groups with the resource label or resourceId.
+
+If several rows look similar, do not guess which one is "the same" record. Show them separately and ask user to choose.
+
 For long texts show only several first words and add "..." at the end (only if user did not request this field specifically).
 
 Also when you communicate with user about record, add related link to this record. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
+
+Before sending the link, verify that the `resourceId`, `{primary key}`, `_label`, and shown fields come from the same exact returned row.

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

@@ -20,9 +20,13 @@ Use `start_custom_action` and `start_custom_bulk_action` for resource actions.
 
 Before performing any state mutation including action calls edit/delete please fetch record which is going to be edited/deleted and show user record in format field → value (show several most important fields which can help user to understand what exactly record he is going to edit or delete). 
 
+Every confirmation must describe one exact fetched row. Never combine `_label`, primary key, link, or field values from different rows or different resources in one confirmation.
+
 For field values with long texts show only several first words and add "..." at the end.
 Also please add related link to record with will be changed. Build it as `{ADMIN_BASE_PATH}resource/{resourceId}/show/{primary key}`. Use _label from `get_resource_data` as anchor text for link (use markdown link). Links should always be relative paths and must start with `ADMIN_BASE_PATH`. Do not add an extra slash after `ADMIN_BASE_PATH`.
 
+Before sending the confirmation, verify that the `resourceId`, `{primary key}`, `_label`, and all shown fields come from the same exact fetched row.
+
 And in the same message ask user for final confirmation.
 
 When creating new record, show user all data which you gona create and in same message ask for confirmation.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@adminforth/agent",
-  "version": "1.18.6",
+  "version": "1.19.0",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
   "type": "module",