Download for MacApple silicon, macOS 14+
Skill

anysite-crm-inbound

@anysiteio Updated 2026-10-05

Instant read-only verdict on ONE inbound lead - who they really are, whether the company is real and ICP-fit, route suggestion and talking points - in 2-5 anysite calls. Takes an email, a name+company, or a linkedin_url; checks the CRM for prior history but writes nothing. Use when a single new lead just arrived (demo request, reply, form fill, DM) and the user wants a fast qualify/route decision. For batch prospecting use anysite-crm-prospect; for accounts already worked in the CRM use anysite-crm-account-brief.

Install

With your agent

Install OMGSkills skill "anysiteio/agent-skills:plugins/anysite-gtm/skills/anysite-crm-inbound" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/anysiteio/agent-skills /tmp/agent-skills && ln -s /tmp/agent-skills/plugins/anysite-gtm/skills/anysite-crm-inbound ~/.claude/skills/anysite-crm-inbound

From README

CRM Inbound — one lead, one minute Every skill in this pack is batch-shaped except the most frequent moment in GTM life: a single lead just landed and someone asks "is this real / are they our ICP / who takes the call?". This skill answers that in 2 calls (verdict) to 4–5 calls (full mini-brief). Strictly read-only. Input Whatever the user has: an email, a name + company, a linkedinurl, or a forwarded demo-request text. Extract identifiers yourself; don't interrogate the user. Flow (cheap-first, stop as soon as the verdict is clear) Identify the person and company linkedinurl → execute linkedin/user/user {user: , cachemaxagedays: 30} → done. email with a work domain → people/by-email {email} (name, title, company, LinkedIn; may be a stored answer up to a year old — cross-check the company against the email domain). Miss → companies/resolve {website: } → company: → searchusers {firstname, lastname, currentcompany: [{"type": "company", "value": " "}]}.