mcp-attribution-worktree

Triage MCP attribution issues and link local report data to GitHub repair workflows.

1.1k|133|Updated May 23, 2025
One-click install
npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill mcp-attribution-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-attribution-worktree
Source: https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/skills/mcp-attribution-worktree
Command: npx skills add https://github.com/TencentCloudBase/CloudBase-AI-Toolkit --skill mcp-attribution-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of managing and resolving attribution issues within the MCP and skills-related configuration, replacing ad-hoc debugging with an auditable, evidence-driven maintenance workflow.

Core Features & Use Cases

  • Evidence-Driven Triage: Fetches pending attribution issues and inspects representative runs to determine if they are actionable or noise.
  • Isolated Repair: Uses Worktrunk to create dedicated worktrees for each fix, ensuring changes are isolated and auditable.
  • Full Lifecycle Management: Guides the user through the entire loop from triage and GitHub issue linkage to PR submission and post-PR evaluation.

Quick Start

Use the mcp-attribution-worktree skill to fetch the pending tool attribution backlog and begin the triage process for the first actionable issue.

Frequently Asked Questions about mcp-attribution-worktree

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

FAQPage Schema
How do I automate triage and resolution for MCP tool attribution issues?

Automating MCP attribution triage involves linking local report API data to GitHub repair workflows, inspecting representative runs to filter noise, and creating isolated worktrees for auditable closure of technical debt.

What is the best way to manage isolated worktrees for fixing model attribution configuration?

Managing isolated worktrees for attribution configuration requires using dedicated branching mechanisms to isolate each fix, ensuring changes are auditable and separated from the main codebase before PR submission.

How does evidence-driven debugging work for resolving skills-related attribution errors?

Evidence-driven debugging for attribution errors fetches pending backlog issues and inspects representative runs to validate whether they are actionable, replacing ad-hoc debugging with an auditable maintenance workflow.

Can I link local report API data directly to GitHub issues for tool attribution maintenance?

Yes, linking local report API data to GitHub issues provides full lifecycle management for tool attribution maintenance, guiding the process from initial triage and issue linkage through PR submission and post-PR evaluation.

Why use isolated worktree management when repairing model-facing contract improvements?

Isolated worktree management ensures that model-facing contract improvements are separated and evidence-based, preventing configuration conflicts and providing an auditable trail for resolving technical debt.

What are the limitations of ad-hoc debugging for MCP attribution configuration?

Ad-hoc debugging for MCP attribution configuration lacks auditable closure and evidence-based validation, making it difficult to track technical debt resolution across interconnected tool and skill maintenance workflows.