skillboardUpdated every 6 hours
skillboardWhen 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.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and roadmap priorities.
Identify:
| 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 |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/feedback · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/feedback"
cp -r "skills/pages/utility/feedback" ".claude/skills/feedback"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.