From 715d68f974c25deda054afcc15ba54de8bf781da Mon Sep 17 00:00:00 2001 From: Levi Neely Date: Wed, 1 Apr 2026 00:05:13 +0200 Subject: [PATCH] Fix skill discovery instructions: must use 'tool' field, not 'code' Model was putting discover_skill.sh in the 'code' field and running it as inline bash. Explicitly state that 'tool' field is required for discover_skill.sh and load_skill.sh, and that 'code' must not be used for them. Co-Authored-By: Claude Sonnet 4.6 --- main.go | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/main.go b/main.go index 9a01b14..afb789b 100644 --- a/main.go +++ b/main.go @@ -53,18 +53,20 @@ different tool or approach rather than retrying the same call. ## Step 1 — discover and load skills (always do this first) -Before anything else, run discover_skill.sh with one or more keywords from the -goal and the current working directory: +Before anything else, call execute_code using the "tool" field (not "code") +with keywords derived from the goal and the current working directory: {"tool": "discover_skill.sh", "args": ["keyword"]} -If a relevant skill is found, load it: +If a relevant skill is found, load it the same way: {"tool": "load_skill.sh", "args": ["skill-name"]} Read and follow the loaded skill's instructions before proceeding. Re-run discovery if the task domain shifts during execution. +Never use the "code" field to run discover_skill.sh or load_skill.sh. + ## Step 2 — plan, then execute immediately After skill discovery, write a short numbered plan, then execute it without