/feedback
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.
$ npx -y skills add kostja94/marketing-skills --skill feedback --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/feedback
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
feedback.SKILL.mdname: feedback-page-generator
description: 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.
metadata:
version: 1.0.1
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: 1. **Tool**: Canny, FeatureBase, UserVoice, custom, or embedded form 2. **Scope**: Feedback only, roadmap only, or both 3. **Primary goal**: Collect requests, show transparency, build community 4. **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
Read more
name: feedback-page-generator description: 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. metadata: version: 1.0.1
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: 1. **Tool**: Canny, FeatureBase, UserVoice, custom, or embedded form 2. **Scope**: Feedback only, roadmap only, or both 3. **Primary goal**: Collect requests, show transparency, build community 4. **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
Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.
Repo: kostja94/marketing-skills
Other skills on kostja94-marketing-skills.
- /google-search-console
When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries,"
Open skill - /seo-monitoring
When the user wants to build an SEO data analysis system, monitor indexing/traffic/keywords/backlinks, or set up benchmarks. Also use when the user mentions "SEO data analysis," "SEO monitoring," "article database," "traffic benchmark," "penalty recovery," "SEO work document,"
Open skill - /ai-traffic
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to
Open skill - /traffic
When the user wants to analyze website traffic sources, attribution, or dark traffic. Also use when the user mentions "traffic sources," "dark traffic," "direct traffic," "UTM parameters," "traffic attribution," "channel attribution," "attribution optimization," "channel
Open skill - /tracking
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event
Open skill - /community-forum
When the user wants to promote via forums, communities, or invite users to join a community. Also use when the user mentions "forum promotion," "Indie Hacker," "Hacker News," "community growth," "Discord promotion," "vertical community," "brand encyclopedia," "Wikipedia,"
Open skill