You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Skills from skills.urls are cached by existence and never updated #33548
index.json is re-fetched on every run, but it's only used to enumerate files — nothing compares the remote content against what's already in ~/.cache/opencode/skills/<name>/. Once SKILL.md exists locally, any change published at the URL is ignored.
Repro:
Host a skill via skills.urls, start opencode (it caches SKILL.md).
Edit and re-publish the same skill at the same URL.
Restart opencode — the stale SKILL.md is still used.
The only workaround is having every user rm -rf ~/.cache/opencode/skills/<name>. That doesn't scale when you maintain a shared catalog and ship fixes.
Proposal: make the cache version-aware. index.json already round-trips on every run, so an optional version (or content hash/etag) per skill entry is enough — on pull, if the cached version differs from the index, re-download that skill's files. No version present → current behavior, so it stays backward compatible.
Happy to send a PR if this direction is acceptable.
This issue might be related to existing issues. Please check:
SKILL reference not update after edit the SKILL #19050: SKILL reference not updated after editing — covers local skill files not refreshing within a running session (different root cause, but same general theme of stale skill content)
These are not exact duplicates — #33548 specifically targets remote skills.urls cached files never being re-downloaded across restarts, which is a distinct scenario. Flagging in case the maintainers want to coordinate or track together.
Activity
github-actions commentedon Jun 23, 2026
This issue might be related to existing issues. Please check:
These are not exact duplicates — #33548 specifically targets remote
skills.urlscached files never being re-downloaded across restarts, which is a distinct scenario. Flagging in case the maintainers want to coordinate or track together.