mcp-attribution-worktree
Triage, repair, and close MCP attribution issues from the local report API with evidence-driven decisions and isolated Worktrunk worktrees. Use this skill when Codex needs to process `tool` attribution issues and skills-related attribution issues, inspect related runs, decide whether the issue is actionable in `mcp/src` or `config/source/skills`, update attribution fields as `owner=codex`, and then complete the fix loop through GitHub issue tracking, worktree-based code changes, PR submission, and follow-up iteration when the problem is repairable.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill mcp-attribution-worktree --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# MCP Attribution Worktree Process MCP and skills-related attribution issues as an auditable maintenance workflow instead of ad-hoc debugging. ## What this skill does Use this skill to: - fetch pending MCP and skills-related attribution issues from the local report API - inspect issue detail plus representative runs before making any status decision - map failures back to concrete `mcp/src` tools, `config/source/skills`, or classify them as environment / grader / duplicate noise - update attribution issues with concise evidence, `owner=codex`, and links to external GitHub work - isolate each actionable repair in its own Worktrunk worktree and branch - carry actionable issues through repo repair and PR creation instead of stopping at issue state updates - continue from existing GitHub issues or PRs when later review or evaluation feedback shows the first direction was incomplete or wrong - run a real post-PR evaluation when an evaluation interface is available, and use that result to decide whether another repair loop is needed ## Do not use this skill for - generic bug fixing without attribution evidence - unrelated attribution categories that do not map to `mcp/src` or `config/sou
- What this skill does
- Do not use this skill for
- Workflow
- Common requests
- Routing
- Model-oriented repair heuristic
- Operating rules
- Required preflight
- Required closure preflight
- Quick commands
- Minimum self-check
curl -s 'http://127.0.0.1:5174/api/attributions?category=tool&resolutionStatus=todo&limit=50' curl -s 'http://127.0.0.1:5174/api/attributions?category=skill&resolutionStatus=todo&limit=50' curl -s "http://127.0.0.1:5174/api/attributions/<issueId>" curl -s "http://127.0.0.1:5174/api/runs/<caseId>/<runId>/result" curl -s "http://127.0.0.1:5174/api/runs/<caseId>/<runId>/trace" curl -s "http://127.0.0.1:5174/api/runs/<caseId>/<runId>/evaluation-trace" wt switch --create feature/attribution-<slug> gh issue create --repo TencentCloudBase/CloudBase-MCP gh pr view <number> --comments --repo TencentCloudBase/CloudBase-MCP gh pr create --repo TencentCloudBase/CloudBase-MCP
What does the mcp-attribution-worktree skill do?
Triage, repair, and close MCP attribution issues from the local report API with evidence-driven decisions and isolated Worktrunk worktrees. Use this skill when Codex needs to process `tool` attribution issues and skills-related attribution issues, inspect related runs, decide whether the issue is actionable in `mcp/src` or `config/source/skills`, update attribution fields as `owner=codex`, and then complete the fix loop through GitHub issue tracking, worktree-based code changes, PR submission, and follow-up iteration when the problem is repairable.
How do I install it?
Run `npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill mcp-attribution-worktree --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From TencentCloudBase/CloudBase-AI-Toolkit, a repository with 1,066 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.