top-market-beaters

web.dubapp.com/get-top-market-beaters-38pq0g · updated May 21, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$browse install web.dubapp.com/get-top-market-beaters-38pq0g
0 commentsdiscussion
summary

Return Dub's Top Market Beaters leaderboard — the 20 Core-creator portfolios currently outperforming the market — with rank, name, ticker, creator, today and all-time % returns, description, and profile URL. Single anonymous HTTP GET to /explore/market-beaters returns the fully SSR'd grid; no auth, no proxy, no JS execution required.

skill.md
name
top-market-beaters
title
Dub Top Market Beaters (Core Creators)
description
>- Return Dub's Top Market Beaters leaderboard — the 20 Core-creator portfolios currently outperforming the market — with rank, name, ticker, creator, today and all-time % returns, description, and profile URL. Single anonymous HTTP GET to /explore/market-beaters returns the fully SSR'd grid; no auth, no proxy, no JS execution required.
website
web.dubapp.com
category
investing
tags
- copy-trading - leaderboard - investing - dub - core-creators - read-only
source
'browserbase: agent-runtime 2026-05-18'
updated
'2026-05-18'
recommended_method
api
alternative_methods
- method: url-param rationale: >- The Core vs Premium variant is path-based (/explore/market-beaters for Core, /explore/premium/market-beaters for Premium). Query-string ?type= is silently ignored on /explore/market-beaters but does work on /leaderboard. - method: browser rationale: >- Unnecessary — the SSR'd HTML already contains every card and field. Browser path is identical to HTTP path in extractable data but ~100× the cost. Only justified if Dub adds an anti-bot wall to the HTML route in the future (none observed across 3 fetches: 200 OK with and without proxies).
verified
false
proxies
false

Dub Top Market Beaters (Core Creators)

Purpose

Return the current Top Market Beaters leaderboard from Dub's Core Creators on web.dubapp.com — the curated list of Core portfolios that are outperforming the market. For each ranked portfolio: name, ticker, creator display name, today's % return, all-time % return, short strategy description, and canonical profile URL. Read-only; never copies, follows, or invests.

When to Use

  • Daily / hourly tracking of which Core creator portfolios are leading the market on Dub.
  • Building dashboards or alerts on top-performing copy-trading portfolios.
  • Comparing Core (free-to-copy, curated) vs. Premium (paid) leaderboards on Dub.
  • Any agent task that says "top creators / top portfolios / market beaters on Dub" — that exact phrase is a literal h2 section heading on /explore.

Workflow

The full leaderboard is fully server-side rendered in the HTML returned by a single anonymous HTTP GET to a stable, public URL. No JavaScript execution, no login, no proxy, no captcha, no ?type= toggle parsing — just GET → parse HTML. Sub-second, ~$0.0001 per fetch via Browserbase Fetch. Lead with the HTTP path; the browser flow is an unnecessary 100× cost wrapper around the same SSR'd payload.

  1. Fetch the page (Core Creators):

    GET https://web.dubapp.com/explore/market-beaters
    

    For Premium creators use GET https://web.dubapp.com/explore/premium/market-beaters (returns the analogous 20-card grid with title Top Market Beaters - Premium). The query-string form ?type=premium is silently ignored on this URL — the Core vs Premium toggle is path-based, not param-based.

    Headers: none required. No Referer, no User-Agent, no Cookie. The page returns 200 OK with the full grid SSR'd into the HTML.

  2. Confirm the page rendered. Sanity-check by looking for the canonical h1 in the response body:

    <h1 class="... font-serif text-display-lg">Top Market Beaters</h1>
    

    and the subtitle <p>Portfolios outperforming the market</p>. If the h1 is missing, you were probably redirected (e.g. AppsFlyer smart-banner injecting JS); refetch.

  3. Split the grid into card chunks. Each portfolio card begins with the literal anchor open-tag:

    <a class="flex h-full w-full" href="/portfolios/{HANDLE}">
    

    Splitting the HTML on <a class="flex h-full w-full" href="/portfolios/ yields one chunk per card. The page renders exactly 20 cards on a single page (no pagination, no infinite scroll, no "See more" — /explore/market-beaters is the canonical full list as of the trace). Order is by rank: index 0 = rank 1.

  4. Extract fields per card chunk (regex against each chunk):

    FieldSource
    handle (portfolio ticker, uppercase)The leading capture ([A-Za-z0-9_]+) immediately after the split delimiter
    name (portfolio display name)<p class="truncate text-md font-semibold text-primary">([^<]+)</p>
    ticker<span class="font-mono ... text-action">\$<!-- -->([A-Z0-9_]+)</span> — note the literal <!-- --> comment node Next.js injects between $ and the value
    creator (display name)<span class="truncate text-secondary">([^<]+)</span> — the first such span after the · separator. May be a first-name + last-initial (e.g. John P.), a single name (Jeremy, Seb), or an org/handle (APMIA, Hugh Mungus)
    today_return_pct>Today<.*?<span ... text-(gain|loss|primary)[^"]*>([+-]?\d+\.\d+%)</span> (DOTALL)
    all_time_return_pct>All-Time<.*?<span ... text-(gain|loss|primary)[^"]*>([+-]?\d+\.\d+%)</span> (DOTALL)
    description<p class="line-clamp-\d ... text-secondary ...">([^<]+)</p> — HTML-decode &quot;, &amp;, &#x27;, &#39;, Unicode entities (')
    profile_urlhttps://web.dubapp.com/portfolios/{handle}
  5. Sort sanity-check: the page is ranked by all-time return, with rank 1 being the highest. Rank-1's all_time_return_pct should be the largest positive value among the 20 cards. The marketing copy ("Portfolios outperforming the market") means all 20 entries are alpha-positive over the lifetime window — but today_return_pct can be deeply negative on a market-wide red day and that's expected (the page does not re-rank intraday).

  6. Stamp as_of with the current UTC date — the page itself does not include a server-side "last updated" timestamp. Cache-Control on the response is private, no-cache, no-store, max-age=0, must-revalidate, so each fetch is freshly regenerated server-side.

Browser fallback

Only justified if Dub introduces a future anti-bot wall on the HTTP path (none observed). If needed:

browse open https://web.dubapp.com/explore/market-beaters --remote
browse wait load
browse get html body          # returns the same SSR'd HTML as the HTTP fetch
# parse with the same regexes from step 4 — the browser does not unlock any
# additional fields, it just adds cost and turn count

Do not click any portfolio card during fallback — the portfolio detail page is not needed for the leaderboard task, and a stray click on the rendered "Copy" or "Invest" button is a real-money action surface (dub is a SEC-registered broker-dealer; this is a real trading app, not a paper demo).

Site-Specific Gotchas

  • No anti-bot wall observed. Verified by 2 successive fetches with proxies: true and 1 fetch with proxies: false — all 3 returned 200 OK with the identical 20-card payload in the same rank order. proxies are not required for this endpoint. Default to omitting --proxies to save ~$0.0008 per fetch.
  • The phrase "Top Market Beaters" is a literal h2 section heading on multiple pages. Disambiguate by URL: /explore shows a 3-card carousel preview of Top Market Beaters with a "See all" link pointing to /explore/market-beaters; the latter is the full 20-card grid. The carousel on /explore only contains 3 cards in SSR — don't scrape it directly, follow the "See all" link.
  • Core vs Premium routing is path-based, not param-based. /explore/market-beaters is Core (free copy-trading creators). /explore/premium/market-beaters is Premium (paid creators — Pelosi, Buffett, Infinity, etc.). The query-string ?type=premium is silently ignored on /explore/market-beaters (page title stays "Top Market Beaters", not "...- Premium"). The ?type=core|premium toggle only works on /leaderboard, not on /explore.
  • Don't confuse /leaderboard with /explore/market-beaters. They are different surfaces with different data:
    • /leaderboard?type=core has three tables (Highest Returns, Most Copiers, Most Copying Capital), 9 rows each, with three time-window tabs (All Time / Monthly / Today). Only the active tab (All Time by default) is SSR'd — the Monthly and Today panels exist in the DOM but their <div> body is empty until a client-side fetch fires on tab click. There is no observed URL param that selects a different default tab — tested ?window=, ?period=, ?tab=, ?time= (all monthly/today empty).
    • /explore/market-beaters is the dedicated "Top Market Beaters" page — 20 cards, no tabs, no time-window switcher. Today's % and All-Time % are both shown on every card.
  • Next.js <!-- --> comment nodes inside spans break naïve regex. The ticker is rendered as <span ...>$<!-- -->JOHNDPHAN</span>, not <span ...>$JOHNDPHAN</span>. Always include <!--\s*--> in your ticker regex or use a tolerant capture (\$\s*(?:<!--[^>]*-->)?\s*([A-Z0-9_]+)).
  • Creator handle may be missing on some leaderboard rows. On /leaderboard?type=core, the row for portfolios without a public creator @username (e.g. $NUKEFUTURE) has no @username span at all — it shows only the portfolio name and ticker. On /explore/market-beaters, every card has a creator field (display name), but format varies: first-name + last-initial (John P.), single name (Jeremy, Seb, APMIA), or full alias (Hugh Mungus). Don't assume a @handle pattern.
  • Image srcSet payloads are huge (~30% of HTML weight) — the cards include 12-width responsive srcSet URLs each ~3KB. Strip <img ... srcSet="..."/> before regex-extracting fields to make parsing 3× faster, or just regex against the original HTML — both work, the latter is fine for 20-card pages.
  • Cache-Control is no-store. Every fetch hits the origin (X-Vercel-Cache: MISS). Don't rate-limit yourself based on cache-hit assumptions — but also don't hammer: sustained ≤ 1 req/s is polite for a leaderboard that updates intraday at most.
  • Sandbox WebSocket egress note (skill-build environment, not skill-runtime): the Browserbase remote-browser path (connect.usw2.browserbase.com WebSocket) is not reachable from the Vercel Sandbox host that built this skill — only the Browserbase REST API (api.browserbase.com) was reachable. That's why this skill was verified end-to-end via POST /v1/fetch rather than browse open --remote. For agents consuming this skill from environments with full network egress, both paths work; the HTTP path is still strictly preferred for cost.
  • dub is a regulated SEC-registered broker-dealer. Treat any clickable button on a portfolio detail page as a potential trade-execution surface. The leaderboard extraction itself touches no execution surface — but during browser fallback, scope to read-only verbs (get html, screenshot, snapshot) and never click a portfolio card.

Expected Output

{
  "success": true,
  "page_url": "https://web.dubapp.com/explore/market-beaters",
  "section": "Top Market Beaters",
  "subtitle": "Portfolios outperforming the market",
  "creator_type": "core",
  "as_of": "2026-05-18T00:00:00Z",
  "card_count": 20,
  "cards": [
    {
      "rank": 1,
      "name": "johndinhphan",
      "ticker": "$JOHNDPHAN",
      "handle": "JOHNDPHAN",
      "creator": "John P.",
      "today_return_pct": "-5.30%",
      "all_time_return_pct": "+543.22%",
      "description": "I find value where others overlook it - safe, growing, and built to last. One year is all it takes.",
      "profile_url": "https://web.dubapp.com/portfolios/JOHNDPHAN"
    },
    {
      "rank": 2,
      "name": "Copy The Cat",
      "ticker": "$COPYDACAT",
      "handle": "COPYDACAT",
      "creator": "Carlos C.",
      "today_return_pct": "-6.54%",
      "all_time_return_pct": "+147.61%",
      "description": "\"Copy the Cat\" monitors the moves of the most successful institutional investors to identify elite starting points for our analysis...",
      "profile_url": "https://web.dubapp.com/portfolios/COPYDACAT"
    }
  ]
}

For the Premium-creator variant, set creator_type: "premium" and page_url: "https://web.dubapp.com/explore/premium/market-beaters" (also 20 cards, same schema).

Failure shapes (rare — only if the HTTP fetch itself fails):

{ "success": false, "reason": "fetch_failed", "status_code": 5xx }
{ "success": false, "reason": "card_grid_missing", "note": "h1 'Top Market Beaters' present but 0 cards parsed — possible markup migration; refetch and inspect the leading anchor pattern" }
how to use top-market-beaters

How to use top-market-beaters on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add top-market-beaters
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$browse install web.dubapp.com/get-top-market-beaters-38pq0g

The skills CLI fetches top-market-beaters from GitHub repository web.dubapp.com/get-top-market-beaters-38pq0g and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/top-market-beaters

Reload or restart Cursor to activate top-market-beaters. Access the skill through slash commands (e.g., /top-market-beaters) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.736 reviews
  • Aanya Mehta· Dec 28, 2024

    top-market-beaters is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Pratham Ware· Dec 24, 2024

    top-market-beaters fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Diego Patel· Dec 16, 2024

    top-market-beaters reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Diego Gupta· Dec 8, 2024

    We added top-market-beaters from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Meera Smith· Nov 19, 2024

    Solid pick for teams standardizing on skills: top-market-beaters is focused, and the summary matches what you get after install.

  • Ava Martinez· Nov 7, 2024

    I recommend top-market-beaters for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Anaya Khanna· Oct 26, 2024

    Useful defaults in top-market-beaters — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Meera Mehta· Oct 10, 2024

    top-market-beaters has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Evelyn Smith· Sep 21, 2024

    Useful defaults in top-market-beaters — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Aditi Huang· Sep 9, 2024

    We added top-market-beaters from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 36

1 / 4