[Bug]: Skill install manifests resolve Go modules with @latest

Open Beginner friendly
#301 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
devtools

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
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@latest
  • skills/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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxhsj/openclaw-zero-token

All issues in linuxhsj/openclaw-zero-token

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.