Visitor ID
Turns website visits into outreach signals. It takes visitors from RB2B or a company-by-IP tool, keeps them in one database and once a week exports a CSV: company, date, the page they read, and queue A or B.
For B2B service companies that run outbound and want to write to people who already read their site. The skill is free. It needs Claude Code, Node.js, Python 3 and a Cloudflare account. Source of visits: RB2B or a company-by-IP tool. The skill clones the Worker code from GitHub itself. ZIP for Claude Code · 3 KB
npx skills add victor-shulga/visitor-id/skills/visitor-idWhat it does
The skill deploys a small Worker with a D1 database to your Cloudflare account. The Worker receives the webhook, stores the visit and answers at once, so RB2B never switches the integration off. Once a week export.py rolls the recent visits into one row per company, with the same columns as the other signals in your prospect list. Then the companies go through the usual stop filters and into the CRM with a «website visit» signal and its date.
Input and output
Key features
- Queue A: looked at pricing, cases, contact or services, or came 3+ times. Write to them this week; the rest waits for a second signal in queue B
- A person with name, title and LinkedIn comes only from RB2B and only for US visitors. In Europe and elsewhere you see the company by office IP
- A visit without a person is accepted too. For such a company you find 2–3 people: the decision maker and a champion
- The CSV columns match the signal block of a prospect list, so a visit sits next to your other signals with no manual copying
- The free RB2B plan posts visits only to Slack. Then Claude reads the channel daily and forwards each visit to the Worker
- The reason for the first message is the topic of the page they read. The visit itself is never mentioned: the visitor does not know they were identified, and saying so burns the contact
What you can really learn
RB2B shows the person: name, title, LinkedIn and company. This works only for US visitors, because it relies on cookies from US ad networks, and outside the US it cannot be repeated technically or legally. Company-by-IP tools work in any country, but they show only the company, and only when the visitor is on an office network. You recognise a person from Europe only if you already know them: by your own link with a ?ref= tag in an email, or by a LinkedIn sign-in on a lead magnet. So for most visits outside the US the skill gives you a company, and you find the people under it yourself.
How to install
Node 18+ required. The command installs the skill into the current project folder:
npx skills add victor-shulga/visitor-id/skills/visitor-idTo keep the skill at hand in every project, add -g:
npx skills add -g victor-shulga/visitor-id/skills/visitor-idIn Claude Code: unzip the folder visitor-id into ~/.claude/skills/ and restart the app. The folder is hidden: on Mac press Cmd+Shift+G in Finder and paste ~/.claude/skills/, on Windows open %USERPROFILE%\.claude\skills. The skill runs only in Claude Code: it deploys the Worker with wrangler and runs Python. Then type /visitor-id in Claude Code: the skill clones the code, runs the tests and walks you through the deploy. You type the webhook secret yourself; it never goes into the chat.
Download the ZIP · 3 KBOpen the skill's folder on GitHub and save the files. The main file is SKILL.md, and the rest is pulled in from it.
Check it works: type /visitor-id in the chat — the skill should answer. If it does not: skills are read at session start, so restart Claude.