audit-consistency

Audits deBridge ecosystem tool definitions and documentation for inconsistencies and drift.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/debridge-finance/debridge-skills --skill audit-consistency-debridge-finance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-consistency
Source: https://github.com/debridge-finance/debridge-skills/tree/main/.claude/skills/audit-consistency
Command: npx skills add https://github.com/debridge-finance/debridge-skills --skill audit-consistency-debridge-finance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit deBridge ecosystem surfaces to identify mismatches and drift across MCP server tools, skill resources, this repository's skills, and upstream references, ensuring a single source of truth.

Core Features & Use Cases

  • Detect tool name drift and parameter mismatches between MCP, skills, and upstream SKILL.md.
  • Validate workflow alignment across get_instructions, skill resources, and repository documentation.
  • Flag stale or missing references to maintain consistency during updates and deployments.

Quick Start

Run a comprehensive audit to surface inconsistencies across deBridge tool definitions and documentation.

Frequently Asked Questions about audit-consistency

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

FAQPage Schema
How do I audit cross-source tool consistency and flag drift in MCP servers?

Tool name drift occurs when tool definitions mismatch across MCP servers and skill resources. You detect this drift by running a comprehensive audit that flags tool name validity and parameter coverage mismatches across the deBridge ecosystem.

What is cross-surface consistency governance for deBridge skills?

Cross-surface consistency governance enforces a single source of truth across deBridge MCP tools, repository skills, and upstream references. It validates workflow alignment and flags stale references to maintain consistency during deployments.

How do I validate workflow alignment across skill resources and upstream references?

You validate workflow alignment by auditing get_instructions, skill resources, and repository documentation. The audit enforces parameter coverage and flags stale references to ensure workflows match across all deBridge ecosystem surfaces.

Does the deBridge audit tool check parameter coverage and tool name validity?

Yes, the consistency audit enforces tool name validity and parameter coverage. It detects parameter mismatches between MCP server tools, skill resources, and upstream SKILL.md references to maintain ecosystem alignment.

Why does tool definition drift happen between MCP servers and skill resources?

Tool definition drift happens when updates are applied inconsistently across MCP servers, repository skills, and upstream references. The audit identifies these mismatches and flags stale references to restore a single source of truth.

When should I run a comprehensive consistency audit for deBridge ecosystem updates?

Run a consistency audit during updates and deployments to flag stale or missing references. This prevents workflow misalignment and ensures parameter coverage remains consistent across MCP tools and skill resources.