sales-betalist
BetaList platform help — pre-launch startup discovery directory where early adopters find startups before they make it big (15,000+ featured startups, 100K+ early adopters, DR67 dofollow backlink). Covers submission optimization, acceptance criteria (21% acceptance rate), free queue vs $129 Priority listing, newsletter inclusion (30K+ subscribers), listing best practices, and API access. Use when your startup needs early adopter signups, BetaList submission got rejected, not sure if Priority listing is worth $129, or listing isn't attracting enough interest. Do NOT use for multi-directory launch strategy (use /sales-launch-directory). Do NOT use for Product Hunt (use /sales-producthunt).
What this skill does
# BetaList Platform Help
Helps with everything related to using BetaList — a pre-launch startup discovery platform founded in 2010 by Marc Kohlbrugge. BetaList connects founders with 100,000+ registered early adopters who actively seek new products to try before mainstream launch.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated knowledge.
Ask the user:
1. **What are you trying to do on BetaList?**
- A) Submit my startup for the first time
- B) Optimize an existing or upcoming listing
- C) Decide between free queue and Priority ($129)
- D) Understand why my submission was rejected
- E) Access the BetaList API
- F) Something else — describe it
2. **What stage is your product?**
- A) Pre-launch — no public access yet (private beta, waitlist)
- B) Recently launched — live but early stage
- C) Established — been live for a while
- D) Not sure if BetaList is the right fit
3. **What's your primary goal?**
- A) Get beta testers and early feedback
- B) SEO backlink (DR67 dofollow)
- C) Newsletter exposure (30K+ subscribers)
- 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 different skill, route:
- Multi-directory launch strategy → `/sales-launch-directory`
- Product Hunt launch → `/sales-producthunt`
- General audience growth → `/sales-audience-growth`
- Email marketing for subscribers → `/sales-email-marketing`
- Landing page optimization → `/sales-checkout`
Otherwise, answer directly from the platform knowledge below.
## Step 3 — BetaList platform reference
**Read `references/platform-guide.md`** for detailed directory documentation, pricing, acceptance criteria, and backlink value.
*You no longer need the platform guide details — focus on the user's specific situation.*
## Step 4 — Actionable guidance
### Optimizing your BetaList submission
| Element | Best practice |
|---|---|
| Tagline | Lead with the problem you solve, under 60 chars. "Find leads who visit your website" > "AI-powered B2B lead generation platform" |
| Description | Focus on what makes you different, not feature lists. Address: What problem? For whom? Why now? |
| Screenshots | Show the product in action — real UI, not marketing graphics. Include at least one GIF showing core workflow |
| Thumbnail GIF | Add one animated GIF as thumbnail — it stands out in the directory. Use brand colors, not white background. Ideal size: 800x600px (displayed at 400x300px) |
| URL | Working landing page with clear CTA (signup, waitlist, beta access). Must be your own domain |
| Category | Pick the most specific category that fits — BetaList shows category pages |
### Free queue vs Priority ($129) decision
**Pay for Priority when:**
- You're coordinating a multi-platform launch and need timing control
- You're pre-launch with a narrow beta window — 2 months is too long
- The $129 is worth it for the guaranteed newsletter exposure
- You want the DR67 backlink NOW, not in 2 months
**Stay in the free queue when:**
- No timing pressure — you're playing the long game
- Budget is tight and you can wait
- You're submitting to many directories and BetaList is just one of them
- You want to use the queue time to refine your product
**ROI math:** BetaList typically delivers 200-500 visitors with 15-20% conversion rates. At $129 Priority: $0.50-$1.40 per signup. Free queue: $0 per signup but 2+ month delay.
### Maximizing results after featuring
1. **Be ready on launch day** — your listing is live for 24 hours on the homepage. Have your landing page, onboarding, and support ready
2. **Respond to feedback** — early adopters who find you via BetaList are genuinely interested in trying new things. Engage with them
3. **Track with UTMs** — add `?utm_source=betalist&utm_medium=directory&utm_campaign=launch` to your submitted URL
4. **Don't waste the newsletter slot** — the daily newsletter reaches 30K+ subscribers. Your tagline and thumbnail are what drive clicks
### Improving a rejected submission
Since BetaList doesn't provide rejection reasons, work through this checklist:
1. **Landing page quality** — is the design professional? Does it load fast? Is the CTA obvious?
2. **Value proposition** — can a stranger understand what you do in 5 seconds?
3. **Uniqueness** — how is this different from existing solutions?
4. **Stage** — are you genuinely pre-launch or recently launched? Established products get rejected
5. **Domain** — are you on your own domain (not a subdomain of a hosting provider)?
6. **Previous launches** — have you already launched on Product Hunt? BetaList prefers exclusivity
## Gotchas
*Best-effort from research — review these, especially items about pricing and acceptance criteria that may be outdated.*
- **21% acceptance rate.** BetaList is selective — most submissions get rejected. Don't submit until your landing page is polished and your value proposition is crystal clear.
- **No rejection feedback.** If rejected, you won't know why. Use the checklist above to diagnose and improve, then resubmit.
- **Audience has shifted.** BetaList's audience skewed toward makers/builders after its 2011-2016 "golden era." Set expectations: you'll get early adopters who are often founders themselves, not mainstream consumers.
- **Queue time varies.** "~2 months" is typical but can be shorter or longer depending on submission volume.
- **$129 is non-refundable if accepted.** Only rejected Priority submissions get refunds. Once featured, no refunds regardless of results.
- **One shot per submission.** Each submission is reviewed independently. If rejected, improve and resubmit as a new submission.
- **Exclusivity preference.** BetaList favors products that haven't launched on other major platforms. If you've already done a Product Hunt launch, your chances decrease.
- **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date.
## Related skills
- `/sales-launch-directory` — Multi-directory launch strategy across 30+ platforms (sequencing, backlink stacking, budget allocation)
- `/sales-producthunt` — Product Hunt platform help (largest launch platform, DR91 dofollow)
- `/sales-audience-growth` — Grow your email list and subscriber base
- `/sales-checkout` — Optimize your landing page for conversion before submitting
- `/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: Submit a SaaS tool to BetaList
**User says**: "I built a project management tool for remote teams and want to submit to BetaList"
**Skill does**:
1. Confirms product is pre-launch or recently launched (meets stage requirement)
2. Reviews landing page against acceptance criteria: value proposition clarity, design quality, own domain
3. Recommends tagline optimization: lead with the problem ("Remote teams lose 5 hours/week to status meetings") not the solution
4. Advises adding a product GIF as thumbnail with brand colors, 800x600px
5. Discusses free queue (~2 months) vs Priority ($129) based on their timing needs
**Result**: Optimized submission with clear value proposition, strong visuals, and informed queue/Priority decision
### Example 2: Decide whether $129 Priority is worth it
**User says**: "Should I pay $129 for BetaList Priority or just wait in the free queue?"
**Skill does**:
1. Asks about timing constraints and multi-platform launch coordination
2. Presents ROI math: 200-500 visitors at 15-20% conversion = 30-100 signups for $129
3. Compares to alternatives: waiting 2 months (free) vs guaranteed newsletter exposure (paid)
4. Recommends PriRelated in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.