How do I install the Account Watchlist skill?

Run npx skillmds@latest add reqbeat-growth/account-watchlist 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 Account Watchlist 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 Account Watchlist?

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 Account Watchlist free to use?

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

Who published Account Watchlist?

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

Account Watchlist by reqbeat-growth

Name: Account Watchlist
Author: reqbeat-growth

Account Watchlist

Watch named accounts and get pushed the moment they start hiring, instead of polling. Use when the user asks to monitor companies, wants an alert when a target account opens a role, an ABM trigger, or a daily diff of what changed.

File contents

Account watchlist

Polling asks "anything new?" a hundred times and is wrong ninety-nine of them. A watch answers once, at the exact moment a named account starts hiring the function the user sells to. That moment is the whole value: first voice, not ninth.

Ask for it like this

"Tell me when Monzo starts hiring engineers"
"Watch these 20 accounts for sales roles"
"What changed in my patch since yesterday?"

How it works

Push setup, two calls:

POST /v1/webhooks     register the delivery target once
POST /v1/watches      company_id or a criteria set, plus event_types

Header X-API-Key from $REQBEAT_API_KEY. One POST /v1/quickstart (webhook_url + domain) wires a working watch and webhook in a single call if the user prefers. Missed deliveries replay via /v1/webhook-deliveries/replay; signature verification is in the API reference.

Pull path, no webhook needed:

GET /v1/events              the event feed, filter by company_id or event_type
get_changes (MCP tool)      ledger diff with a since-cursor: only what changed

For a daily diff, store the cursor between runs and pull only the delta.

Output format

For setup: confirm what is watched (companies or criteria), which events, and where deliveries go. For a diff pull: a short list of changes, each with company, event type, and date, newest first, followed by "nothing else changed since {cursor date}".

Rules

Free tier holds 3 concurrent watches; deleting one returns the slot. Say so before creating a fourth.
Delivered changes on free tier cap at 50 per billing month, forward-only, no backfill. Quote this rather than letting the user discover it.
A watch that fires belongs in the funnel: offer pre-call-brief on the company, then signal-first-outreach for the first touch.
Never print the key, and never register a webhook target the user did not name.

---name: account-watchlistdescription: Watch named accounts and get pushed the moment they start hiring, instead of polling. Use when the user asks to monitor companies, wants an alert when a target account opens a role, an ABM trigger, or a daily diff of what changed.---# Account watchlistPolling asks "anything new?" a hundred times and is wrong ninety-nine of them. A watch answers once, at the exact moment a named account starts hiring the function the user sells to. That moment is the whole value: first voice, not ninth.## Ask for it like this- "Tell me when Monzo starts hiring engineers"- "Watch these 20 accounts for sales roles"- "What changed in my patch since yesterday?"## How it worksPush setup, two calls:```POST /v1/webhooks register the delivery target oncePOST /v1/watches company_id or a criteria set, plus event_types```Header `X-API-Key` from `$REQBEAT_API_KEY`. One `POST /v1/quickstart` (webhook_url + domain) wires a working watch and webhook in a single call if the user prefers. Missed deliveries replay via `/v1/webhook-deliveries/replay`; signature verification is in the API reference.Pull path, no webhook needed:```GET /v1/events the event feed, filter by company_id or event_typeget_changes (MCP tool) ledger diff with a since-cursor: only what changed```For a daily diff, store the cursor between runs and pull only the delta.## Output formatFor setup: confirm what is watched (companies or criteria), which events, and where deliveries go. For a diff pull: a short list of changes, each with company, event type, and date, newest first, followed by "nothing else changed since {cursor date}".## Rules1. Free tier holds 3 concurrent watches; deleting one returns the slot. Say so before creating a fourth.2. Delivered changes on free tier cap at 50 per billing month, forward-only, no backfill. Quote this rather than letting the user discover it.3. A watch that fires belongs in the funnel: offer `pre-call-brief` on the company, then `signal-first-outreach` for the first touch.4. Never print the key, and never register a webhook target the user did not name.

Frequently asked questions