Duplicate skill slug `pr-review-canvas` (Team Kit vs plugin) diverges HTML vs Cursor Canvas workflows

[zechsmerquis]

Summary

Two different workflows share the same Agent Skill YAML name: pr-review-canvas, which makes the product guidance confusing when both the Cursor Team Kit bundle and the standalone PR Review Canvas plugin are installed.

Where

Location	Deliverable / workflow
cursor-team-kit/skills/pr-review-canvas/SKILL.md	Interactive PR walkthrough as a standalone HTML page (gh api, temp files, local python3 -m http.server, renderer.js). Frontmatter describes HTML output; uses disable-model-invocation: true.
pr-review-canvas/skills/pr-review-canvas/SKILL.md	Cursor Canvas workflow (gh pr diff, aligns with Canvas conventions / .canvas.tsx). Matches the standalone plugin description on the Marketplace.

User impact

• The same skill identifier implies one capability, but the runbooks contradict (HTML artifact vs Cursor Canvas).
• Both use the heading # PR Review Canvas, which reinforces the mismatch for the HTML path.

Suggested fixes (any one helps)

1. Rename the Team Kit skill (for example pr-review-html or pr-review-static-html) so name: is unique in this repo, and retitle/description so “Canvas” means the same thing as elsewhere in Cursor.
2. Merge into a single skill with an explicit fork: Cursor Canvas vs static HTML export, if one entry point is preferred.
3. Cross-link the two skills so people who install both understand which to invoke.

Thanks for maintaining these plugins—the HTML reviewer toolkit is substantial; it mainly needs a distinct skill identity from the Canvas-focused plugin.