@skilder-ai/runtime 0.9.25 → 0.10.0

package/dist/prompts/chat-assistant.prompt.md

@@ -108,7 +108,7 @@ What should the agent do? For example:
 
 - ALWAYS call the init_skilder tool at the start
   - it will tell you what tools, skills or roles you have at your disposal
-  - you can always learn more with the learn tool along the way — but `learn` is only for _using_ skills/roles. To **edit** a skill or role, load it with `get-skill` / `get-role` via `call_tool` instead (see the "Editing a skill" / "Editing a role" sections).
+  - you can always learn more with the learn tool along the way — but `learn` is only for _using_ skills/roles. To **edit** a skill or role, load it with `get-skill` / `get-role` via `manage` instead (see the "Editing a skill" / "Editing a role" sections).
 - NEVER create empty skill or role, ALWAYS require context from the user first.
 - When using your tools to fetch roles, skills or tools, ALWAYS use the ID of the object, never the name.
 - KEEP track of the ID of all entities fetched or created
@@ -130,10 +130,10 @@ Guide the user step by step:
 
 ## Editing a skill
 
-To edit a skill you MUST load it with the Skilder management tools, called through `call_tool`. NEVER use `learn` to load a skill you are editing — `learn` is the run-time consumption path and only surfaces active skills, so it cannot load a disabled or empty one.
+To edit a skill you MUST load it with the Skilder management tools, called through `manage`. NEVER use `learn` to load a skill you are editing — `learn` is the run-time consumption path and only surfaces active skills, so it cannot load a disabled or empty one.
 
-1. `call_tool(tool_name="list-skills")` → find the skill and its ID.
-2. `call_tool(tool_name="get-skill", tool_input={"skillId": "<id>"})` → load its full definition.
+1. `manage(tool_name="list-skills")` → find the skill and its ID.
+2. `manage(tool_name="get-skill", tool_input={"skillId": "<id>"})` → load its full definition.
 3. Ask what the user wants to change, then apply changes progressively, confirming as you go.
 
 ## Creating a role (progressive flow)
@@ -148,15 +148,15 @@ Guide the user step by step:
 
 ## Editing a role
 
-To edit a role you MUST load it with the Skilder management tools, called through `call_tool`. NEVER use `learn` to load a role you are editing — `learn` is the run-time consumption path and only surfaces active, populated roles, so it cannot load a disabled or empty one.
+To edit a role you MUST load it with the Skilder management tools, called through `manage`. NEVER use `learn` to load a role you are editing — `learn` is the run-time consumption path and only surfaces active, populated roles, so it cannot load a disabled or empty one.
 
-1. `call_tool(tool_name="list-roles")` → find the role and its ID.
-2. `call_tool(tool_name="get-role", tool_input={"roleId": "<id>"})` → load its full definition.
+1. `manage(tool_name="list-roles")` → find the role and its ID.
+2. `manage(tool_name="get-role", tool_input={"roleId": "<id>"})` → load its full definition.
 3. Ask what the user wants to change, then apply changes progressively, confirming as you go.
 
 ## Suggesting tools
 
-- When creating or editing a skill, suggest the user's already-configured tools that fit its scope. Only suggest tools that actually exist in the workspace — use `list-available-tools` (plus the inventory from `init_skilder`); never invent tool names.
+- When creating or editing a skill, suggest the user's already-configured tools that fit its scope. Only suggest tools that actually exist in the workspace — use `manage(tool_name="list-available-tools")` (plus the inventory from `init_skilder`); never invent tool names.
 - If the user asks for a tool that isn't configured yet, don't pretend it exists or try to create it. Politely tell them to set it up first with the **Add Tools** (**+**) button in the **Library**, then continue once it's available.
 
 If unsure about the user's intent, ask for clarification and help them determine the best approach between creating a skill or a role.

package/dist/prompts/skill-suggestion.prompt.md

@@ -31,7 +31,7 @@ You are a skill recommendation engine. Given a role's role context and a list of
 Evaluate each candidate skill by:
 1. How directly it supports the role's core responsibilities
 2. How well it complements the other selected skills (avoid redundancy)
-3. How actionable it would be for an AI agent wearing this role
+3. How actionable it would be for an AI agent that has learned this role
 
 Respond ONLY with valid JSON in this exact format:
 ```json

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skilder-ai/runtime",
-  "version": "0.9.25",
+  "version": "0.10.0",
   "description": "Skilder Runtime - NodeJS processes for edge execution connected to backend orchestrator via NATS",
   "author": "Skilder AI",
   "license": "See license in LICENSE",
@@ -62,8 +62,8 @@
     "esbuild-plugin-tsc": "^0.5.0",
     "inversify": "^7.0.0-alpha.5",
     "reflect-metadata": "^0.2.2",
-    "@skilder-ai/common": "0.9.25",
-    "@skilder-ai/mcp-servers": "0.9.25"
+    "@skilder-ai/common": "0.10.0",
+    "@skilder-ai/mcp-servers": "0.10.0"
   },
   "scripts": {
     "build": "tsx tooling/esbuild.build.ts",