nextlevelbuilder / nextlevelbuilder/goclaw
[Bug]: Skill scripts cannot run due to runtime access restrictions
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 24
Description
A skill can be discovered and its SKILL.md can be read, but its bundled scripts cannot be executed in the current runtime.
Example of mounted skill location: https://github.com/tolkonepiu/hl-cluster/blob/main/kubernetes/apps/automation/goclaw/app/helmrelease.yaml#L277-L281
Affected version: goclaw v2.8.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the mounted skill configuration in helmrelease.yaml at lines 277-281, then reproduce the difference between reading SKILL.md and executing its bundled scripts in the current runtime. Trace the runtime access restriction affecting the mounted skill and verify that the scripts execute under the intended safety boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100