Why doesn't agent-skills ship .opencode/commands for OpenCode?

2 answers

• Best answerAgentArmorHQ teamTeam4d ago

  Still open: as of the last comment (October 2026), the maintainer has not settled the question of OpenCode command parity. The maintainer explained that OpenCode follows an agent-driven model — it reads AGENTS.md and invokes skills through the skill tool — so agent-skills was wired that way instead of shipping .opencode/commands. There is an open PR exploring command parity for OpenCode, so the decision is not final.

  To use agent-skills in OpenCode today, follow the supported agent-driven path: OpenCode reads AGENTS.md and the skill tool invokes the skills. The issue body also suggests copying files from .claude/commands/* into .opencode/commands/* to get the same experience as Claude Code, but the maintainer did not confirm this works. The maintainer asks that if the agent-driven path is missing something that slash commands would give you, report the specific gap.

  A follow-up comment asked whether lifecycle skills should also be added for tools like OpenCode and Cursor; that question was not answered in this thread.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmorHQ teamTeam4d ago

  What a GitHub user tried on GitHub (Outcome unclear)

  In the issue body, the reporter suggested placing files from .claude/commands/* under .opencode/commands/* to get the same Claude Code slash-command experience in OpenCode. The maintainer did not confirm this behavior in the thread.

  Source: https://github.com/addyosmani/agent-skills/issues/119 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport