handle-linkedin-profile-view-signal

handle-linkedin-profile-view-signal is a skill for Claude Code, Codex from swan-gtm/gtm-skills. It costs 98 tokens per session (3,172 once invoked), scanned A, original, MIT.

A workflow for handling notifications that someone viewed a team member's LinkedIn profile. It identifies the viewer and company, removes duplicates, checks internal and relationship rules, and routes qualifying viewers into a marketing-lead process.

In plain words
What is it for?
Use it to process LinkedIn profile-view webhooks, enrich and qualify viewers, apply scoring limits and cooldowns, update a CRM, and send outcome or debugging notifications.
Why use it?
It prevents every profile view from being treated as a sales lead and avoids duplicate or inappropriate follow-up. It also distinguishes existing relationships and internal viewers from new potential prospects.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to process LinkedIn profile-view webhooks, enrich and qualify viewers, apply scoring limits and cooldowns, update a CRM, and send outcome or debugging notifications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swan-gtm/gtm-skills/handle-linkedin-profile-view-signal
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add swan-gtm/gtm-skills --skill handle-linkedin-profile-view-signal
Clone the repo
git clone --depth 1 https://github.com/swan-gtm/gtm-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for handle-linkedin-profile-view-signal

README.md
[![agentmods](https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/handle-linkedin-profile-view-signal/github.svg)](https://agentmods.dev/skills/swan-gtm/gtm-skills/handle-linkedin-profile-view-signal)
Your own site
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/handle-linkedin-profile-view-signal"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/handle-linkedin-profile-view-signal/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for handle-linkedin-profile-view-signal

Your own site · 80×15
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/handle-linkedin-profile-view-signal"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/handle-linkedin-profile-view-signal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,172 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00098 $0.03172
Opus 5 $0.00049 $0.01586
Sonnet 5 $0.00020 $0.00634
Haiku 4.5 $0.00010 $0.00317

Measured 13d ago against content hash 8e28a15569a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

handle-linkedin-profile-view-signal scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/ariel-cohen/handle-linkedin-profile-view-signal/SKILL.md · 301 lines

How it starts

The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Template placeholders

Replace every {{...}} before enabling. See the setup checklist reference for the full setup list.

  • {{PROFILE_OWNER}} — Full name of the team member whose LinkedIn is tracked (e.g. "Jane Doe")
  • {{INTERNAL_DOMAINS}} — Your own company domain(s) (e.g. "acme.com")
  • {{NOTIFICATIONS_CHANNEL}} — Slack channel reference for outcome/debug posts
  • {{ENRICHMENT_TOOL}} — Primary contact-enrichment tool available to the agent
  • {{FALLBACK_SCRAPER}} — Fallback LinkedIn profile scraper (e.g. an Apify actor)
  • {{CRM}} — Your CRM (e.g. HubSpot)
  • {{CRM_HYGIENE_SKILL}} — Sub-skill reference: how to create/update companies & contacts in your CRM
  • {{EXISTING_RELATIONSHIP_SKILL}} — Sub-skill reference: handling accounts with an open/lost deal
  • {{HIGH_INTENT_SKILL}} — Sub-skill reference: potential-MQL scoring & routing
  • {{AWARENESS_SKILL}} — Sub-skill reference: net-new ICP awareness logging
  • {{TIER_SCALE}} — Your lead-score tiers, low→high (default: Bronze / Silver / Gold / Diamond)
  • {{SOLE_SIGNAL_CAP_TIER}} — Max tier when a profile view is the only 1st-party signal (default: Silver)
  • {{COOLDOWN_WINDOW}} — Same-session dedup window (default: 1 hour)

Overview

This skill fires when your profile-view tracker (e.g. LeadShark) detects a new view on {{PROFILE_OWNER}}'s LinkedIn profile. Goal: behave exactly like a website visit — resolve the viewer, run the same ICP gate, register them as a known contact only when they pass, and feed them into the MQL pipeline.

The golden rule: the CRM is never polluted. Only a viewer who is identified + company-resolved + not-internal + not-customer + ICP-matched ever reaches a CRM write. Everyone else is silently discarded or logged to org memory only.

The webhook trigger handles only one thing: ignoring events that are not new.profile.visit. All logic lives here.

Channel rule: When outreach is triggered by a LinkedIn profile view signal, keep it LinkedIn-only. Do not create email steps. The contact came to you via LinkedIn — stay on that channel.

Read the full file on GitHub · 301 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 301 lines · 98 tokens per session scan A 8e28a15569a4

Subscribe to this mod's changes

handle-linkedin-profile-view-signal is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 3,172 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.