Website Visitor Identification
Design website visitor identification and deanonymization programs — company vs person-level ID, vendor selection (Clearbit/Breeze, RB2B, 6sense, etc.), privacy guardrails (GDPR/CCPA operational), Slack alert triage, and ICP routing to MQL or outbound triggers. Use when implementing visitor ID, reverse-IP reveal, intent data, or person-level LinkedIn visitor tracking. Triggers on: "visitor identification", "deanonymization", "website intent", "Clearbit Reveal", "RB2B", "who visited our website", "reverse IP", "WebSights", "Leadfeeder", "visitor ID privacy".
Install
/plugin marketplace add LeadMagic/gtm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add LeadMagic/gtm-skills --skill website-visitor-identificationgit clone --depth 1 https://github.com/LeadMagic/gtm-skills.git /tmp/gtm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/gtm-skills/skills/inbound/website-visitor-identification ~/.claude/skills/website-visitor-identificationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Website Visitor Identification ## Overview Most B2B sites convert 2–3% of traffic to forms — the rest looks like dark traffic. Visitor identification (deanonymization) recovers **company** or **person** signals from anonymous sessions. The mistake: buying RB2B or 6sense before deciding identification **level**, running person-level ID on EU traffic without privacy review, or routing every alert to SDRs without an ICP filter. This skill is the **canonical home** for visitor ID strategy: person vs business decision tree, vendor comparison (Clearbit/Breeze, RB2B, 6sense, Demandbase, ZoomInfo WebSights, Leadfeeder/Dealfront, Warmly, Koala, Factors.ai, Albacross), privacy operational checklist (not legal advice), and GTM workflows from website visit → MQL or guardrailed outbound trigger. ## Frameworks Referenced - **HubSpot Breeze Intelligence (Clearbit heritage).** Company Reveal on visit; form enrichment for person + firmographics in HubSpot-native stacks. - **Dharmesh Shah (HubSpot).** Visitor ID instruments the **Attract** stage of the inbound flywheel — permission-based follow-up after self-directed research. `references/dharmesh-shah-hubspot-inbound.md` · Pattern 20 + 27. - **Chris Walker (Refine Labs).** Visitor ID is the **measurable** counterpart to dark social — pair with `content-marketing` and `attribution`, not replace them. Pattern 26 + 20. - **Scott Brinker — MarTech consolidation.** One company-ID owner + at most one
Details
- Skill name
website-visitor-identification- Repository
- LeadMagic/gtm-skills
- Path
skills/inbound/website-visitor-identification/SKILL.md- License
- MIT
- Repo updated
- 14 October 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the Website Visitor Identification skill do?
Design website visitor identification and deanonymization programs — company vs person-level ID, vendor selection (Clearbit/Breeze, RB2B, 6sense, etc.), privacy guardrails (GDPR/CCPA operational), Slack alert triage, and ICP routing to MQL or outbound triggers. Use when implementing visitor ID, reverse-IP reveal, intent data, or person-level LinkedIn visitor tracking. Triggers on: "visitor identification", "deanonymization", "website intent", "Clearbit Reveal", "RB2B", "who visited our website", "reverse IP", "WebSights", "Leadfeeder", "visitor ID privacy".
How do I install the Website Visitor Identification skill?
Claude Code plugin: /plugin marketplace add LeadMagic/gtm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Website Visitor Identification popular?
It lives in LeadMagic/gtm-skills, which has 79 GitHub stars and 18 forks, and is included in 1 curated skill list.
Related skills
1p Tagging Pixels
79LeadMagic/gtm-skills
Set up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side tagging vs client-side, 1P vs 3P data strategy, and identity resolution. Use when setting up tracking, implementing pixels, building attribution, or preparing for privacy-first measurement. Triggers on: "pixel", "tracking", "conversion tracking", "first-party data", "server-side tagging", "UTM", "cookie consent", "1P vs 3P", "identity resolution", or any tracking implementation request.
A B Testing
79LeadMagic/gtm-skills
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
Abm 1 to 1
79LeadMagic/gtm-skills
Runs strategic 1-to-1 ABM for 5-15 high-value accounts: account plans, custom microsites, executive engagement, direct mail, and board-level connections. Use when a named enterprise account justifies bespoke content and executive time, or when the user needs a strategic account plan. Triggers on: "1-to-1 ABM", "strategic ABM", "custom ABM", "key account marketing", "named account".
Dfx Analyze
49hw-native-sys/simpler
Analyze an onboard run's performance/scheduling/dependency/dump data using simpler's BUILT-IN DFX tools (simpler_setup.tools.*) instead of hand-rolling instrumentation. Use AFTER an onboard run when you need per-run device timing (Total/Orch/Sched), AICPU scheduler-overhead / Tail-OH breakdown, the task dependency graph, scope ring-fill peaks, or to inspect args dumps. These are simpler's own tools (shipped in the wheel), distinct from any cross-repo workload. Reach for this before writing custom timing/logging into the runtime.
Social Media Strategy
79LeadMagic/gtm-skills
Build and execute social media strategy for B2B — LinkedIn, X/Twitter, posting cadence, engagement tactics, content formats, sizing guides, and platform-specific best practices. Use when building social presence, planning content, or optimizing engagement. Triggers on: "social media", "LinkedIn strategy", "Twitter strategy", "X strategy", "posting guide", "social content", "engagement", "content calendar", "image sizes", "social graphics", or any social media planning request.
File Bug
49lllyys/vreader
Create a GitHub issue for a bug row in docs/bugs.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing bug row, or asks 'create issue for bug #N', 'file bug 115', 'mirror bug 42 to GH', 'this bug needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/bugs.md` row because it lacks `GH: #N`. Stays strictly in the mirror-an-existing-row scope — do not use for triaging new bugs (that's the triage skill) or fixing bugs (that's fix-issue).
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.