polyplugin

Reconcile and validate dual-host plugin manifests for Claude Code and Codex.

2|Updated May 21, 2026

Search Tags:#validation #Codex #Claude Code #plugin packaging #marketplace metadata #manifest reconciliation #release versioning

Ready to run

npx skills add https://github.com/howells/skills --skill polyplugin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: polyplugin
Source: https://github.com/howells/skills/tree/main/polyplugin
Command: npx skills add https://github.com/howells/skills --skill polyplugin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

You need a single, coherent plugin product that works across both Claude Code and Codex without the two hosts drifting into incompatible or mismatched metadata.

Core Features & Use Cases

Dual-host manifest reconciliation: Align .claude-plugin and .codex-plugin files so name, version, description, repository, license, and capabilities stay consistent.
Plugin-or-skill-collection decisioning: Choose between a true plugin boundary and a shared skill collection based on whether you need bundled runtime surfaces, commands, MCP/apps, release metadata, or host-specific behavior.
Validation-first workflow: Inventory existing manifests, propose minimal changes, and validate with claude plugins validate . and Codex validation when available.

Quick Start

Use the polyplugin skill to convert or upgrade your repo so it ships a dual-host plugin with synchronized manifests for both Claude Code and Codex.

Frequently Asked Questions about polyplugin

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make a plugin work on both Claude Code and Codex?▼

To make a plugin work on both Claude Code and Codex, you need to reconcile dual-host manifests by aligning the name, version, description, repository, license, and capabilities across both `.claude-plugin` and `.codex-plugin` files so metadata stays consistent.

What is the best way to keep plugin metadata synchronized across multiple agent hosts?▼

Keeping plugin metadata synchronized across multiple agent hosts requires a validation-first workflow that inventories existing manifests, proposes minimal changes, and runs `claude plugins validate .` alongside Codex validation to enforce consistent identity and release versioning.

Do I need a true plugin boundary or a shared skill collection for my agent tool?▼

You need a true plugin boundary instead of a shared skill collection if your product requires bundled runtime surfaces, commands, MCP/apps, release metadata, or host-specific behavior across Claude Code and Codex environments.

How do I validate agent plugin packaging for Codex and Claude?▼

Validating agent plugin packaging involves running `claude plugins validate .` for the Claude Code manifest and performing Codex validation when available to ensure both host surfaces pass structural and metadata checks.

Why does my plugin version drift between Claude and Codex manifests?▼

Plugin version drift between Claude and Codex manifests happens when `.claude-plugin` and `.codex-plugin` files are updated independently without manifest reconciliation to enforce synchronized identity and release versioning across both hosts.