Skill Ingestion and Compatibility of OpenCode

[TomLucidor]

I think being locked in by Claude is a bit unfair since they are always at risk of jacking up prices, so I recommend the following as an alternative

• Use OpenCode as it seems to be a high-performant alternative https://github.com/anomalyco/opencode
• Use OMOC to improve automation https://github.com/code-yeongyu/oh-my-opencode
• Absorbing skills and knowledge with Borg https://github.com/aplaceforallmystuff/claude-agent-borg [Feature]: Adding a Borg function for skill integration code-yeongyu/oh-my-openagent#1160 (comment)
• Other tools mentioned by copycats like Oh-My-ClaudeCode https://github.com/obra/superpowers https://github.com/affaan-m/everything-claude-code
• vLLM options (for MLX use vLLM-MLX or MLX-OpenAI-Server, OMLX seems interesting tho)
• Blending Oh-My-OpenCode and BMAD https://github.com/cexll/myclaude?tab=readme-ov-file#modules-overview

[jeremylongshore]

Hey @TomLucidor — sorry for the late reply, and thanks for staying on this. You've been consistently pushing us toward multi-platform thinking and it's had real impact.

A few things that shipped since you posted:

1. compatible-with field in the skill spec

Skills can now declare platform compatibility in their frontmatter:

compatible-with: claude-code, cursor, opencode

The validator checks this against known platforms. This was directly informed by conversations like this one.

2. The skill format is already portable

SKILL.md is just markdown with YAML frontmatter — it's not a proprietary Claude format. Any agent that reads markdown instructions can consume these skills. OpenCode, Borg, OMOC — if they read markdown, the skills work. The allowed-tools field is the main Claude-specific piece, but it degrades gracefully (unknown tools just get ignored).

3. Rebrand to tonsofskills.com

We moved away from "claudecodeplugins.io" to a platform-neutral name. Small signal, but intentional.

4. Cursor SaaS Pack

We shipped a 30-skill Cursor pack — proof that the ecosystem isn't Claude-only.

Where we're honest about limitations

Our CI validation and testing pipeline is Claude Code-centric. We don't yet have automated testing against OpenCode or other agents. But the instruction format ports, and community PRs adding compatible-with: opencode to existing skills would be welcome.

The tools you listed (OpenCode, OMOC, Borg, vLLM) are all valid approaches. We're not trying to compete with them — we're trying to make skills portable across all of them.

Appreciate you keeping the pressure on this. It matters.

— Jeremy