skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
wannalead.co85 installs

job-change-signals

Find recent buyer-persona job changes and produce a precise, fresh trigger list using Wannalead search and enrichment endpoints.

How do I install this agent skill?

npx skills add https://wannalead.co --skill job-change-signals
view source ↗

Is this agent skill safe to install?

No partner audit is available yet. Read the source before installing.

What does this agent skill do?

Job-change signals

Find people who recently moved into a role you sell to. Use Wannalead endpoints only and prioritize recency and fit over volume.

First-use context

On a new workspace, start with wannalead-onboarding: its wannalead me identity check is the first Wannalead command, and it loads any saved context from ONBOARDING.md and the durable files. Incomplete onboarding does not block this task. Use the saved context when present, take the rest from the user's request, and ask only for details this task needs. Authentication, the relevant network connection, billing, and endpoint guards still apply.

Mandatory endpoint discovery

Before calling the API, run the complete discovery sequence:

wannalead endpoints
wannalead routes <filter>
wannalead endpoints <name> --examples --json-schema
wannalead openapi path <exact-/v1-route>

Scan the full catalog, search the domain and synonyms, then read every candidate's complete contract before building a payload. Never rely on the endpoint names below or say a capability is impossible until the live catalog, plausible candidates, deprecations, and replacements have been checked.

Durable context

Follow the progressive context rules from wannalead-onboarding. Before querying, load COMPANY.md and the relevant ICP from ICPS.md. Read current CRM exclusions and prior contact state from their authoritative systems when available. Keep the trigger list in the task result or server-side campaign state, not in local Markdown. A job change is prospect evidence, not a durable ICP rule; propose any context change to the user before updating ICPS.md.

Choose the path

Run salesnav.seat first. With hasSeat: true, use Path A: it is the only path that returns job changes directly, already filtered by function, seniority, company size and region. Without a seat, use Path B (existing connections or CRM list) or Path C (persona search); a salesnav.* call on such an account fails with LINKEDIN_SALES_NAVIGATOR_SEAT_REQUIRED. Path D is a last resort.

Path A: Sales Navigator (seat required)

wannalead call salesnav.seat -body '{}'
wannalead call salesnav.leads.search -body '{"function":"human resources","seniority":"decision_makers","recently_changed_jobs":true,"company_headcount":"51-200,201-500,501-1000,1001-5000,5001-10000","region":"105015875","count":100}'
  • recently_changed_jobs = changed jobs in the last 90 days. Rows carry currentPositions[].startedOn and a RECENTLY_HIRED or RECENTLY_PROMOTED signal; keep the recency window the user asked for.
  • Page with next_start (max 100 rows per page, 2,500 per query). Narrow the filters instead of paging deep.
  • Resolve free-text titles to ids with salesnav.facets.typeahead (type: title, plus lang: fr_FR for French titles such as DRH) only when needed; keywords also works.
  • salesnav.profiles.get returns addedAt per position (when the person added it), finer than the month-level startedOn.
  • salesProfileId is Sales Navigator scoped (ACwAA). Before an invitation or a message, resolve the person with profiles.resolve and use its ACoAA.

Path B: known people (connections or CRM list)

  1. Take the user's existing list: me.connections, mirror data, or CRM records matching the persona.
  2. Hydrate them with one bulk profiles.enrich call and keep current positions whose startYear/startMonth fall inside the window, or whose company differs from the stored one.

This catches champions who moved company: a warm lead at the new company.

Path C: persona search plus start dates

  1. Search the persona with people.search using the function filter (for example human resources) plus keywords, geo and seniority.
  2. Enrich survivors with one bulk profiles.enrich call and filter current positions by start date.
  3. Check company size with companies.enrich (employeeCount) when the ICP has a headcount range.

Free accounts hit LinkedIn's monthly search limit quickly (search_limit_reached): stop paging and say so instead of retrying.

Path D: announcement posts (noisy)

job-changes.search is a keyword search over posts, not a job-change feed. Most rows come back without author or text and need posts.resolve, and a persona keyword alone (for example DRH) returns generic posts. Use the announcement phrase in the post language (for example "starting a new position" or "j'occupe désormais le poste de") and expect to discard most rows after persona filtering.

Recurring runs

With a Sales Navigator seat, a saved search already counts its new results: salesnav.saved-searches returns newHitsCount per saved search, a cheap first check before re-running salesnav.leads.search.

For a daily or weekly trigger, keep the previous run's member ids (memberId or ACoAA) as the baseline and report only new ones. Store the baseline where the user agrees (campaign state, CRM, or a local JSON file), never as prospect notes in ICPS.md.

LinkedIn start dates have month-level precision. Do not claim day-level recency.

Output

A short weekly list of named new-role holders matching the persona and account criteria, with the observed change signal and its available recency.

Guardrails

  • Prefer 20–50 precise matches over a wide export.
  • Remove open-to-work, skills-update, and recruiter noise.
  • Treat freshness as the value and avoid stale-trigger outreach.
  • Stop on rate-limit or connection errors; never retry-loop.
  • For a reproducible Wannalead product failure, capture the endpoint and request_id/job_id; report it with feedback.send only after the user approves the exact body, and never include secrets or raw private content.
  • Never assemble LinkedIn IDs or call LinkedIn directly.

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/wannalead.co/job-change-signals">View job-change-signals on skillZs</a>