agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/hiring-signal-outreach/SKILL.md

hiring-signal-outreach

Skill13 starsChanged 25 days agoMITView on GitHub

Use this skill when a target company is hiring for roles your product supports or replaces: \"they are hiring SDRs\", \"use job postings as a buying signal\", \"write outreach based on their job listing\". Reads the job listing for priorities, tools, team size and pain, decides whether the hire means need for your product, picks the right contact (usually the hiring manager), and writes outreach that helps the new hire succeed rather than threatening the role. Includes a scoring rule for which listings are worth acting on.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this when a job listing at a target account touches the problem you solve.

    line 16
  2. Distinctive:

    MUST contact the hiring manager, not recruiting or the candidate.

    line 64
  3. Distinctive:

    MUST act within the listing's lifetime.

    line 65
  4. Distinctive:

    NEVER suggest the company should not make the hire.

    line 66
  5. Distinctive:

    NEVER contact candidates or new hires to sell to their future employer.

    line 67

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this when a job listing at a target account touches the problem you solve. A company paying to hire for a problem has budget and urgency; the listing tells you what they think the problem is in their own words.

Inputs

  • The job listing text.
  • Account fit and tier.
  • Your offer and the roles it supports.

The play

1. Read the listing like a brief

Extract: the team the role joins and its size, what the person will own, the tools named, metrics they will be measured on, the phrases that reveal pain ("build from scratch", "clean up", "scale from 10 to 50"), and seniority.

2. Decide what the hire means

Listing typeMeaningWorth acting?
First hire in a functionBuilding the process from zeroYes: strong
Several roles in one team at onceScaling fast, process strainYes: strong
Leader for an existing teamChange is comingYes: time it to their start
Single backfillReplacing someoneWeak, unless the listing reveals new scope
Role your product partly automatesBudget exists; handle with careYes, with a support angle

3. Pick the contact

The hiring manager (the role's future boss) is almost always right. Not HR, not recruiting, and never the new hire before they start.

4. Write the angle: help, not replace

Frame the product as what makes the new team productive faster, or what covers the gap until the hire lands. "You don't need to hire" insults the plan they already approved.

5. Time it

Within 7 days of the listing appearing, while the problem is top of mind. A second touch when the role closes ("as your new team starts...").

Message pattern

Subject: the new SDR team

Hi Dana, saw Lumen is hiring four SDRs and the listing mentions building outbound "from the ground up". The part that usually slows new teams most is not the calling, it is getting a clean, researched list in front of each rep every morning.

We help teams like Northwind's get new reps booking in their second week. Worth a look before they start?

What good looks like

  • The opener quotes or closely paraphrases the listing, proving it was read.
  • The angle supports the hiring plan.
  • Listings are scored, and backfills are mostly ignored.
  • The common mistake is "I noticed you're hiring" followed by a generic pitch, which every vendor in the category sends the same week.

Rules

  • MUST contact the hiring manager, not recruiting or the candidate.
  • MUST act within the listing's lifetime.
  • NEVER suggest the company should not make the hire.
  • NEVER contact candidates or new hires to sell to their future employer.

Example prompts

  • "Here's a job listing for a RevOps manager at Contoso. Is it a signal for us, and what should we send?"
  • "Write outreach for these 20 accounts hiring SDRs this month."
  • "Score these job listings and tell me which to act on."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.