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

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

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.

Compare cursor-team-kit/skills/pr-review-canvas/SKILL.md with pr-review-canvas/skills/pr-review-canvas/SKILL.md, starting with their frontmatter, headings, and workflow descriptions. Confirm the intended distinction with maintainers, then make the skill identity and documentation unambiguous by applying one of the proposed rename, merge, or cross-link approaches.