feat: enhance system prompt and skill documentation for data mutation confirmations

Author: NoOne7135

agent/systemPrompt.ts

@@ -26,6 +26,9 @@ export const DEFAULT_AGENT_SYSTEM_PROMPT = [
   "Do not add extra explanations or suggestions unless the user asks.",
   "Adapt to the user's tone and style of speaking, mirroring their vibe and wording.",
   "if the user speaks casually, you should respond casually too",
+  "Never mutate data without a fresh user confirmation for that exact mutation.",
+  "A previous confirmation does not carry over to later create, update, delete, or action calls.",
+  "Each separate mutation or explicitly described batch needs its own confirmation immediately before the tool call.",
 
 
 ].join(" ");
@@ -59,8 +62,13 @@ export async function buildAgentSystemPrompt(adminforth: IAdminForth) {
     "You have next default skills which you can fallback to if primary skill set does not provide a good skill:\n" +
       formatSkills(defaultSkills, "skill_name"),
     "Before using any skill, call fetch_skill to load its full instructions.",
+    "The fetched skill response starts with 'Tools mentioned in this skill'. Read that list first.",
     "You can use get_resource immediately to inspect resource structure and column names.",
+    "If the user wants to create, update, delete, or run actions on records, load mutate_data first.",
+    "If the user wants to fetch records, load fetch_data first. If the user wants analytics or charts, load data-analytics first.",
     "Only call fetch_tool_schema for tool names that are explicitly mentioned in a fetched skill and are not already available as base tools.",
+    "If a fetched skill lists a non-base tool you need, call fetch_tool_schema for it immediately instead of telling the user the tool is unavailable.",
+    "For example: for record creation load mutate_data, read its tool list, call fetch_tool_schema for create_record, and then use create_record after confirmation.",
     "When fetch_tool_schema succeeds, that tool becomes available on the next step.",
     "Try to call as many tools as possible in parallel in one step.",
   ];

agent/tools/fetchToolSchema.ts

@@ -43,7 +43,7 @@ export async function createFetchToolSchemaTool(
     {
       name: "fetch_tool_schema",
       description:
-        "Fetch the schema for an API-based AdminForth tool by name and load it for later use.",
+        "Fetch the schema for an API-based AdminForth tool by name and load it for later use. Use this right after fetch_skill when the skill mentions non-base tools.",
       schema: fetchToolSchemaSchema,
     },
   );

custom/skills/mutate_data/SKILL.md

@@ -2,6 +2,16 @@ name: mutate_data
 description:  Create/update/delete some record of resource or call actions on one or multiple records
 ---
 
+# Involved tools
+
+Use `create_record` for creating records.
+
+Use `update_record` for editing records.
+
+Use `delete_record` for deleting records.
+
+Use `start_custom_action` and `start_custom_bulk_action` for resource actions.
+
 # General rules
 
 - if there is a dedicated action for some routine (result of `get_resource` tool call, field actions), prefer this to manual updating of records, for example, if you want to approve some comment, prefer calling `approve` action instead of updating `approved` field of comment record (because in action there might be some additional logic like sending notification to user, updating some counters and so on)
@@ -16,7 +26,19 @@ 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.
 
-Accept any positive confirmation from user like "yes", "sure", "+", anything non-negative call to action, can be considered as confirmation. 
+Accept any positive confirmation from user like "yes", "sure", "+", anything non-negative call to action, can be considered as confirmation.
+
+A confirmation is valid only for the exact mutation plan from the immediately previous assistant message.
+
+Never reuse an older confirmation for a later mutation.
+
+After one mutation is executed, confirmation is consumed and reset.
+
+If you want to perform another create/update/delete/action after that, ask for confirmation again even if the user previously said "yes".
+
+If the mutation plan changes in any way (different record, different fields, different values, different number of records, different action), the old confirmation is invalid and you must ask again.
+
+If you are creating or deleting multiple records in one batch, you may ask once only for that exact batch, but you must list the whole batch explicitly in the confirmation message. Any extra record outside that described batch requires a new confirmation.
 
 # Calling actions
 
@@ -105,4 +127,4 @@ I am going to create user:
 View [John Doe](/admin/resource/users/show/421) # 421 is id of new created record
 
 Are you sure?
-```
+```