mcpbeat

Feedback Page Generator

kostja94/feedback-page-generator

When the user wants to create, optimize, or audit a feedback or roadmap page. Also use when the user mentions "feedback page," "roadmap," "feature requests," "vote on features," "Canny," "UserVoice," or "product feedback." For sitewide page planning, use website-structure.

672 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
836
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/kostja94/marketing-skills --skill feedback-page-generator

The instruction itself

9 sections, as written by the author

Pages: Feedback / Roadmap

Guides feedback and roadmap pages that collect user input and communicate product direction. Often integrates with Canny, FeatureBase, UserVoice, or similar. Supports product-led growth and community engagement.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and roadmap priorities.

Identify:

  • Tool: Canny, FeatureBase, UserVoice, custom, or embedded form
  • Scope: Feedback only, roadmap only, or both
  • Primary goal: Collect requests, show transparency, build community
  • Audience: Users, prospects, or both

Page Structure

| Section | Purpose |

|---------|---------|

| Headline | "Share Your Ideas" or "Product Roadmap" |

| Value | We listen; your input shapes the product |

| Feedback | Form or embed; categories (feature, bug, other) |

| Roadmap | In progress, planned, completed; or link to external board |

| Process | How we prioritize; what happens after you submit |

| CTA | Submit idea, vote, view roadmap |

Best Practices

Feedback Collection

  • Low friction: Few fields; optional details
  • Categories: Feature request, Bug, General
  • Duplicate detection: "Similar ideas" to merge votes

Roadmap Display

  • Status: In progress, planned, completed
  • Transparency: Don't over-promise; "Exploring" vs "Committed"
  • Update regularly: Stale roadmap hurts trust

Integration

  • Embed: Canny, FeatureBase embed on your domain
  • Or link: /feedback → feedback.yourproduct.com
  • SEO: Often noindex for external boards; index if on your site

Output Format

  • Headline and value proposition
  • Page structure (feedback + roadmap sections)
  • Process copy (how we use feedback)
  • Integration notes (Canny, etc.)
  • SEO (index vs noindex)

Related Skills

  • docs-page-generator: Feedback process in docs
  • contact-page-generator: Alternative for simple feedback
  • changelog-page-generator: Completed roadmap items → changelog

How to use it

Copy the folder

Take kostja94/feedback-page-generator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.