sales-rb2b
RB2B platform help — Person-Level Website Visitor ID, Company-Level ID, Hot Pages, Hot Leads, Traffic Insights, Identity Resolution API, integrations. Use when you know companies visit your site but not which people, the RB2B pixel isn't identifying visitors, you need person-level ID not just company-level, Hot Pages aren't flagging high-intent visits, or you're comparing RB2B vs Clearbit Reveal for visitor identification. Do NOT use for visitor identification strategy across tools (use /sales-intent), enrichment strategy across tools (use /sales-enrich), building prospect lists across tools (use /sales-prospect-list), or lead scoring strategy (use /sales-lead-score).
What this skill does
# RB2B Platform Help
Help the user with RB2B platform questions — Person-Level Website Visitor ID, Company-Level ID, Hot Pages, Hot Leads, Traffic Insights, Identity Resolution API, and integrations.
**Important context**: RB2B offers **person-level** visitor identification (US traffic only) — it identifies the individual visiting your site, not just the company. This is the key differentiator vs Clearbit Reveal, Leadfeeder, and other company-level-only tools. Company-level ID is powered by Demandbase and works globally.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated knowledge.
**What area of RB2B do you need help with?**
- a) Person-Level ID — identify individual visitors by name, email, LinkedIn
- b) Company-Level ID — identify companies visiting your site
- c) Hot Pages — flag high-intent page visits
- d) Hot Leads — filter visitors by firmographic/demographic criteria
- e) Traffic Insights — dashboard analytics on visitor activity
- f) Identity Resolution API — programmatic access to RB2B's data
- g) Integrations — connect RB2B to CRM, Slack, or other tools
- h) Pixel setup and installation
- i) Something else
**What's your primary use case?**
- a) Alert sales when target accounts or people visit the site
- b) Enrich anonymous traffic with contact data for outbound
- c) Build retargeting audiences from identified visitors
- d) Score and route leads based on website behavior
- e) API-based identity resolution for my own app
- f) Compare RB2B to other visitor ID tools
**What's your current stack?**
- a) HubSpot
- b) Salesforce
- c) Other CRM (Pipedrive, Close, etc.)
- d) Slack-only (no CRM)
- e) Custom app / API-only
## Step 2 — Route or answer directly
If the question is about **visitor identification strategy across tools** (not RB2B-specific) — hand off: "This is an intent signal strategy question — run: `/sales-intent {user's original question}`"
If the question is about **enrichment strategy across tools** — hand off: "This is an enrichment strategy question — run: `/sales-enrich {user's original question}`"
If the question is about **building prospect lists across tools** — hand off: "This is a prospect list building question — run: `/sales-prospect-list {user's original question}`"
If the question is about **lead scoring model design** — hand off: "This is a lead scoring strategy question — run: `/sales-lead-score {user's original question}`"
If the question is about **connecting RB2B to other tools** — hand off: "This is a tool integration question — run: `/sales-integration {user's original question}`"
Otherwise, answer directly using the reference below.
## Step 3 — RB2B 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
### Setting up RB2B pixel
1. **Sign up** at rb2b.com and choose a plan
2. **Copy the pixel snippet** from your RB2B dashboard (Settings → Pixel)
3. **Add to your website** — paste in the `<head>` tag of every page (or use Google Tag Manager)
4. **Verify installation** — visit your own site and check the RB2B dashboard for the visit
5. **Configure Hot Pages** — mark your pricing, demo, and comparison pages as high-intent
6. **Set up Slack alerts** — connect Slack and choose a channel for visitor notifications
7. **Connect CRM** — push identified visitors to HubSpot or Salesforce
### Optimizing match rates
1. **Focus on US traffic** — person-level ID only works for US visitors; ensure your marketing drives US traffic if person-level ID is your goal
2. **Upgrade to Pro+** — 35-45% person-level coverage vs lower rates on other plans
3. **Use Hot Pages** — even if you can't ID everyone, Hot Pages ensures you catch high-intent visitors
4. **Combine with outbound** — use RB2B-identified visitors as warm leads for outbound sequences (they've already shown intent)
### RB2B + outbound workflow
1. **RB2B identifies visitor** on pricing page → pushes to Slack + CRM
2. **Sales rep reviews** the visitor's LinkedIn profile and company
3. **If ICP match** → add to outbound sequence in Apollo/Salesloft/Outreach
4. **Personalize outreach** — reference the specific page they visited ("I noticed you were looking at our enterprise pricing...")
5. **Time the outreach** — reach out within 24 hours of the visit for highest conversion
## Gotchas
*Best-effort from research — review these, especially items about plan-gated features and coverage rates that may be outdated.*
- **Person-level ID is US-only**: RB2B cannot identify individual visitors outside the US. If your audience is primarily international, you'll only get company-level data (powered by Demandbase). This is a hard compliance limitation, not a feature gap.
- **Free plan is company-level only**: The Free plan (150 resolutions) does NOT include person-level identification. You need a paid plan (Starter or above) for person-level ID. Don't assume the free trial shows person-level capabilities.
- **API is a separate product**: The Identity Resolution API at api.rb2b.com has its own credit-based pricing, completely separate from the pixel product pricing. Don't confuse pixel plan limits with API credits.
- **Match rates vary significantly**: The 35-45% person-level match rate is for Pro+ plans with sufficient US traffic. Lower plans and sites with more international/mobile/VPN traffic will see much lower rates. Set expectations accordingly.
- **Pixel requires JavaScript**: The RB2B pixel is a JavaScript snippet. It won't work on server-rendered pages that don't execute client-side JS, email tracking pixels, or native mobile apps. For those use cases, use the API product instead.
- **Self-improving**: If you discover something not covered here, append it to `references/learnings.md` with today's date.
## Step 5 — Related skills
- `/sales-intent` — Buying signals and visitor identification strategy across tools (RB2B is one option for visitor ID)
- `/sales-enrich` — Enrichment strategy across tools (RB2B API provides identity resolution)
- `/sales-prospect-list` — Build prospect lists from identified visitors and other sources
- `/sales-lead-score` — Score leads using RB2B visitor data + other signals
- `/sales-integration` — Connect RB2B to CRM, Slack, and other tools
- `/sales-clearbit` — Clearbit/Breeze Intelligence (competitor for company-level visitor ID via Reveal)
- `/sales-customersai` — Customers.ai platform help (B2C ecommerce visitor ID for Shopify + Klaviyo — different market than RB2B's B2B focus)
- `/sales-cadence` — Design outbound sequences for RB2B-identified visitors
- `/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: Set up person-level visitor identification
**User says**: "I want to know exactly who is visiting our pricing page so my SDRs can follow up — how do I set up RB2B?"
**Skill does**: Walks through pixel installation, Hot Pages configuration for the pricing page, Slack alert setup, explains person-level ID is US-only with 35-45% match rate on Pro+, recommends connecting to CRM for automatic lead creation, and suggests a follow-up workflow where SDRs reach out within 24 hours referencing the specific page visited
**Result**: Sales team gets real-time Slack alerts with visitor name, email, LinkedIn, and company when someone hits the pricing page
### Example 2: RB2B vs Clearbit Reveal comparison
**User says**: "We're currently using Clearbit Reveal for website visitor identification — should we switch to RB2B?"
**Skill does**: Compares person-level (RB2B) vs company-level only (Clearbit Reveal), explains RB2B's US-only limitation vs Reveal's global coverage, discusses pricing differences (RB2B $79-199/mo vs Clearbit credit-based), notes that ClearbiRelated 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.