skills.rest
quaid-app
quaid-appOFFICIAL
Explore all skills by this author →
WebsiteGitHub

frozen-public-contracts

Surface diagnostics without breaking frozen MCP/JSON contracts.

3|3|Updated Apr 13, 2026
Search Tags:#mcp#diagnostics#contract-testing#open-spec#api-compatibility#frozen-contracts
One-click install
npx skills add https://github.com/quaid-app/quaid --skill frozen-public-contracts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frozen-public-contracts
Source: https://github.com/quaid-app/quaid/tree/main/.squad/skills/frozen-public-contracts
Command: npx skills add https://github.com/quaid-app/quaid --skill frozen-public-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pattern to surface diagnostics when a surface is frozen in the OpenSpec/MCP contract, preventing unintended changes that could destabilize downstream tooling.

Core Features & Use Cases

  • Treat exact-key tests as hard contract locks to prevent unapproved surface changes.
  • Prefer CLI-only widening before MCP widening to minimize contract churn.
  • Differentiate plain-text CLI output from MCP JSON surface and update artifacts when the contract is reopened or updated.

Quick Start

Apply the frozen-contract pattern to safely expose diagnostics without breaking a frozen MCP/JSON contract.

Frequently Asked Questions about frozen-public-contracts

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

FAQPage Schema
How do I add diagnostics to a frozen MCP contract without breaking API compatibility?▼

To add diagnostics to a frozen MCP contract without breaking API compatibility, apply the frozen-contract pattern: treat exact-key tests as hard locks, prefer CLI-only widening before altering MCP JSON surfaces, and keep plain-text CLI output distinct from MCP JSON.

What is the best way to surface QA diagnostics when an OpenSpec API surface is frozen?▼

The best way to surface QA diagnostics over a frozen OpenSpec surface is to widen the plain-text CLI output first, avoiding MCP JSON changes to prevent contract drift and minimize downstream tooling destabilization.

Why do exact-key tests act as hard locks in frozen contract testing?▼

Exact-key tests act as hard locks in frozen contract testing to prevent unapproved surface changes, ensuring that any diagnostic additions do not alter the established MCP JSON key structure and break API compatibility.

Can I use CLI widening to avoid MCP contract drift when exposing troubleshooting data?▼

Yes, you can use CLI widening to avoid MCP contract drift. By adding diagnostic output to the plain-text CLI instead of the MCP JSON surface, you prevent contract drift while still exposing necessary troubleshooting data.

When should I update MCP JSON artifacts for diagnostics in a frozen contract?▼

You should update MCP JSON artifacts for diagnostics only when the frozen contract is officially reopened or updated, ensuring exact-key test locks are intentionally released before altering the MCP JSON surface.

Does frozen-public-contracts differentiate CLI output from MCP JSON surfaces?▼

Yes, frozen-public-contracts differentiates plain-text CLI output from the MCP JSON surface, applying patterns that treat exact-key tests as hard locks to prevent unintended contract drift when shipping diagnostics.

Related Skills

Explore More Legal & Compliance Skills→
taurgistaurgis
27

mcp-yaml-testing

Validate YAML-based MCP test definitions with Aegis before execution.

Community
Intermediate
DigicationDigication

fake-skill

Provide a frozen test fixture for deterministic skill-dev evaluation and parsing.

Official
Basic
nuno7lopesnuno7lopes

apple-reminders

Manage Apple Reminders via remindctl CLI with list operations and date filters.

Community
Basic
equaltoaiequaltoai
3

preserve-mcp-contract

Analyzes MCP contract changes for compatibility and compliance.

Official
Advanced