create-theokit 1.5.1 → 1.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-theokit",
-  "version": "1.5.1",
+  "version": "1.7.0",
   "type": "module",
   "description": "Scaffold a new TheoKit project",
   "license": "Apache-2.0",

package/templates/default/agents/chat.ts

@@ -1,5 +1,4 @@
 import { agent } from '@theokit/agents'
-import { defineSkillReadTool } from '@theokit/sdk'
 import { z } from 'zod'
 
 import { BASE_INSTRUCTIONS } from './prompts/instructions.js'
@@ -25,7 +24,9 @@ export default agent()
   .system(BASE_INSTRUCTIONS)
   .tool(weatherTool)
   .tool(currentTimeTool)
-  // `defineSkillReadTool` exposes the skills to the model as an on-demand `skill_read` tool — the model
-  // sees each skill's name + description and loads the full body only when it needs it.
-  .tool(defineSkillReadTool([dailyBriefingSkill]))
+  // `.skills([...])` wires the code-defined skill in ONE call: the SDK lists its name + description in a
+  // `<skills>` block every turn (cheap, so the model KNOWS it exists) AND auto-provisions a `skill_read`
+  // tool the model calls to load the full body on demand (so a long procedure only enters the prompt
+  // when needed). Pass a filesystem skill NAME (a string) here too; mix strings + createSkill freely.
+  .skills([dailyBriefingSkill])
   .build()

package/templates/default/agents/prompts/instructions.ts

@@ -16,6 +16,6 @@ export const BASE_INSTRUCTIONS = `You are a helpful assistant living inside a Th
   what failed and what you need (e.g. a valid city or IANA timezone).
 
 ## Skills
-- You have a \`skill_read\` tool that lists documented procedures (skills). When a request matches a
-  skill's description — e.g. the user asks for a "briefing" / "morning update" / "what's my day looking
-  like" (the **daily-briefing** skill) — call \`skill_read\` to load its steps, then follow them.`
+- The \`<skills>\` block above lists documented procedures (skills) by name + description. When a request
+  matches a skill's description, call the \`skill_read\` tool with that skill's name to load its full
+  steps, then follow them. Don't guess a procedure a skill already documents.`

package/templates/default/agents/skills/daily-briefing.ts

@@ -4,8 +4,8 @@ import { createSkill } from '@theokit/sdk'
  * A real, code-defined skill (`createSkill`) — a documented procedure the MODEL can pull in on demand.
  *
  * Unlike a loose Markdown note, this is wired into the agent: `agents/chat.ts` passes it to
- * `defineSkillReadTool([...])`, which gives the model a `skill_read` tool. The model sees the skill's
- * name + description in every turn (cheap) and calls `skill_read('daily-briefing')` to load the full
+ * `.skills([dailyBriefingSkill])`. That one call lists the skill's name + description in a `<skills>`
+ * block every turn (cheap) AND provisions a `skill_read` tool the model calls to load the full
  * `instructions` only when it actually needs them — so long procedures don't bloat every prompt.
  *
  * Lives in `agents/skills/` — a semantic folder the route scanner skips, so it never becomes an endpoint.

package/templates/default/package.json.tmpl

@@ -15,8 +15,8 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "theokit": "^0.31.0",
-    "@theokit/agents": "^0.35.2",
+    "theokit": "^0.36.0",
+    "@theokit/agents": "^0.38.0",
     "@theokit/sdk": "^2.25.0",
     "@theokit/ui": "^1.0.0",
     "@usetheo/ui": "^0.14.0",