opencode-skill-hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GH_TOKEN | No | Used as a fallback if GITHUB_TOKEN is unset. | |
| GITHUB_TOKEN | No | PAT with public_repo (classic) or no scopes (fine-grained). Raises rate limits and enables code search. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_project_needsA | Scan a workspace's dependency manifests (package.json, Cargo.toml, pyproject.toml, go.mod, requirements.txt) and configuration files, then report the detected stacks, frameworks and dependencies along with the specialised skills and agents the project is likely to need. Call this first, before searching or installing anything. |
| search_skills_and_agentsA | Search GitHub for reusable OpenCode/Claude skills (SKILL.md files) and MCP server configurations matching a query. Returns repository, file path and a raw download URL for each match. Set GITHUB_TOKEN in the server environment to enable code search (required for finding actual SKILL.md files). |
| install_skill_or_agentA | Install a skill or register an MCP server into an OpenCode workspace. For itemType='skill' this writes ${workspacePath}/.opencode/skills//SKILL.md, downloading it from sourceUrl or generating a documented boilerplate when sourceUrl is omitted. For itemType='mcp-server' this merges mcpConfig into ${workspacePath}/opencode.json under mcp., creating the file when needed. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools map to a clean sequential workflow: analyze the project, search for matches, then install. Each has a clearly distinct verb and target, so an agent can easily pick the right one with no overlap.
All three follow a consistent verb_noun snake_case pattern (analyze_project_needs, search_skills_and_agents, install_skill_or_agent). Predictable and readable throughout.
Three tools form a coherent discover-then-install pipeline where each earns its place, though the surface is on the lean side. A list/remove capability would round it out.
The read-then-write lifecycle (analyze, search, install) is covered, but there is no way to list already-installed skills/servers, update them, or uninstall them. These notable gaps mean agents can add but not manage or clean up.