[FEATURE]: Skill Update Notification and Auto-Update Mechanism #7017

Open
opened 2026-02-16 18:05:55 -05:00 by yindo · 3 comments
Owner

Originally created by @moonjoke001 on GitHub (Jan 20, 2026).

Originally assigned to: @thdxr on GitHub.

Problem

Currently, skills installed in OpenCode (via git clone or manual copy) have no update mechanism:

  1. No update notification - Users don't know when upstream skills have new versions
  2. No auto-update - Must manually git pull or re-clone each skill
  3. No version tracking - No way to see installed vs latest version

This is especially problematic for popular skills like:

  • obra/superpowers (currently at v4.0.3)
  • OthmanAdi/planning-with-files (currently at v2.4.1)
  • nextlevelbuilder/ui-ux-pro-max-skill

Proposed Solution

Option A: Update Check Command

opencode skill check-updates
# Output:
# superpowers: v4.0.1 → v4.0.3 (update available)
# planning-with-files: v2.4.1 (up to date)

Option B: Startup Notification

On startup, check for updates and show notification:

[!] 2 skill updates available. Run `/skill update` to update.

Option C: Auto-Update (with config flag)

// opencode.json
{
  "skill": {
    "autoUpdate": true,  // or "notify" or false
    "checkInterval": "daily"
  }
}

Implementation Considerations

  1. Skills installed via git clone can use git fetch to check for updates
  2. Skills from npm plugins would follow npm update mechanism (per PR #9010)
  3. Need to track installation source (git URL vs manual copy vs npm)

Related Issues

  • #8386 - Skill Registry proposal (includes version management)
  • #9010 - Plugin skill support (npm-based updates)
  • #6013 - Add Skill Configuration to Config Type

Environment

  • OpenCode v1.1.28
  • Skills installed via git clone to ~/.config/opencode/skills/
Originally created by @moonjoke001 on GitHub (Jan 20, 2026). Originally assigned to: @thdxr on GitHub. ## Problem Currently, skills installed in OpenCode (via git clone or manual copy) have no update mechanism: 1. **No update notification** - Users don't know when upstream skills have new versions 2. **No auto-update** - Must manually `git pull` or re-clone each skill 3. **No version tracking** - No way to see installed vs latest version This is especially problematic for popular skills like: - `obra/superpowers` (currently at v4.0.3) - `OthmanAdi/planning-with-files` (currently at v2.4.1) - `nextlevelbuilder/ui-ux-pro-max-skill` ## Proposed Solution ### Option A: Update Check Command ```bash opencode skill check-updates # Output: # superpowers: v4.0.1 → v4.0.3 (update available) # planning-with-files: v2.4.1 (up to date) ``` ### Option B: Startup Notification On startup, check for updates and show notification: ``` [!] 2 skill updates available. Run `/skill update` to update. ``` ### Option C: Auto-Update (with config flag) ```json // opencode.json { "skill": { "autoUpdate": true, // or "notify" or false "checkInterval": "daily" } } ``` ## Implementation Considerations 1. Skills installed via git clone can use `git fetch` to check for updates 2. Skills from npm plugins would follow npm update mechanism (per PR #9010) 3. Need to track installation source (git URL vs manual copy vs npm) ## Related Issues - #8386 - Skill Registry proposal (includes version management) - #9010 - Plugin skill support (npm-based updates) - #6013 - Add Skill Configuration to Config Type ## Environment - OpenCode v1.1.28 - Skills installed via git clone to `~/.config/opencode/skills/`
Author
Owner

@github-actions[bot] commented on GitHub (Jan 20, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #8386: Comprehensive Skill Registry + Installer proposal that includes version management, pinned installs, and update mechanisms
  • #8751: Hot-reload feature that enables agents to create and reload skills on-the-fly
  • #7846: /skills command for listing and quick-invoking skills with better discoverability

#8386 in particular addresses most of the core functionality proposed here (update checks, version tracking, and auto-update via registry mechanism), though with a broader scope. The approaches are complementary - #8386 focuses on registry-based installation and management, while this issue focuses on update notifications for existing installations.

Feel free to ignore if your use case requires a different approach or if you'd like to track standalone update mechanisms separate from the registry system.

@github-actions[bot] commented on GitHub (Jan 20, 2026): This issue might be a duplicate of existing issues. Please check: - #8386: Comprehensive Skill Registry + Installer proposal that includes version management, pinned installs, and update mechanisms - #8751: Hot-reload feature that enables agents to create and reload skills on-the-fly - #7846: /skills command for listing and quick-invoking skills with better discoverability #8386 in particular addresses most of the core functionality proposed here (update checks, version tracking, and auto-update via registry mechanism), though with a broader scope. The approaches are complementary - #8386 focuses on registry-based installation and management, while this issue focuses on update notifications for existing installations. Feel free to ignore if your use case requires a different approach or if you'd like to track standalone update mechanisms separate from the registry system.
Author
Owner

@nokaka commented on GitHub (Jan 20, 2026):

This is really necessary; here are some projects you can refer to.

https://github.com/numman-ali/openskills
https://github.com/vercel-labs/add-skill
https://github.com/buzhangsan/skills-manager-client/blob/master/docs/README_EN.md

@nokaka commented on GitHub (Jan 20, 2026): This is really necessary; here are some projects you can refer to. https://github.com/numman-ali/openskills https://github.com/vercel-labs/add-skill https://github.com/buzhangsan/skills-manager-client/blob/master/docs/README_EN.md
Author
Owner

@thoroc commented on GitHub (Feb 15, 2026):

Should we mention there is the vercel's solution as well? skills.sh

@thoroc commented on GitHub (Feb 15, 2026): Should we mention there is the vercel's solution as well? skills.sh
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7017