ZCF moving on to Codex #306
-
|
ZCF recently added support for Codex instead of being strictly bounded to Claude Code (but not in P.S. Users are moving on to OpenCode + Oh-My-OpenCode UfoMiao/zcf#244 UfoMiao/zcf#288 UfoMiao/zcf#300 |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
@TomLucidor — good flag on ZCF + Codex. This is actually great news for the ecosystem. The more agents that consume markdown-based skill instructions, the more portable the whole format becomes. We did the ZCF integration work back in January (Issue #184 — server.json manifests, MCP presets, BMAD workflows), and Codex support just extends that further. The Re: users moving to OpenCode + Oh-My-OpenCode — see my response in #305. The skill format is agent-agnostic by design. We want tonsofskills.com to be the skill marketplace regardless of which coding agent you run. — Jeremy |
Beta Was this translation helpful? Give feedback.
@TomLucidor — good flag on ZCF + Codex.
This is actually great news for the ecosystem. The more agents that consume markdown-based skill instructions, the more portable the whole format becomes. We did the ZCF integration work back in January (Issue #184 — server.json manifests, MCP presets, BMAD workflows), and Codex support just extends that further.
The
compatible-withfield we added to the skill spec can includecodexandzcfalongsideclaude-codeandcursor. If someone wants to PR those tags onto existing skills that work with ZCF/Codex, we'd merge that.Re: users moving to OpenCode + Oh-My-OpenCode — see my response in #305. The skill format is agent-agnostic by design. We want tons…