[Bug]: Skill install manifests resolve Go modules with @latest
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Read the install manifests at skills/eightctl/SKILL.md:16 and skills/sonoscli/SKILL.md:16. Check the Go install syntax and the CLI versions each skill expects, then pin both modules to exact versions and record the tested versions if useful. Done when neither install command uses @latest and both skills still install the intended CLIs.
Written by the indexing model from the issue text.
Description
Bug type
Behavior bug (incorrect output/state without crash)
Summary
The install modules in two skills resolve a Go module at run time instead of pinning a version:
skills/eightctl/SKILL.md:16:github.com/steipete/eightctl/cmd/eightctl@latestskills/sonoscli/SKILL.md:16:github.com/steipete/sonoscli/cmd/sonos@latest
Each skill depends on specific CLI flags and output, so a new upstream release can change behavior without any change here, and two installs at different times can behave differently.
Note
Refs: main@a654bcf.
Steps to reproduce
.
Expected behavior
Pin exact versions (e.g. @v1.2.3) and bump them deliberately. Optionally record the tested version in the skill description or a comment.
Actual behavior
.
OpenClaw version
.
Operating system
.
Install method
No response
Model
.
Provider / routing chain
.
Config file / key location
No response
Additional provider/model setup details
No response
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
No response
- Dominant language
- TypeScript
- Stars
- 5.2k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from linuxhsj/openclaw-zero-token
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linuxhsj/openclaw-zero-token#302 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 57/100
linuxhsj/openclaw-zero-token#300 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
linuxhsj/openclaw-zero-token#224 · 2 reactions ·
All issues in linuxhsj/openclaw-zero-token
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day