lkn
/
ollie-core
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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 <noreply@anthropic.com>
This commit is contained in:
Levi Neely 2026-04-01 00:05:13 +02:00
parent 75cadfeb53
commit 715d68f974
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
main.go
View File

@ -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