anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Skill Registry + Installer for Awesome-Claude-Skills (Make OpenCode the One Tool) #5638

New Issue
Open
opened 2026-02-16 17:55:03 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 17:55:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @super-unique-ai on GitHub (Jan 14, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

TL;DR: Add a Skill Registry plus Skills Manager to OpenCode so we can browse, install, pin, update, and remove skills from curated sources, starting with ComposioHQ/awesome-claude-skills.

🔗 Links

🧠 Motivation

OpenCode already supports Agent Skills via SKILL.md discovery. What’s missing is a distribution and management layer that makes skills easy to find, install, trust, and keep updated.

awesome-claude-skills is a large catalog of practical, repeatable workflows. Integrating it would expand OpenCode beyond coding into standardized workflows for docs, spreadsheets, research, automation, and more.

❗ Problem

Current state

  • Skills are manual to install (copy folders around).
  • No built-in way to:
    • 🔎 search a catalog
    • 📥 install and remove cleanly
    • 📌 pin versions
    • 🔁 update safely
    • 🧾 show provenance and licensing

Result

  • Skills are powerful but not discoverable.
  • Keeping skills updated is annoying and error-prone.
  • Duplication increases because reuse is hard.

✅ Proposal

1) Add a Skill Registry concept

A registry is a source of skills that OpenCode can index.

Default registry (MVP):

Future optional registries:

  • Any public Git repo
  • Private repos via auth
  • npm packages (later)

Registry metadata should include:

  • skill name
  • short description
  • category tags
  • license info plus warnings
  • version info (tag or commit SHA)
  • optional trust signals (verified registry, signed tags, etc.)

2) Add a Skills Manager (CLI and TUI first)

Ship core functionality behind commands first (UI can come later after design review).

Suggested commands

/skills search <query>
/skills info <skill>
/skills install <skill> [--version <sha|tag>] [--scope user|project]
/skills update [<skill>]
/skills remove <skill>
/skills list

Install scopes

  • User scope (global)
    ~/.config/opencode/skills/<skill>/SKILL.md

  • Project scope (local, preferred default)
    .opencode/skills/<skill>/SKILL.md

This complements the existing Agent Skills discovery model.

🎯 MVP Deliverables

📚 Registry indexing

  • Fetch registry source (git clone or pull)
  • Detect skill folders containing SKILL.md
  • Build an index (name, description, tags)

📥 Install plus provenance

  • Install copies skill folder into chosen scope
  • Write a manifest file recording provenance:
    • registry source URL
    • commit SHA or tag installed
    • installed timestamp
    • installed files list (optional but ideal)

Example manifest:

{
  "source": "https://github.com/ComposioHQ/awesome-claude-skills",
  "skill": "pdf",
  "version": "a1b2c3d4",
  "installedAt": "2026-01-13T00:00:00Z",
  "scope": "project"
}

🔁 Updates

  • skills update pulls latest registry changes
  • Update re-syncs installed skills (preferably with diff preview or confirmation)
  • Preserve user edits if skills are modified locally (either warn, or require --force)

🧾 Licensing

  • Display repo license (Apache-2.0) and warn that individual skills may differ
  • Warn (or optionally block) installs when license data is missing or unclear
  • Surface license info in /skills info <skill>

🛡️ Security and Safety Considerations

Third-party skills should be treated as untrusted content by default.

Install-time confirmation should show:

  • registry source plus URL
  • pinned version (SHA or tag)
  • files to be installed
  • best-effort risk hints (heuristics):
    • filesystem access
    • shell invocation
    • network calls
    • integrations and automation

Recommended defaults

  • Prefer project scope installs to reduce unexpected global changes
  • Default to pinned installs (commit SHA) for reproducibility
  • Provide a --verify mode to show exactly what will be written before installing

🌟 Why awesome-claude-skills first

  • Large catalog, actively maintained
  • Consistent SKILL.md pattern
  • Covers high-value workflows (docs, data, automation, productivity)

Source:

✅ Acceptance Criteria

  • /skills search pdf shows results from awesome-claude-skills
  • /skills info pdf shows description, tags, license, source URL, and available versions (tag or SHA)
  • /skills install pdf --scope project installs into .opencode/skills/pdf/
  • Installed skills are discoverable and usable via OpenCode Agent Skills behavior
  • /skills install ... --version <sha|tag> pins to a deterministic version
  • /skills update updates safely and preserves provenance
  • Each installed skill includes a manifest with source plus version
  • Clear provenance plus license warnings on install

🧱 Implementation Strategy (Incremental)

  1. Registry fetch plus index
  2. Install plus manifest
  3. List and remove
  4. Update
  5. Trust model plus warnings
  6. Optional: UI layer after design review

🔁 Alternatives Considered

Manual installs (copy folders, submodules)

✅ Works for power users
❌ Not discoverable
❌ No update UX
❌ No provenance or pinning

One big bundled pack

❌ Hard to update selectively
❌ Poor provenance and attribution
❌ Doesn’t scale

🚀 Optional Path: Start as an Official Plugin

If maintainers prefer keeping core small initially, ship this as an official plugin that:

  • indexes registries
  • manages install, update, remove
  • writes into existing skills discovery paths

Then graduate parts into core once validated.

🙌 Notes for Maintainers

  • This issue is intentionally scoped to be incremental and reviewable.
  • UI can be deferred; the CLI and TUI commands provide immediate value.
  • Registry schema can start minimal and evolve (name, description, tags, license, version).
Originally created by @super-unique-ai on GitHub (Jan 14, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request > **TL;DR:** Add a **Skill Registry** plus **Skills Manager** to OpenCode so we can **browse, install, pin, update, and remove** skills from curated sources, starting with **[ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)**. --- ## 🔗 Links - 📦 Skills catalog to integrate: **[ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)** - 📚 OpenCode Agent Skills docs: **https://opencode.ai/docs/agent-skills** - 🧷 OpenCode repository: **[anomalyco/opencode](https://github.com/anomalyco/opencode)** --- ## 🧠 Motivation OpenCode already supports **Agent Skills** via `SKILL.md` discovery. What’s missing is a **distribution and management layer** that makes skills easy to **find**, **install**, **trust**, and **keep updated**. **awesome-claude-skills** is a large catalog of practical, repeatable workflows. Integrating it would expand OpenCode beyond coding into standardized workflows for docs, spreadsheets, research, automation, and more. --- ## ❗ Problem ### Current state - Skills are **manual** to install (copy folders around). - No built-in way to: - 🔎 search a catalog - 📥 install and remove cleanly - 📌 pin versions - 🔁 update safely - 🧾 show provenance and licensing ### Result - Skills are powerful but not discoverable. - Keeping skills updated is annoying and error-prone. - Duplication increases because reuse is hard. --- ## ✅ Proposal ### 1) Add a **Skill Registry** concept A registry is a **source of skills** that OpenCode can index. **Default registry (MVP):** - **[ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)** **Future optional registries:** - Any public Git repo - Private repos via auth - npm packages (later) **Registry metadata should include:** - skill name - short description - category tags - license info plus warnings - version info (tag or commit SHA) - optional trust signals (verified registry, signed tags, etc.) --- ### 2) Add a **Skills Manager** (CLI and TUI first) Ship core functionality behind commands first (UI can come later after design review). #### Suggested commands ```bash /skills search <query> /skills info <skill> /skills install <skill> [--version <sha|tag>] [--scope user|project] /skills update [<skill>] /skills remove <skill> /skills list ``` #### Install scopes - **User scope (global)** `~/.config/opencode/skills/<skill>/SKILL.md` - **Project scope (local, preferred default)** `.opencode/skills/<skill>/SKILL.md` > This complements the existing Agent Skills discovery model. --- ## 🎯 MVP Deliverables ### 📚 Registry indexing - [ ] Fetch registry source (git clone or pull) - [ ] Detect skill folders containing `SKILL.md` - [ ] Build an index (name, description, tags) ### 📥 Install plus provenance - [ ] Install copies skill folder into chosen scope - [ ] Write a manifest file recording provenance: - registry source URL - commit SHA or tag installed - installed timestamp - installed files list (optional but ideal) Example manifest: ```json { "source": "https://github.com/ComposioHQ/awesome-claude-skills", "skill": "pdf", "version": "a1b2c3d4", "installedAt": "2026-01-13T00:00:00Z", "scope": "project" } ``` ### 🔁 Updates - [ ] `skills update` pulls latest registry changes - [ ] Update re-syncs installed skills (preferably with diff preview or confirmation) - [ ] Preserve user edits if skills are modified locally (either warn, or require `--force`) ### 🧾 Licensing - [ ] Display repo license (Apache-2.0) and warn that **individual skills may differ** - [ ] Warn (or optionally block) installs when license data is missing or unclear - [ ] Surface license info in `/skills info <skill>` --- ## 🛡️ Security and Safety Considerations Third-party skills should be treated as **untrusted content by default**. **Install-time confirmation should show:** - registry source plus URL - pinned version (SHA or tag) - files to be installed - best-effort risk hints (heuristics): - filesystem access - shell invocation - network calls - integrations and automation **Recommended defaults** - Prefer **project scope** installs to reduce unexpected global changes - Default to **pinned installs** (commit SHA) for reproducibility - Provide a `--verify` mode to show exactly what will be written before installing --- ## 🌟 Why awesome-claude-skills first - Large catalog, actively maintained - Consistent `SKILL.md` pattern - Covers high-value workflows (docs, data, automation, productivity) Source: - **[ComposioHQ/awesome-claude-skills](https://github.com/ComposioHQ/awesome-claude-skills)** --- ## ✅ Acceptance Criteria - [ ] `/skills search pdf` shows results from **awesome-claude-skills** - [ ] `/skills info pdf` shows description, tags, license, source URL, and available versions (tag or SHA) - [ ] `/skills install pdf --scope project` installs into `.opencode/skills/pdf/` - [ ] Installed skills are discoverable and usable via OpenCode Agent Skills behavior - [ ] `/skills install ... --version <sha|tag>` pins to a deterministic version - [ ] `/skills update` updates safely and preserves provenance - [ ] Each installed skill includes a manifest with source plus version - [ ] Clear provenance plus license warnings on install --- ## 🧱 Implementation Strategy (Incremental) 1. Registry fetch plus index 2. Install plus manifest 3. List and remove 4. Update 5. Trust model plus warnings 6. Optional: UI layer after design review --- ## 🔁 Alternatives Considered ### Manual installs (copy folders, submodules) ✅ Works for power users ❌ Not discoverable ❌ No update UX ❌ No provenance or pinning ### One big bundled pack ❌ Hard to update selectively ❌ Poor provenance and attribution ❌ Doesn’t scale --- ## 🚀 Optional Path: Start as an Official Plugin If maintainers prefer keeping core small initially, ship this as an **official plugin** that: - indexes registries - manages install, update, remove - writes into existing skills discovery paths Then graduate parts into core once validated. --- ## 🙌 Notes for Maintainers - This issue is intentionally scoped to be **incremental** and **reviewable**. - UI can be deferred; the CLI and TUI commands provide immediate value. - Registry schema can start minimal and evolve (name, description, tags, license, version).
yindo added the discussion label 2026-02-16 17:55:03 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#5638
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?