All skills
newslinkedin Recruiting & Talent

Layoff Wave Interceptor

Catch freshly laid-off talent within days of the announcement, before every other recruiter circles back

Run this skill with your agent
1. Connect the MCP server
https://apidirect.io/mcp?token=YOUR_API_KEY
2. Then just say to your agent
Find people just laid off in {sector} who are open to work as a {role} and give me a shortlist to reach out to today
In clients that support MCP prompts (Claude Desktop, Claude Code, Cursor) this skill appears as a prompt named layoff-wave-interceptor. Any agent can also call get_skill(skill_id="layoff-wave-interceptor") to pull these steps on demand.

What it does

News breaks layoffs faster than LinkedIn does; by resolving the affected company to its numeric id and scanning for fresh 'open to work' / 'impacted' posts, you reach displaced candidates while they are still on the market and before the inbound rush.

Who it's for: In-house recruiters and staffing agencies racing to place displaced talent

Inputs

Input Required Description Example
sector Yes Industry or sector to monitor for layoff announcements fintech
role Yes Target job title to prioritize among the impacted employees Backend Engineer

How your agent runs it

  1. 1
    search_news(query="{sector} layoffs", time_published=7d, limit=50)

    Identify companies that announced workforce reductions in the last week and extract each affected company name.

  2. 2
    search_linkedin_companies(query=<company name>)

    Resolve each affected company from the news into its numeric LinkedIn company_id.

  3. 3
    search_linkedin(query="open to work", author_company=<company_id>, author_title={role}, get_sentiment=true, sort_by=most_recent)

    Surface impacted employees who just announced availability; keep the most recent posts matching the target role.

  4. 4
    linkedin_person_posts(url=<person_url>, get_sentiment=true)

    Confirm the person is genuinely displaced and currently active before adding them to the outreach list.

Delivers: A time-ranked shortlist of freshly displaced {role} candidates from companies that just announced {sector} layoffs, with profile links and recency signals.

Tools used

The full playbook

This is exactly what the MCP returns to your agent (via the layoff-wave-interceptor prompt or get_skill tool), with your inputs filled in.

SKILL: Layoff Wave Interceptor
News breaks layoffs faster than LinkedIn does; by resolving the affected company to its numeric id and scanning for fresh 'open to work' / 'impacted' posts, you reach displaced candidates while they are still on the market and before the inbound rush.

You are running this skill on API Direct via its MCP tools. Execute the steps below yourself by calling the named tools in order — values in <angle brackets> come from a previous step. Then deliver the result described at the end.

INPUTS:
  - sector (required): <sector — ASK THE USER>
  - role (required): <role — ASK THE USER>

STEPS:
  1. Tool `search_news` — search_news(query="<sector> layoffs", time_published=7d, limit=50)
     Identify companies that announced workforce reductions in the last week and extract each affected company name.
  2. Tool `search_linkedin_companies` — search_linkedin_companies(query=<company name>)
     Resolve each affected company from the news into its numeric LinkedIn company_id.
  3. Tool `search_linkedin` — search_linkedin(query="open to work", author_company=<company_id>, author_title=<role>, get_sentiment=true, sort_by=most_recent)
     Surface impacted employees who just announced availability; keep the most recent posts matching the target role.
  4. Tool `linkedin_person_posts` — linkedin_person_posts(url=<person_url>, get_sentiment=true)
     Confirm the person is genuinely displaced and currently active before adding them to the outreach list.

DELIVER: A time-ranked shortlist of freshly displaced <role> candidates from companies that just announced <sector> layoffs, with profile links and recency signals.

Note: each underlying tool call is billed at its normal endpoint price; get_sentiment adds a small per-page surcharge. Page through results as needed but stop once you have enough to deliver the outcome.