[FEATURE]: Portable Agent Packages with Bundled Skills #7470

Open
opened 2026-02-16 18:07:17 -05:00 by yindo · 2 comments
Owner

Originally created by @jorgedanisc on GitHub (Jan 24, 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

I've been developing some agents, and something I found would be really cool is if we could make agents more portable. For example, I want to share an agent with my team, but I have skills that are dedicated just for that agent. Right now, there's no easy way to bundle everything together from what I found.

Proposed Solution

Support a standardized agent package structure that bundles agents with their dedicated skills:

~/.config/opencode/agent/my_agent/
├── AGENT.md
├── skills/
│   ├── skill-1/SKILL.md
│   ├── skill-2/SKILL.md
│   └── skill-3/SKILL.md
└── config.json (optional)
  • Package as a single folder (zip/archive for easy sharing)
  • Simple import command: opencode import agent-package.zip
  • Optional config.json to keep AGENT.md leaner

Use Cases

  • Share custom agents across team members
  • Distribute specialized agents for specific workflows
  • Version control agent packages independently

It could even expand to other configuration needs related to agents, here I just showcased a potential use case for skills and config portability, but I think there could be more plug-in that I have not thought about that could be placed inside the agent folder as well


I know this is not strictly new, I just didn't want to disrupt possible related ideas on these similarly related issues:
#5052
#3471
#6635

Originally created by @jorgedanisc on GitHub (Jan 24, 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 I've been developing some agents, and something I found would be really cool is if we could make agents more portable. For example, I want to share an agent with my team, but I have skills that are dedicated just for that agent. Right now, there's no easy way to bundle everything together from what I found. ### Proposed Solution Support a standardized agent package structure that bundles agents with their dedicated skills: ``` ~/.config/opencode/agent/my_agent/ ├── AGENT.md ├── skills/ │ ├── skill-1/SKILL.md │ ├── skill-2/SKILL.md │ └── skill-3/SKILL.md └── config.json (optional) ``` - Package as a single folder (zip/archive for easy sharing) - Simple import command: `opencode import agent-package.zip` - Optional `config.json` to keep `AGENT.md` leaner ### Use Cases - Share custom agents across team members - Distribute specialized agents for specific workflows - Version control agent packages independently It could even expand to other configuration needs related to agents, here I just showcased a potential use case for skills and config portability, but I think there could be more plug-in that I have not thought about that could be placed inside the agent folder as well --- I know this is not strictly new, I just didn't want to disrupt possible related ideas on these similarly related issues: #5052 #3471 #6635
yindo added the discussion label 2026-02-16 18:07:17 -05:00
Author
Owner

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

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

  • #3471: Streamlined Distribution for Agent Definitions - directly addresses sharing agents and packaging them with custom tools
  • #8386: Skill Registry + Installer for Awesome-Claude-Skills - proposes bundling skills with versioning and package distribution
  • #10148: Feature Request: Plugin-bundled Skills Discovery - about bundling skills within packages with auto-discovery
  • #7467: GitHub-based Agent Marketplace for Sharing and Discovering Agents - addresses agent sharing and portability across teams
  • #6207: Easily import settings/agents/MCP servers from other tools - covers import/export and agent distribution
  • #8533: Allow custom skills directories - skills organization and directory flexibility for bundling
  • #8304: plugin support skills - bundling skills within plugins
  • #10305: Import settings from Claude Code - import/export of agent definitions
  • #6347: Plugin Hook for Registering Additional Config Directories - plugin-based configuration provisioning

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 24, 2026): This issue might be a duplicate of existing issues. Please check: - #3471: Streamlined Distribution for Agent Definitions - directly addresses sharing agents and packaging them with custom tools - #8386: Skill Registry + Installer for Awesome-Claude-Skills - proposes bundling skills with versioning and package distribution - #10148: Feature Request: Plugin-bundled Skills Discovery - about bundling skills within packages with auto-discovery - #7467: GitHub-based Agent Marketplace for Sharing and Discovering Agents - addresses agent sharing and portability across teams - #6207: Easily import settings/agents/MCP servers from other tools - covers import/export and agent distribution - #8533: Allow custom skills directories - skills organization and directory flexibility for bundling - #8304: plugin support skills - bundling skills within plugins - #10305: Import settings from Claude Code - import/export of agent definitions - #6347: Plugin Hook for Registering Additional Config Directories - plugin-based configuration provisioning Feel free to ignore if none of these address your specific case.
Author
Owner

@diegohb commented on GitHub (Feb 12, 2026):

@jorgedanisc in the meantime, I've had a lot of luck using opencode-architect with some instruction about a "non-code plugin" but essentially it's a plugin. see example structure here. Today I made 2 other packages by using the opencode-architect agent and saying extract these skills and package them like github repo X (intellisearch).

Also, today I discovered playbooks.com which installs to ~/.agents/ dir, a new pattern that seems to be evolving for packaging these.

@diegohb commented on GitHub (Feb 12, 2026): @jorgedanisc in the meantime, I've had a lot of luck using [opencode-architect](https://github.com/qforge-dev/opencode-architect) with some instruction about a "non-code plugin" but essentially it's a plugin. see [example structure here](https://github.com/diegohb/opencode-intellisearch). Today I made 2 other packages by using the opencode-architect agent and saying extract these skills and package them like github repo X (intellisearch). Also, today I discovered playbooks.com which installs to ~/.agents/ dir, a new pattern that seems to be evolving for packaging these.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#7470