Need help implementing this on your team?
We'll install the skills, customize them to your workflow, and run the output through your team's combined LinkedIn network. Skills do the research, Linkd does the motion.
Live
Discovery
Signals
Hiring is budget. Hiring is pain.
A live job posting is the strongest qualification there is for tools serving that function. The skill finds companies hiring for a specified role, with each posting as evidence, and filters out stale and aspirational listings before they hit the deliverable.
HS
hiring-signal-account-discovery.zip
17.6 KB
·
Bundle: .skill file + SKILL.md inside
·
v1.0
A posting is a budget commitment.
A live job posting is the most concrete buying signal there is for tools that serve that function. Hiring a VP RevOps = revenue operations tooling pain + budget. Hiring 5 sales engineers = scaling motion = enablement and demo tooling. Hiring a Head of Security = security and GRC pain. The signal is concrete because it costs real money to recruit.
The skill hunts on LinkedIn job posts and ATS pages (Greenhouse, Lever, Ashby) for the target role. Default window: last 30–60 days. Anything older is flagged or dropped, a posting from 6 months ago may be filled, abandoned, or evergreen.
Context matters. A 5,000-person company hiring a Senior Sales Engineer is meaningfully different from a 50-person company hiring a VP Sales. The skill flags company size + posting recency on every row so the user can read the signal correctly.
Any of these will work.
Find companies hiring a VP of RevOps right now.
Who's actively recruiting for Director of Security?
Hiring-signal account list, 100 companies hiring SDRs.
Companies scaling their CS team in the last 30 days.
Five steps.
01
Confirm the role
Be specific. "Sales leader" is too vague. "VP Sales OR CRO at companies under 1000 in B2B SaaS" is targetable. Ask the pitch context to judge relevance.
02
Hunt the postings
LinkedIn jobs + ATS pages (Greenhouse, Lever, Ashby). Default 30–60 day window. Older listings flagged or dropped, evergreen postings aren't real signals.
03
Detect aspirational hires
Postings recurring for 6+ months without being filled, or "if the right candidate" language. Flagged as weaker signal.
04
Contextualize by size
A 5,000-person company hiring a senior engineer is different from a 50-person company hiring a VP. Each row carries headcount + posting date.
05
Emit account list
CSV with: company, domain, posting URL, posting date, role title, ATS source. JSON variant for the chain into account-list-tierer or research-brief.
Postings, not pattern-matching.
!
Stale postings get dropped
A posting from 6+ months ago is more likely filled than open. The skill flags or drops; doesn't silently include to pad the list.
#
Replacement vs growth hires
Hiring a NEW VP Sales is different from replacing one. The skill notes when a company already has someone in the role (replacement = weaker signal).
@
Headcount-contextualized
"Hiring a senior engineer" means different things at 50 vs 5,000 employees. The skill flags company size so the signal can be read correctly.
?
Aspirational hires flagged
Postings that recur for many months are often "we'll hire if the right candidate appears". Marked as weaker signal, not premium.
Job posting as evidence row.
CSV ready for upload to Sales Nav, with one row per company. Each row carries the posting URL, the date, the specific role title, the ATS, and company headcount. Plus a JSON variant for chaining into account-list-tierer or account-research-brief.
Sample row
Globex Health
domain: globex.io
role: VP RevOps
posted: 2026-05-04
ats: Greenhouse
headcount: ~340
signal: new-role (no
current VP RevOps)
url: boards.greenhouse.io
/globex/jobs/45233
Posting contract
- Output
- CSV + JSON
- Window
- 30–60 days (default)
- Required tools
- web_search, web_fetch
- Sources
- LinkedIn, Greenhouse, Lever, Ashby
- Replacement detection
- Yes
- Pairs with
- account-list-tierer
Pick your Claude. Drop in the skill.
The download is a zip containing two things: the .skill file (what you upload to Claude) and a SKILL.md sidecar (the human-readable instructions). Unzip first, then follow the steps for your Claude.
⌘
Most people
Claude.ai or Desktop
- Download and unzip the bundle.
- Open or create a Project in Claude.
- Go to Project knowledge, click Add content.
- Upload the
.skillfile from the unzipped bundle. - Start a new chat in that project. Ask it to run the skill.
Download bundle ↓
No restart needed
›_
Developers
Claude Code
- Download and unzip the bundle.
- Unzip the inner
.skillfile too (it's also a zip). - Move the resulting folder into
~/.claude/skills/ - Restart Claude Code.
- Type a prompt that fits the trigger. The skill loads automatically.
Download bundle ↓
macOS / Linux / WSL
{ }
Builders
API or Agent SDK
- Download and unzip the bundle.
- Open the SKILL.md sidecar to read the full instructions.
- Load via the Skills API, or paste the instructions into your agent's system prompt.
- Make sure your agent has
web_searchand file output enabled. - Ship it.
View SKILL.md ↓
v1.0
Read the full instructions.
This is exactly what Claude reads when the skill triggers. No hidden prompts, no separate config. What you see here is what you get.
hiring-signal-account-discovery-SKILL.md
⌄
hiring-signal-account-discovery-SKILL.md
Loading SKILL.md...