Repository navigation
Skills being over-used #18
Replies: 1 comment
|
Thanks for the detailed report. I reproduced it in a test RPG scaffold: with an inventory and abilities already in place, asking Claude Code to extend them loaded Fixed in v1.17.0. The card and the bootstrap now say: to change or extend a system the project already has, follow the project's code; docs and repo tooling need no skill. Same prompts after the change: 0 of 5 loads, same graded answer quality. My test harness only runs Claude Code, so I did not measure Codex. What I can say is that Codex now loads about 40% less bootstrap text every session (15.3 KB down to 9.1 KB), and it carries the same rule. Turning off single skills: the README has a table for every host: https://github.com/jame581/GodotPrompter#using-fewer-skills
If you added a This fix is in v1.17.0, now released. Its Godot 4.8 content was checked against 4.8-beta3 and will be re-checked at 4.8-stable in a follow-up release. |
Uh oh!
There was an error while loading. Please reload this page.
Something like 60% of my token usage is eaten up by agents using skills from GodotPrompter. I do like the plugin overall, and I do think the quality of the agents' work has increased, but I think they are over-eagerly calling the skills. The worst offenders are when they call the skills related to inventory system or ability system just because my project is an RPG. Those systems are already in place in my project and they're much more complex as well. There's no benefit for the agents to use those skills in that scenario. Same goes for the "brainstorming" skill. Especially Codex constantly uses it, even for changes that doesn't touch Godot related stuff.
So - my question is: Can I turn off individual skills? How are others solving this issue?
All reactions