openclaw - 💡(How to fix) Fix [Bug]: openclaw skills install --force --version does not fully replace existing workspace skill [1 participants]

TL;DR

The issue can be mitigated by manually updating the local metadata files after running the openclaw skills install command with the --force flag.

Guidance

• Verify that the --force flag is correctly updating the skill files, but not the metadata, by checking the file contents and metadata versions after running the command.
• Manually update the _meta.json and .clawhub/origin.json files to reflect the new version number (1.0.5 in this case) after installation.
• Consider adding a step to the openclaw skills install process to automatically update the local metadata files when the --force flag is used.
• Check the OpenClaw documentation to see if there are any known issues or workarounds for this problem.

Example

# Manually update the metadata files after installation
openclaw skills install claude-to-free --version 1.0.5 --force
# Update _meta.json
jq '.version = "1.0.5"' workspace/skills/claude-to-free/_meta.json > temp.json && mv temp.json workspace/skills/claude-to-free/_meta.json
# Update .clawhub/origin.json
jq '.installedVersion = "1.0.5"' workspace/skills/claude-to-free/.clawhub/origin.json > temp.json && mv temp.json workspace/skills/claude-to-free/.clawhub/origin.json

Notes

This workaround assumes that the issue is specific to the openclaw skills install command and not a more general problem with the OpenClaw workspace or registry.

Recommendation

Apply workaround: manually update the local metadata files after running the openclaw skills install command with the --force flag, as this will ensure that the local install is consistent with the expected version.