/sidebar
When the user wants to design, optimize, or audit a sidebar for blogs, docs, or content pages. Also use when the user mentions "sidebar," "blog sidebar," "content sidebar," "side panel," "sidebar navigation," "related content," "sidebar CTA," "doc sidebar," or "sidebar widgets."
$ npx -y skills add kostja94/marketing-skills --skill sidebar --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
/sidebar
Context preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to design, optimize, or audit a sidebar for blogs, docs, or content pages. Also use when the user mentions "sidebar," "blog sidebar," "content sidebar," "side panel," "sidebar navigation," "related content," "sidebar CTA," "doc sidebar," or "sidebar widgets."
SKILL.md
sidebar.SKILL.mdname: sidebar-generator
description: When the user wants to design, optimize, or audit a sidebar for blogs, docs, or content pages. Also use when the user mentions "sidebar," "blog sidebar," "content sidebar," "side panel," "sidebar navigation," "related content," "sidebar CTA," "doc sidebar," or "sidebar widgets." For blog layout, use blog-page-generator.
metadata:
version: 1.0.1
Components: Sidebar
Guides sidebar design for content sites (blogs, docs). ~80% of users focus on the left; sidebars influence flow but can hurt conversion if overused. Posts without sidebars show 3.1x higher conversion; bottom-right sticky CTAs outperform sidebars (5.62% vs 0.58% CTR).
**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 content structure and conversion goals.
Identify: 1. **Content type**: Blog, docs, e-commerce 2. **Primary goal**: Navigation, CTA, related content 3. **Mobile**: Collapse to hamburger or hide on small screens
Best Practices
Placement
- **Left sidebar**: Prime for nav; 80% of users focus left
- **Right sidebar**: Secondary content, ads, related posts
- **Static vs sticky**: Static for content-focused; sticky for persistent CTA (subscription, cart)
Conversion Reality
| Approach | Typical result | |----------|----------------| | **Sidebar CTA** | <1% opt-in for blog sidebars | | **In-content CTA** | 3x+ higher conversion | | **Bottom-right sticky** | 5.62% CTR vs 0.58% sidebar | | **No sidebar** | 3.1x higher conversion vs with sidebar |
**Recommendation**: Prefer in-content CTAs or bottom-right sticky over sidebar CTAs. Use sidebar for nav and discovery, not primary conversion.
Widget Guidelines
- **One high-value CTA** max; avoid clutter
- **Social proof**: Testimonials, logos
- **Popular/related posts**: Discovery, internal linking
- **Avoid**: Too many ads, affiliate links; reduces trust and speed
Mobile
- **Collapse**: Hamburger or off-canvas drawer
- **57%+ mobile traffic**: Responsive design non-negotiable
- **Reduce clutter**: Hide or simplify sidebar on small screens
Output Format
- **Placement** (left/right, static/sticky)
- **Widget** list (nav, CTA, related, social proof)
- **Mobile** behavior
- **Conversion** note (in-content vs sidebar CTA)
Related Skills
- **toc-generator**: TOC often in sidebar for long content
- **cta-generator**: Sidebar CTA (use sparingly)
- **newsletter-signup-generator**: Sidebar signup; consider in-content instead
- **internal-links**: Related posts in sidebar
Read more
name: sidebar-generator description: When the user wants to design, optimize, or audit a sidebar for blogs, docs, or content pages. Also use when the user mentions "sidebar," "blog sidebar," "content sidebar," "side panel," "sidebar navigation," "related content," "sidebar CTA," "doc sidebar," or "sidebar widgets." For blog layout, use blog-page-generator. metadata: version: 1.0.1
Components: Sidebar
Guides sidebar design for content sites (blogs, docs). ~80% of users focus on the left; sidebars influence flow but can hurt conversion if overused. Posts without sidebars show 3.1x higher conversion; bottom-right sticky CTAs outperform sidebars (5.62% vs 0.58% CTR).
**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 content structure and conversion goals.
Identify: 1. **Content type**: Blog, docs, e-commerce 2. **Primary goal**: Navigation, CTA, related content 3. **Mobile**: Collapse to hamburger or hide on small screens
Best Practices
Placement
- **Left sidebar**: Prime for nav; 80% of users focus left
- **Right sidebar**: Secondary content, ads, related posts
- **Static vs sticky**: Static for content-focused; sticky for persistent CTA (subscription, cart)
Conversion Reality
| Approach | Typical result | |----------|----------------| | **Sidebar CTA** | <1% opt-in for blog sidebars | | **In-content CTA** | 3x+ higher conversion | | **Bottom-right sticky** | 5.62% CTR vs 0.58% sidebar | | **No sidebar** | 3.1x higher conversion vs with sidebar |
**Recommendation**: Prefer in-content CTAs or bottom-right sticky over sidebar CTAs. Use sidebar for nav and discovery, not primary conversion.
Widget Guidelines
- **One high-value CTA** max; avoid clutter
- **Social proof**: Testimonials, logos
- **Popular/related posts**: Discovery, internal linking
- **Avoid**: Too many ads, affiliate links; reduces trust and speed
Mobile
- **Collapse**: Hamburger or off-canvas drawer
- **57%+ mobile traffic**: Responsive design non-negotiable
- **Reduce clutter**: Hide or simplify sidebar on small screens
Output Format
- **Placement** (left/right, static/sticky)
- **Widget** list (nav, CTA, related, social proof)
- **Mobile** behavior
- **Conversion** note (in-content vs sidebar CTA)
Related Skills
- **toc-generator**: TOC often in sidebar for long content
- **cta-generator**: Sidebar CTA (use sparingly)
- **newsletter-signup-generator**: Sidebar signup; consider in-content instead
- **internal-links**: Related posts in sidebar
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

