sales-huzzler
Huzzler platform help — founder community and weekly product launch competition for startups. Covers Launch Arena (Mon-Wed submissions, Wed-Sun voting, Gold/Silver/Bronze badges with dofollow backlinks for winners only), community categories (#feedback, #showcases, #wins, #growth, #marketing), Huzzler Black ($79 one-time — lifetime premium visibility, verified badge, SEO boost, no ads), product showcases, Stripe-verified MRR, advertising credits ($34 promoted), AI-free community policy, and referral system. Use when your product needs more visibility among founders, want to win a Huzzler Launch Arena badge, unsure if Huzzler Black is worth it, or trying to earn a dofollow backlink from the directory. Do NOT use for general launch strategy across multiple directories (use /sales-launch-directory), email marketing (use /sales-email-marketing), or audience growth (use /sales-audience-growth).
What this skill does
# Huzzler Platform Help Helps the user with Huzzler platform questions — from submitting a product and competing in the weekly Launch Arena through community engagement, Huzzler Black premium, and maximizing backlink value. ## Step 1 — Gather context If `references/learnings.md` exists, read it first for accumulated knowledge. Ask the user: 1. **What do you need help with?** - A) Launching a product — submitting, writing a listing - B) Winning Launch Arena — competition strategy, getting votes - C) Community engagement — getting feedback, building connections - D) SEO backlinks — getting the dofollow backlink via Launch Arena - E) Huzzler Black — evaluating the $79 premium tier - F) Something else — describe it 2. **What stage is your product?** - A) Idea stage — haven't built anything yet - B) MVP / prototype — working but early - C) Launched — live product with users - D) Growing — looking for more visibility and users 3. **What's your goal?** - A) First users and feedback - B) Community recognition and Launch Arena win - C) SEO backlinks - D) All of the above **If the user's request already provides most of this context, skip directly to the relevant step.** Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end. ## Step 2 — Route or answer directly If the request maps to a specialized skill, route: - Launch strategy across multiple directories → `/sales-launch-directory` - Product launch strategy and funnels → `/sales-funnel` - Email list building / audience growth → `/sales-audience-growth` - Email marketing to subscribers → `/sales-email-marketing` - Landing page / checkout optimization → `/sales-checkout` - Open Launch-specific questions → `/sales-openlaunch` - ProductBurst-specific questions → `/sales-productburst` - MicroLaunch-specific questions → `/sales-microlaunch` - LaunchingNext-specific questions → `/sales-launchingnext` - SideProjectors buy/sell questions → `/sales-sideprojectors` - SoloPush-specific questions → `/sales-solopush` - CtrlAlt.cc-specific questions → `/sales-ctrlaltcc` Otherwise, answer directly from platform knowledge below. ## Step 3 — Huzzler platform reference **Read `references/platform-guide.md`** for detailed module documentation, pricing, integrations, and data model. *You no longer need the platform guide details — focus on the user's specific situation.* ## Step 4 — Actionable guidance ### Launch Arena competition checklist | Step | What to do | Why it matters | |---|---|---| | 1. Submit Mon-Wed | Enter the Launch Arena before Wednesday cutoff | Late submissions get fewer voting days | | 2. Prepare visuals | Logo, screenshots, compelling description | First impression drives votes | | 3. Tell your story | Why you built this, the problem it solves | Huzzler community values founder stories | | 4. Engage in community | Post in #feedback, comment on others' products | Active members get reciprocal support | | 5. Share externally | Post your Launch Arena entry on Twitter, communities | External traffic drives votes | | 6. Respond to feedback | Reply to every comment and question | Shows you're a real, engaged founder | ### Winning Launch Arena The weekly competition format means: - **Smaller field**: ~18 contestants per week (much less competition than Product Hunt) - **Multi-day voting**: Wed-Sun gives you 4+ days to gather votes (vs PH's 24 hours) - **Reciprocity matters**: Engaging with other founders' products builds goodwill and return votes - **Timing**: Submit early in the Mon-Wed window to maximize visibility during submission phase ### When Huzzler Black is worth it **Buy Huzzler Black ($79) when:** - You're launching multiple products and want lifetime visibility for all of them - The verified badge adds credibility to your profile - You want to remove ads from your experience - You're betting on upcoming features (alternatives pages, problem directory) **Skip Huzzler Black when:** - You only need a single Launch Arena entry (free) - The backlink is your primary goal (only winners get it regardless of Black status) - Budget is tight — $79 is more than Open Launch Premium ($12) or CtrlAlt.cc ($39) ### Multi-platform launch strategy Huzzler works best as one platform in a broader launch: 1. **SoloPush + ProductBurst** — instant listings (Day 1) 2. **Huzzler Launch Arena** — submit Monday for weekly competition 3. **Open Launch Premium ($12)** — next-day launch with DR65 backlink 4. **MicroLaunch** — 30-day leaderboard cycle 5. **CtrlAlt.cc + LaunchingNext** — curated directories (queue or pay to skip) 6. **Product Hunt** — save for main launch event ## Gotchas *Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.* - **Backlink is NOT automatic.** This is the most important gotcha. Unlike ProductBurst or SoloPush where every listing gets a dofollow backlink, Huzzler only gives dofollow backlinks to Launch Arena winners (Gold/Silver/Bronze). Regular product listings do not get an external backlink by default. - **DR varies by source.** LaunchDirectories lists DR 41 in one place and DR 47 in another. The difference is not huge but don't rely on exact numbers. - **Small community = small traffic.** 3,382 members and ~2.4K MAU reported. Don't expect significant direct traffic — value is community feedback and potential backlink. - **Weekly competition resets.** If you don't win, your product doesn't get pinned or get the backlink. You can resubmit but competing repeatedly may feel spammy. - **Huzzler Black features are mostly "coming soon."** The $79 buys lifetime visibility and a badge now, but the "alternatives to" pages and problem/solution directory are not yet live. - **AI-free policy is strict.** Don't use AI-generated descriptions or spam. The community actively moderates for AI content. - **No public API.** Everything is manual through the web interface. - **Advertising uses a credit system.** Pricing adjusts based on platform impressions — $34 promoted product, but credit costs may change. - **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date. ## Related skills - `/sales-launch-directory` — Launch strategy across multiple startup directories - `/sales-openlaunch` — Open Launch platform help (open-source PH alternative, DR65 backlinks) - `/sales-firsto` — Firsto platform help (fair launch platform, sustained SEO discovery) - `/sales-ctrlaltcc` — CtrlAlt.cc platform help (curated tool directory) - `/sales-productburst` — ProductBurst platform help (daily/weekly rankings, badges) - `/sales-microlaunch` — MicroLaunch platform help (30-day leaderboard, deals marketplace) - `/sales-launchingnext` — LaunchingNext platform help (curated startup directory) - `/sales-solopush` — SoloPush platform help (indie maker community, no-pressure launch) - `/sales-sideprojectors` — SideProjectors platform help (buy/sell side projects) - `/sales-funnel` — Build and optimize sales funnels for conversion - `/sales-audience-growth` — Grow your email list and subscriber base - `/sales-checkout` — Optimize landing pages and checkout for conversion - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do` ## Examples ### Example 1: Launch a product on Huzzler to win Launch Arena **User says**: "I built a productivity app and want to win Huzzler's Launch Arena this week" **Skill does**: 1. Walks through the competition checklist: submit Mon-Wed, visuals, description, founder story 2. Advises engaging with other contestants' products before voting starts Wednesday 3. Suggests sharing the Launch Arena entry on Twitter and relevant communities Wed-Sun 4. Explains what winners get: 7-day pin, badge, dofollow ba
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".