mcp-integration-audit

Audit MCP integration pipeline post-execution and generate implementation tickets.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/joeloverbeck/worldloom --skill mcp-integration-audit-joeloverbeck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-integration-audit
Source: https://github.com/joeloverbeck/worldloom/tree/main/.claude/skills/mcp-integration-audit
Command: npx skills add https://github.com/joeloverbeck/worldloom --skill mcp-integration-audit-joeloverbeck

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify issues in the MCP integration pipeline after a sibling skill has been executed, ensuring that the pipeline performed as expected.

Core Features & Use Cases

  • Post-Execution Audit: After running a sibling skill, this Skill analyzes the MCP integration pipeline to check for any hidden fallback patterns.
  • Implementation Ticket Generation: Identifies potential issues and generates implementation tickets for them.
  • Complexity Assessment: Assesses the complexity of the MCP integration process and helps in triaging and resolving issues.
  • Use Case: After using the branching-story-bootstrap skill, this Skill can be used to ensure that the MCP pipeline served the skill correctly and identify any potential fallback patterns that need to be addressed.

Quick Start

Run the 'mcp-integration-audit' skill with the 'target_skill_path' argument set to the directory of the skill you want to audit, e.g., 'mcp-integration-audit .claude/skills/branching-story-bootstrap'.

Frequently Asked Questions about mcp-integration-audit

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

FAQPage Schema
How do I audit MCP pipeline performance after running a Claude Code skill?

An MCP integration audit checks the pipeline for hidden fallback patterns after a sibling skill executes. It requires session evidence and codebase verification to ensure the pipeline functioned correctly and served the skill as expected.

How do I generate implementation tickets for MCP integration fallback issues?

You can generate implementation tickets by running a post-execution audit on the target skill directory. The audit assesses pipeline complexity, identifies hidden fallback patterns, and automatically produces tickets to help triage and resolve the integration issues.

What are hidden fallback patterns in an MCP integration pipeline?

Hidden fallback patterns are unintended pipeline behaviors where the MCP integration fails to serve a skill correctly. A post-execution audit identifies these patterns using session evidence and codebase verification to ensure proper pipeline functioning.

Does the MCP integration audit require session evidence and codebase verification?

Yes, the audit requires both session evidence and codebase verification to ensure proper pipeline functioning. This evidence is necessary to accurately assess integration complexity and identify hidden fallback patterns after skill execution.