onfire-ai
- 24 skills
- 0 followers
- 3 hours ago last updated
- ▌ Match Person · onfire-aiResolve a person (from name, email, and/or company context) to a verified LinkedIn profile plus current title and employer using the Onfire `match_person` tool. Use when you have a person reference but no LinkedIn URL, when CRM contacts need identity resolution before enrichment, or as the upstream step before `contact_data_enrichment` on rows missing LinkedIn URLs.
- ▌ Match Company · onfire-aiResolve a company (from name, website, or LinkedIn URL) to a verified LinkedIn URL plus firmographics using the Onfire `match_company` tool. Use when you have any starting signal about a company — a name, a website, a CRM row, a LinkedIn URL you want to verify — and need a canonical identity. Also use as the upstream step before any `ai_prospecting` call that doesn't already have a company LinkedIn URL.
- ▌ AI Prospecting · onfire-aiRun AI prospecting against a target company to rank the likely buyers/champions to approach at that ACCOUNT, using the Onfire `ai_prospecting` tool. Use when the user wants prospects for an account, a ranked list of who to talk to at a company, or a batch run across multiple companies, and wants the engine to decide who is best. NOT for deterministic title/persona/seniority/location/technology lookups (route those to `ask_onfire` over the contact entity) or single-person "is X worth a meeting" checks. Covers `action='run'`, the dataset-backed response and how to query it, the polling pattern for long runs, and the shadow-schema test mode.
- ▌ Hiring Signals · onfire-aiFind open job postings at target companies using the `ask_onfire` tool against the `job_post` entity. Use when the user wants to know what roles a company is actively hiring for, where they're hiring, what seniority they're posting, which companies are hiring for a technology or skill, what open positions signal budget or expansion - phrases like "what is Northwind hiring for?", "find VP-level roles at my target accounts", "which accounts are expanding their security team?", "find buyers at companies hiring AI engineers", "show open data engineer roles in EMEA", or any job posting / hiring signal lookup.
- ▌ Title Movement · onfire-aiDetect month-by-month title movement (new hires and departures by job title) at any target company using `ONFIRE.EXPERIENCES_FULL` via `ask_onfire`. Use this skill whenever the user asks about: - "title movement" or "role movement" at a company - "new titles at [company]" or "what titles are they adding" - "titles that left [company]" or "what roles are disappearing" - "hiring signals for [company]" based on title patterns - "title changes at [company]" or "what roles are growing / shrinking" - detecting org changes, headcount shifts, or leadership gaps at a company - any question combining a company name with tracking who joined or left by title Trigger even if the user just pastes a LinkedIn company URL and asks "what's happening there?" or "show me movement." Works for any company — just needs a `company_linkedin_url` slug.
- ▌ Account Research · onfire-ai bundleGenerate a full account research report for any company. The Onfire MCP `account_research` tool fetches the core data sources - tenant config, 10-K extracts, employee technology footprint, intent signals, and AI-scored prospects - in one call and returns a rendering contract alongside the data. This skill enriches it with additional warehouse signals via `ask_onfire` (hiring momentum, event attendance, persona/technology growth trends, dated deployment proof, active hiring managers), enforces the rendering contract, and produces the final customer-facing A4 HTML file. Use whenever a user asks to "generate a report", "research an account", "build a BDR brief", "run account research", or mentions a company domain alongside words like "signals", "prospects", "10-K", "hiring", "events", "growth", "use cases", or "tenant".
- ▌ Competitor Report · onfire-ai bundleGenerate a full client-grade Competitor Intelligence Brief for a single competitor company. The window is configurable - the last completed calendar quarter (default) or the trailing 12 months. Produces an A4 HTML and optional PDF in a McKinsey-style consulting layout. The brief covers org reshape, hires, leavers, open job postings, customer acquisition motion by industry, market sentiment, GitHub footprint, vendor-trust events, an evidence wall of verbatim third-party quotes, and a Company Reference Card. Use this skill whenever the user asks to "build a competitor brief", "competitive intelligence on X", "deep dive on competitor X", "Nexagon-style report on X", "scan competitor X for the last quarter", "12-month view of competitor Y", "what's happening at competitor Y", or any phrasing that mixes a vendor name with a request for an analytical multi-section report on their org and market posture.
- ▌ Airgap Opportunity · onfire-aiFind and report air-gap demand signal — accounts, people and evidence about air-gapped, isolated, disconnected, cross-domain and classified environments. Use whenever someone asks about air gap, air-gapped, isolated or disconnected networks, data diodes, cross domain solutions, SCIF/SIPR/JWICS/classified networks, offline or DDIL deployment, or asks "who is working on air-gap", "air-gap opportunity", "air-gap accounts", "air-gap signals", "air-gap volume", or wants an air-gap prospect list or report. Anchored on the curated `Air-Gapped Environment` and `Cross Domain / Data Diode` insights, with `search_community_messages` and `query_intent_signals` for verbatim evidence.
- ▌
- ▌ Employee Footprint · onfire-aiFind employees at a target company whose profiles carry a specific technology or competitor signal using the `ask_onfire` tool (insight-based footprint). Use when the user wants proof a product is deployed at an account, wants a competitor footprint cut, or needs evidence from employee profiles — phrases like "who at Meridian Bank uses Sentinex", "find Ironwall users at Nornet", "do any Northwind engineers run Kubernetes", "show me the Sentinex footprint at Skywall Networks", or any technology/competitor footprint lookup at a specific company.
- ▌ Github Repo Signals · onfire-aiFind people who starred or forked GitHub repositories using the `ask_onfire` tool over the `github_member` entity. Use when the user wants to know who interacted with a GitHub repo, find developers who starred repos related to a technology or vendor, or check if people from a specific company engaged with a repo — phrases like "who starred any Artifex repo", "engineers who forked a Kubernetes repo", "did anyone from Northwind interact with our GitHub", "find developers in India interested in open-source security tools", or any GitHub repo engagement lookup.
- ▌
- ▌ Entity People Search · onfire-aiSearch for people/prospects directly from Onfire's LinkedIn people entity (ONFIRE.PEOPLE = entity `contact`) using the `ask_onfire` tool. Use when the user wants to find prospects by job title, company, location, seniority, persona/role, technology footprint, or keywords in their profile — phrases like "find engineers at Northwind", "who are the VPs of Security at banks in the US", "show me people with 'Loglytics' in their job summary", "look up this LinkedIn URL", or any people search that doesn't require Forschung's cross-database scoring.
- ▌ Company Growth Trends · onfire-aiAnalyse monthly headcount growth and technology/persona adoption trends for companies. For total company headcount use `get_company_headcount` (or the `headcount_monthly` entity via `ask_onfire`); for technology or persona growth use `ask_onfire` against the `growth_insight_monthly` entity. Use when the user wants to know if a company is hiring or contracting, whether a specific technology is spreading within a company, or how headcount growth compares to tech adoption — phrases like "is Acme growing?", "is EDR adoption growing at these accounts?", "compare Sentinex vs total headcount trend at Skywall Networks", "which accounts are shrinking?", "is the data engineering team at Frostbyte expanding?", or any month-over-month growth question.
- ▌ Entity Company Search · onfire-aiSearch for companies directly from Onfire's LinkedIn company entity (the `company` entity, table ONFIRE.COMPANIES) using the `ask_onfire` tool. Use when the user wants company firmographics, technology adoption, funding data, or social URLs — phrases like "find fintech companies in Israel with 50-200 employees", "look up Northwind's company data", "which companies in our list are publicly traded", "get the GitHub URL for Artifex", or any company lookup that can be answered with structured filters on LinkedIn company data.
- ▌ Weekly Territory Plan · onfire-ai bundleBuild and refresh a rep's recurring territory plan - up to 5 best-fit accounts x up to 5 buying-committee people, each carrying the signal that surfaced them, a warm-intro path, a drafted first touch, and contact data on request - delivered as one durable artifact plus a shareable report and a plan workbook. Orchestrates `ask_onfire`, `query_intent_signals`, `ai_prospecting`, `detect_warm_intros` and `contact_data_enrichment` behind a scored account resolver, and schedules itself to re-run. Contact enrichment is PAID and strictly on-demand, with a two-phase consent flow above 10 contacts. Use whenever the user says "run my 5x5", "my 5 by 5", "set up my 5x5", "refresh my weekly plan", "what's my week", "build my territory plan", "who should I work this week", or asks to reschedule or change the ICP behind a recurring plan. NOT for researching one named account (use account-research), and NOT for a one-off prospect list at a single company (use ai-prospecting).
- ▌ Community Join Signals · onfire-aiFind people and companies that joined an online community (a Slack workspace, Discord server, Reddit community, LinkedIn group, GitHub org, or X/Twitter) using the `ask_onfire` tool against the `evidence` entity. Use when the user asks who is a member of a SPECIFIC named community, wants to enumerate a community's members, wants community-presence signals for an account or individual, or wants a per-community breakdown — phrases like "pull the members of the Artifex community", "who joined the Artifex Slack", "members of the DevSecOps Discord", "find everyone from Northwind who's in any Kubernetes community", "who joined any security Slack since January", "which communities are Acme's employees in", or any community-membership lookup. The specific community's name, platform, URL, and join date ARE queryable.
- ▌ Sep Cadence Enrollment · onfire-aiThe gateway for ALL work against a connected sales engagement platform (SEP) — Outreach, Salesloft, Gong Engage, Reply.io. Use whenever the user names one of those platforms or uses their vocabulary — "add them to a cadence", "sequence these prospects", "push this person to Outreach", "enroll in Salesloft", "put them in my flow", "sync this lead to the SEP", "what cadences do we have", "is she already in a sequence", "start outreach on these accounts", "push my prospecting results into a cadence". Owns provider discovery (never guess Outreach vs Salesloft), the CRM-first law (write to the CRM, validate the write landed, then create the SEP copy — never the reverse), the engine-enforced CRM-proof gate and its CRM_UPLOAD_REQUIRED refusal, the exact-email rule that keeps the CRM→SEP hydration sync from creating duplicates, and the per-provider enrollment recipe. Routes to sibling skills for email composition (outreach-sequence-email-composer) and Gong flow personalization (gong-create-and-push-to-flow).
- ▌ Contact Data Enrichment · onfire-aiAppend verified professional emails and phone numbers to contact records using the Onfire `contact_data_enrichment` tool. Use when the user asks for emails, phones, or "contact info" for prospects, when enriching a CSV / CRM list, or as the standing follow-up to any `ai_prospecting` run. PAID per contact per data type — has a strict two-phase consent flow above 10 contacts. This skill enforces that flow.
- ▌ Community Message Search · onfire-aiFind people and companies by what they SAID in community/social messages (Slack, Discord, Reddit, StackOverflow, GitHub, etc.) using the `search_community_messages` tool — semantic vector search that returns the SENDERS of messages mentioning or discussing a topic, regardless of how they feel about it. Use for message-based discovery and prospecting — phrases like "find relevant people talking about my competitors", "who's discussing [topic]", "companies whose employees mentioned [topic]", "people raising [pain point]", "find prospects discussing [category]", "relevant chatter about [theme] for this account", "who's asking about [problem]". This is MENTION / discovery, NOT opinion — if the user wants positive/negative sentiment, complaints, or advocacy, use community-messages-sentiment instead; if they want who JOINED a named community, use community-join-signals; for non-message signals (job changes, events, job posts) use query_intent_signals.
- ▌ Event Attendance Signals · onfire-aiFind people who attended conferences, summits, webinars, or industry events using the `ask_onfire` tool against the `event_contact` / `event_company` entities. Use when the user wants to know who went to a specific event, find attendees from a target company, discover which events a person attended, or filter prospects by event participation — phrases like "who attended CloudCon 2025", "find people from Cloudforce at SecureCon", "which events did people from our target accounts go to", "show me Quadrant IT Symposium attendees", or any event attendance lookup.
- ▌
- ▌ Gong Create And Push To Flow · onfire-aiGong: Create and Push to Flow (with personalized email steps)
- ▌ Outreach Sequence Email Composer · onfire-ai bundleEnd-to-end workflow to put a prospect into an Outreach sequence and have the agent compose the email for the manual-email step, grounded in Onfire data (the prospect, their company, the tenant's ICP), user input, and conversation context — then stage it as a draft and ask the user whether to send automatically or send it themselves. Works for a single prospect or many. Use whenever the user says things like "add this prospect to a sequence and draft him an email", "write a custom email for X in Outreach", "sequence these people and compose emails", "put them in my SAP Campaign and draft the outreach", "create a sequence and start emailing these accounts", or any request that combines an Outreach sequence with composing/sending a personalized email. Can also create a brand-new sequence first if the user wants one. Reads and writes your tenant's SEP via the Onfire Integrations tools.