skills.rest
xiongxianfei
xiongxianfeiCOMMUNITY
Explore all skills by this author →
GitHub

partial-portability

Generate a manifest listing Codex and Claude Code adapters while excluding opencode.

3|Updated Apr 19, 2026
Search Tags:#automation#compatibility#codex#manifest#claude-code#opencode#adapters
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill partial-portability
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: partial-portability
Source: https://github.com/xiongxianfei/rigorloop/tree/main/tests/fixtures/adapters/partial-portability
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill partial-portability

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that only Codex and Claude Code adapters are considered compatible, preventing accidental use of opencode.

Core Features & Use Cases

  • Identify compatible adapters for Codex and Claude Code.
  • Exclude opencode from compatibility results.
  • Generate a manifest-ready listing that downstream tools can consume.

Quick Start

Run the compatibility check to generate a manifest listing Codex and Claude Code adapters while omitting opencode.

Frequently Asked Questions about partial-portability

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

FAQPage Schema
How do I generate a compatibility manifest for Codex and Claude Code adapters?▼

To generate a compatibility manifest, run the check to identify adapters compatible with Codex and Claude Code. The process explicitly excludes opencode, delivering a precise, machine-readable listing for downstream tools to consume.

What is the best way to exclude opencode from my adapter compatibility results?▼

To exclude opencode, use a compatibility check that explicitly omits opencode entries. This limits adapter results to only Codex and Claude Code, preventing accidental use of opencode in your manifest output.

Can I use this compatibility check to enforce adapter constraints for downstream automation tools?▼

Yes, you can use this check to enforce adapter constraints. It delivers a precise, machine-readable manifest that downstream automation tools can ingest to strictly enforce compatibility constraints and prevent incompatible adapters.

Why does the compatibility manifest only include Codex and Claude Code adapters?▼

The manifest only includes Codex and Claude Code adapters to ensure teams prevent accidental use of opencode. It limits results to the two compatible adapters in a manifest-ready structure, omitting any opencode entries.

When do I need a manifest-ready listing for adapter compatibility?▼

You need a manifest-ready listing when downstream tools must ingest machine-readable data to enforce compatibility constraints. It ensures only Codex and Claude Code adapters are considered compatible, omitting opencode entries for strict enforcement.

Related Skills

Explore More Software Engineering Skills→
devopstalesdevopstales
1

engram-plugin-thin

Enforce adapter boundary rules and compatibility across Claude, OpenCode, Gemini, and Codex plugin scripts.

Community
Intermediate
Desko77Desko77
40

mermaid-diagrams

Create Mermaid diagrams with ASCII sidecars for cross-tool compatibility.

Community
Intermediate
avifeneshavifenesh
951

maintain-cross-platform

Coordinate release readiness and infrastructure integrity across Claude Code, OpenCode, and Codex CLI.

Community
Advanced
blocknaviblocknavi
1

convex-component-authoring

Create self-contained Convex components with isolated schemas and exports.

Official
Intermediate