surface-parity

Audit method presence and response shape parity across CLI, API, and MCP surfaces.

6|3|Updated Jan 28, 2026

Search Tags:#api #cli #eslint #mcp #parity #surface-parity

Ready to run

npx skills add https://github.com/jamesaphoenix/tx --skill surface-parity

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: surface-parity
Source: https://github.com/jamesaphoenix/tx/tree/main/.claude/skills/surface-parity
Command: npx skills add https://github.com/jamesaphoenix/tx --skill surface-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures shape and behavior parity across CLI, API, and MCP by auditing surface methods, aligning response shapes, and guiding repeatable fixes in an internal loop that keeps surfaces in sync without shipping to users.

Core Features & Use Cases

Audit missing or inconsistent surface methods across CLI, API, and MCP.
Normalize naming, fill shape gaps, and align behavior for identical responses.
Use cases include enforcing parity before cross-surface releases and during refactors.

Quick Start

Run the parity loop across CLI, API, and MCP to audit, fix gaps, and re-audit until parity is achieved.

Frequently Asked Questions about surface-parity

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

FAQPage Schema

How do I audit CLI, API, and MCP surface parity for missing methods?▼

Surface parity is the practice of ensuring method presence and consistent response shapes across CLI, API, and MCP interfaces. It prevents behavior gaps by auditing naming and shape alignment before cross-surface releases.

How do I enforce consistent response shapes across CLI, API, and MCP?▼

You enforce consistent response shapes by running the parity audit loop, which detects shape gaps across CLI, API, and MCP interfaces and guides iterative fixes to normalize naming and align behavior for identical responses.

Does surface parity work with eslint rules tx/require-surface-parity and tx/interface-parity?▼

Yes, the parity audit requires maintaining alignment with eslint rules tx/require-surface-parity and tx/interface-parity to validate readiness and enforce method presence and consistent response shapes across CLI, API, and MCP domains.

When do I need to run a cross-surface parity audit?▼

You need to run a cross-surface parity audit before cross-surface releases and during refactors. It validates readiness by detecting missing methods, shape gaps, and behaviour gaps across CLI, API, and MCP to prevent shipping inconsistencies.

What is the best way to resolve behavior gaps across API and CLI interfaces?▼

The best way to resolve behavior gaps is to execute the parity audit repeatedly, allowing it to guide iterative fixes that fill shape gaps, normalize naming, and align behavior across API and CLI until all surfaces are in sync.