desktop-parity-auditor

Compare live MCPs, plugins, and connectors against core contract definitions.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/JaviMontano/jm-claude-desktop-workspace-core-backup --skill desktop-parity-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop-parity-auditor
Source: https://github.com/JaviMontano/jm-claude-desktop-workspace-core-backup/tree/main/skills/desktop-parity-auditor
Command: npx skills add https://github.com/JaviMontano/jm-claude-desktop-workspace-core-backup --skill desktop-parity-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects drift between the JM Labs core contracts and the live Claude Desktop or Codex environment, ensuring readiness before declaring the workspace healthy.

Core Features & Use Cases

  • Compare live capability planes (MCPs, plugins, connectors) against the intended core definitions.
  • Validate admin health, task orchestration readiness, and dashboard integrity across the workspace.
  • Use case: before a workspace health claim, run the parity audit to confirm there is no drift in capabilities or configurations.

Quick Start

Run parity checks against the live workspace and report any drift.

Frequently Asked Questions about desktop-parity-auditor

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

FAQPage Schema
How do I audit Claude Desktop MCP configurations for drift?

To run a parity audit, compare the live Claude Desktop or Codex workspace against JM Labs core contracts. This deterministic comparison validates MCPs, plugins, local overlays, and task orchestration to report any capability drift.

What is workspace parity drift in Claude Desktop?

Workspace parity drift occurs when live Claude Desktop MCPs, plugins, or admin dashboard configurations diverge from intended core contracts. Detecting this drift ensures task orchestration readiness and workspace health before deployment claims are made.

Can I validate admin dashboard health and task orchestration readiness?

Yes, you can validate admin dashboard health and task orchestration readiness by running a parity audit. This checks the live workspace environment against core definitions to ensure no capability drift exists across MCPs and connectors.

Do I need access to live workspace manifests to check parity?

Yes, checking parity requires access to the live workspace, capability manifests, and admin tools. This access enables a deterministic comparison between the live Claude Desktop environment and the core contracts to accurately report drift.

When should I run a parity audit for MCPs and local overlays?

Run a parity audit for MCPs and local overlays before making any workspace health claim. This ensures there is no drift in capabilities or configurations between the live Claude Desktop environment and the core contracts.