How do I install the Pre Call Brief skill?

Run npx skillmds@latest add reqbeat-growth/pre-call-brief in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pre Call Brief safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pre Call Brief?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pre Call Brief free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pre Call Brief?

reqbeat-growth (@reqbeat-growth) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pre Call Brief by reqbeat-growth — Agent Skill

Name: Pre Call Brief
Author: reqbeat-growth

Pre Call Brief

Brief the user on a company's hiring picture before a call or an email, in one API call. Use when the user asks "brief me on X", wants company research before outreach, a dossier, or context on what a prospect is hiring right now.

File contents

Pre-call brief

Fifteen minutes of manual research, replaced by one call. Before the user writes or dials, hand them the company's live hiring picture: what is open, how fast it is moving, what has been stuck, and what changed recently.

Ask for it like this

"Brief me on Anaplan before my 3pm call"
"What is company 1950 hiring right now?"
"Prep me for outreach to this list of five companies"

How it works

One endpoint does the heavy lifting:

GET /v1/companies/{company_id}/pre-action-brief

Header X-API-Key from $REQBEAT_API_KEY; never print the key. The response carries: pulse (open req count, velocity, direction, surge, weekly momentum), first_hires by function with dates, repost_pain (stuck roles), top_reqs (titles, countries, first_seen, boards), ats_migrations, and a provenance block with as_of.

No company_id yet? Resolve it first with GET /v1/reqs/search?role=...&geo=... or the keyless MCP tool who_is_hiring_for. Company name and HQ come from GET /v1/companies/{id}/enrichment.

Output format

Five lines, in this order, each with its date:

Motion: open reqs, direction, surge yes/no, this week vs last (from momentum buckets).
What they want: top 3 roles with first_seen dates and source boards.
Pain: stuck reposts, if any. This is the door-opener line.
Stage signals: first hires in a function, ATS migration if present.
Talking point: one sentence the user can open with, built only from the rows above.

Rules

Everything dated from the response; the brief quotes as_of.
Empty sections are stated as empty ("no repost pain on record"), never padded.
top_reqs is company-wide, not geo-filtered; say so if the user filtered by country earlier.
Batch politely: for a list of companies, one brief per company_id, and tell the user the call count.

---name: pre-call-briefdescription: Brief the user on a company's hiring picture before a call or an email, in one API call. Use when the user asks "brief me on X", wants company research before outreach, a dossier, or context on what a prospect is hiring right now.---# Pre-call briefFifteen minutes of manual research, replaced by one call. Before the user writes or dials, hand them the company's live hiring picture: what is open, how fast it is moving, what has been stuck, and what changed recently.## Ask for it like this- "Brief me on Anaplan before my 3pm call"- "What is company 1950 hiring right now?"- "Prep me for outreach to this list of five companies"## How it worksOne endpoint does the heavy lifting:```GET /v1/companies/{company_id}/pre-action-brief```Header `X-API-Key` from `$REQBEAT_API_KEY`; never print the key. The response carries: `pulse` (open req count, velocity, direction, surge, weekly momentum), `first_hires` by function with dates, `repost_pain` (stuck roles), `top_reqs` (titles, countries, first_seen, boards), `ats_migrations`, and a provenance block with `as_of`.No `company_id` yet? Resolve it first with `GET /v1/reqs/search?role=...&geo=...` or the keyless MCP tool `who_is_hiring_for`. Company name and HQ come from `GET /v1/companies/{id}/enrichment`.## Output formatFive lines, in this order, each with its date:1. **Motion:** open reqs, direction, surge yes/no, this week vs last (from momentum buckets).2. **What they want:** top 3 roles with first_seen dates and source boards.3. **Pain:** stuck reposts, if any. This is the door-opener line.4. **Stage signals:** first hires in a function, ATS migration if present.5. **Talking point:** one sentence the user can open with, built only from the rows above.## Rules1. Everything dated from the response; the brief quotes `as_of`.2. Empty sections are stated as empty ("no repost pain on record"), never padded.3. top_reqs is company-wide, not geo-filtered; say so if the user filtered by country earlier.4. Batch politely: for a list of companies, one brief per company_id, and tell the user the call count.

Frequently asked questions