SkillFind who to talk toPublic data only

Turn job posts into buying signals

Finds dated job posts that reveal a plan, like a first head of sales or a new country team, checked on the company's own careers page.

Works inClaudeClaude CodeCodexCursorGemini CLIGitHub CopilotChatGPTNeeds: Web searchv1.0 · November 20, 2026
hiring-signal-scan/SKILL.mdDownload
name
hiring-signal-scan
description
Use this skill when you want to know which accounts are hiring in a way that signals a plan you can help with, such as a first head of sales, a country manager or a new sales team. It checks each job post on the company's own careers page and returns the dated posts that hold, with the plan in the post's own words and the role to contact.
license
CC-BY-4.0

Turn job posts into buying signals

A job post is a dated, public statement of a plan. When a company opens a head of sales role, a country manager seat or several sellers in a new city, it has decided to grow its commercial motion, and the people it hires will soon choose tools, partners and suppliers. This skill scans job posts for a list of accounts or a segment and keeps only the posts that reveal such a plan, are still open and carry a date.

Inputs

Ask for what is missing:

  1. What the user sells, and which hires create a need for it. If the user is unsure, propose three to five role patterns, such as "first VP Sales", "country manager, Brazil" or "three or more account executives in one new city".
  2. The accounts to scan (company names with domains), or a segment to discover from (industry, size, region).
  3. The locations of the roles that matter.
  4. The window. Default: posts first published in the last 30 days.
  5. Accounts to leave out: customers, open deals, competitors.

Steps

  1. Find each careers page. Try the company's site first, then note which applicant tracking system hosts the jobs.

  2. Pull the open roles from the source.

    Greenhouse: GET https://boards-api.greenhouse.io/v1/boards/{board_token}/jobs, no login needed; add ?content=true for the full description, department and office. The board token is the name after job-boards.greenhouse.io/ in the company's job links.

    Lever: GET https://api.lever.co/v0/postings/{site}?mode=json, filtered with location, team, department or commitment.

    Other careers pages: fetch the page and read the schema.org JobPosting data when present (datePosted, validThrough, hiringOrganization, jobLocation).

    To discover accounts across a segment, search LinkedIn Jobs or a job board by title and location, newest first, then confirm every hit on the company's own page in step 4.

    Without a web tool, ask the user to paste the job links or the descriptions.

  3. Keep posts that reveal a plan: senior or commercial roles, a first role in a new country or city, several sellers opening at once, a leader asked to build a team. Drop routine single vacancies at large companies, evergreen listings, internships and roles unrelated to what the user sells.

  4. Confirm it is live and dated. Open the post on the company's own careers page. Copies on aggregators outlive the original: on 17 November 2026 a web search surfaced a head of sales role whose own careers page said the job was no longer available. No date, no signal.

  5. Read the whole post, not a snippet. Copy the one line that states the plan, for example "define and execute a regional go-to-market strategy".

  6. Look for a second signal in the same window: a funding round, a new leader, a new office or a trade show. Mark the rows where two signals stack. If the funding-and-leadership-signals skill is installed, run it on the same accounts.

  7. Check for stop signals. A commercial layoff with no re-hire is a reason to drop an account.

  8. Rank. Stacked signals first, then new markets, then seniority.

  9. Report an empty scan as empty, with the accounts and patterns checked.

Output

| # | Company | Role | Location | First posted | Open on (checked) | The plan, in the post's words | Second signal | Why now | Talk to | Source |
|---|---------|------|----------|--------------|-------------------|-------------------------------|---------------|---------|---------|--------|
| 1 | [Company] | [Title] | [City, country] | [YYYY-MM-DD] | [YYYY-MM-DD] | "[quoted line]" | [Signal and date, or none] | [One line of reasoning] | [Role] | [Company careers URL] |

Scanned: [N] accounts, [N] open roles read, [N] matched a pattern, [N] dropped (closed, undated, routine), [N] kept.

"Talk to" is a role, usually the leader the new hire reports to, or the new hire once they start. Never the recruiter.

Guardrails

Reads: company careers pages, public job board APIs, job search results. Writes: nothing outside this conversation. Asks before: adding accounts to a CRM, contacting anyone, or using a tool that needs the user's login.

  • MUST date every row from the post itself and show the date the post was confirmed open.
  • MUST link the company's own page, not an aggregator copy.
  • MUST quote the plan from the post rather than paraphrase it into a stronger claim.
  • NEVER treat a closed or undated post as a signal.
  • NEVER contact candidates or recruiters, or reply to a job post as a sales channel.
  • NEVER scrape behind a login or against a site's terms.

Sources

Made by ALTARA, the AI sales agent your team texts. More skills: https://www.altaratech.com/store

Use it with