AI Assistant:
Summary
Would it be valuable to add a skill that documents how to make Claude Code plugins compatible with other AI coding assistants (Codex, OpenCode, etc.)?
Motivation
The obra/superpowers repository demonstrates excellent patterns for multi-provider support:
- Shared
/skills/ directory used by all providers
- Provider-specific adapters (
.claude-plugin/, .codex/, .opencode/)
- Tool mapping (Skill → custom CLI, TodoWrite → update_plan, etc.)
- Bootstrap injection at session start
- Skill shadowing (project > personal > plugin)
These patterns could help plugin authors who want broader reach beyond Claude Code.
Proposed Skill: multi-provider-plugins
A new skill covering:
- Architecture overview - Adapter pattern, directory structure
- Provider adapters - How to create integrations for Claude Code, Codex, OpenCode
- Tool mapping reference - Translating Claude Code tools to provider equivalents
- Bootstrap patterns - Session-start injection implementations
- Shared skills library - Structuring portable skills
References
- Pattern source: obra/superpowers
- Providers documented: Claude Code, OpenAI Codex, OpenCode
Implementation
PR with the implementation: #10
AI Assistant:
Summary
Would it be valuable to add a skill that documents how to make Claude Code plugins compatible with other AI coding assistants (Codex, OpenCode, etc.)?
Motivation
The obra/superpowers repository demonstrates excellent patterns for multi-provider support:
/skills/directory used by all providers.claude-plugin/,.codex/,.opencode/)These patterns could help plugin authors who want broader reach beyond Claude Code.
Proposed Skill:
multi-provider-pluginsA new skill covering:
References
Implementation
PR with the implementation: #10