ABeck617
- 10 skills
- 0 followers
- 7 hours ago last updated
- ▌ Entity People Search · abeck617Search 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.
- ▌ Contact Data Enrichment · abeck617Append 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 · abeck617Find 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.
- ▌
- ▌ Gong Create And Push To Flow · abeck617Gong: Create and Push to Flow (with personalized email steps)
- ▌ Outreach Sequence Email Composer · abeck617 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.
- ▌ Match Person · abeck617Resolve 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.
- ▌ AI Prospecting · abeck617Run 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.
- ▌ Account Research · abeck617 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 · abeck617 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.