Contact Research

by anthropicsae1513ea94dcNo license27K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Research a specific person using Common Room data. Triggers on 'who is [name]', 'look up [email]', 'research [contact]', 'is [name] a warm lead', or any contact-level question.

FeaturedInstructions onlyResearch & AnalysisMarketing & Sales
AI-generated overview

Researches a person's contact profile from Common Room data and produces a structured profile with engagement signals.

What it does
Looks up a contact in Common Room by email, social handle, name plus company, or name alone, then assembles a profile from returned field groups such as scores, recent activity, website visits, Spark enrichment, and segments. Adds an abbreviated account snapshot for the contact's parent company and proposes two to three signal-backed conversation angles. Output is a formatted profile that omits sections with no data and flags sparse records instead of guessing.
When to use it
Use when someone asks who a specific person is, wants a contact looked up by email or handle, or asks whether a named contact is a warm lead. Also suited to contact-level questions about engagement history, persona, or account context before outreach.
Requirements
Requires access to Common Room contact data, including its object catalog and Spark enrichment where available; no scripts are shipped, only instructions plus a reference guide.

Contact Research

Retrieve a comprehensive contact profile from Common Room. Supports lookup by email, social handle, or name + company. Returns enriched data including activity history, Spark, scores, website visits, and CRM fields.

Step 1: Locate the Contact

Common Room supports multiple lookup methods — use whichever the user has provided:

What the user givesLookup method
Email addressLook up by email (most reliable)
LinkedIn, Twitter/X, or GitHub handleLook up by social handle — specify handle type explicitly
Name + companyIdentity resolution by name + org domain; present matches if ambiguous
Name onlySearch by name; if multiple matches, show a brief list and ask the user to confirm

If no match is found, respond: "Common Room doesn't have a record for this person." Do not speculate or fabricate profile data.

Step 2: Fetch Contact Fields

Use the Common Room object catalog to see available field groups and their contents. For full profiles, request all groups. For targeted questions, request only what's relevant.

Key field groups to know about:

  • Scores — always return as raw values or percentiles, never labels
  • Recent activity — use Contact Initiated filter (last 60 days) for their actions, not your team's
  • Website visits — total count + specific pages (last 12 weeks)
  • Spark — retrieve all Sparks when tracking engagement evolution over time

Step 3: Run Spark Enrichment (If Available)

If Spark is available, use it. Spark provides:

  • Professional background and job history
  • Social presence and influence signals
  • Persona classification: Champion, Economic Buyer, Technical Evaluator, End User, or Gatekeeper
  • Inferred role in the buying process

If Spark is unavailable but real activity data exists (recent actions, website visits, community engagement), infer a persona from those signals. If neither Spark nor activity data is available, classify as Unknown — do not guess a persona from title alone.

Retrieve all Sparks (not just the most recent) when the user wants to understand how this contact's engagement has evolved over time.

Step 4: Assess Account Context

Pull an abbreviated account snapshot for this contact's parent company. Note:

  • Open opportunities, expansion signals, or churn risk at the account level
  • Whether other contacts at this company are also active
  • How this person's engagement compares to their colleagues

Step 5: Identify Conversation Angles

Based on activity and signals, surface the strongest 2–3 hooks:

  • A recent Contact Initiated activity (community post, product event, support ticket)
  • A specific web page they visited recently — especially if it signals evaluation intent
  • A job change, promotion, or company news
  • Their Spark persona and what that suggests about communication style
  • Their role in a known active deal

Output Format

Only include sections where data was actually returned. Omit sections with no data rather than filling them with guesses.

When data is rich:

## [Contact Name] — Profile
**Overview**[2 sentences: who they are, their role, and relationship status]
**Details**- Title: [title]- Company: [company]- Email: [email]- LinkedIn: [URL]- Other profiles: [Twitter/X, GitHub, CRM link if available]
**Scores** [If scores returned][All scores as raw values or percentiles]
**Recent Activity** (last 60 days) [If activity returned][3–5 bullets with dates]
**Website Visits** (last 12 weeks) [If visit data exists][Total visit count + list of pages visited]
**Spark Profile** [If Spark data is non-null][Persona type, background summary, influence signals]
**Segments** [If segments returned][List of segment names this contact belongs to]
**Account Context**[1–2 sentences on their company's status]
**Conversation Starters**[2–3 specific, signal-backed openers]

When data is sparse (e.g., only name, title, email, tags returned; sparkSummary is null):

## [Contact Name] — Profile (Limited Data)
**Data available:** [List exactly what Common Room returned]
[Present only the returned fields]
**Web Search**[Any findings from searching their name + company]
**Note:** Common Room has limited data on this contact. No activity history, scores, or Spark profile available. I can run deeper web searches or look up their company for additional context.

Do not generate conversation starters, persona inferences, or engagement assessments from sparse data. These require real signals.

Quality Standards

  • Lookup must use the correct method for the input type — don't guess on email vs. handle
  • Scores as raw/percentile only — never labels
  • Contact Initiated activity (last 60 days) is the primary engagement signal — lead with it
  • If Spark is unavailable, say so — don't fabricate a persona from title alone
  • Flag any contact where the most recent activity is older than 30 days

Reference Files

  • references/contact-signals-guide.md — full field descriptions, Spark persona guide, and conversation starter principles

Source and attribution

Source:anthropics/knowledge-work-pluginsinpartner-built/common-room/skills/contact-researchat commitae1513e

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

More from anthropics/knowledge-work-plugins

Ticket Deflector

anthropics

Featured

Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."

Awaiting classification27Kupdated today

Tax Season Organizer

anthropics

Featured

Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."

Awaiting classification27Kupdated today

Tax Prep

anthropics

Featured

Prepares tax materials from closed books: a quarterly estimated payment breakdown or a year-end 1099-NEC list and accountant packet.

Business & Finance27Kupdated today

Smb Onboard

anthropics

Featured

Guides a small-business owner through first-time setup: connecting tools, running a value-proof recipe, capturing business context, and setting a weekly…

Productivity & Workflow27Kupdated today

Smb Router

anthropics

Featured

Routes a small-business owner's request to the right plugin skill or command and explains what is available.

Productivity & Workflow27Kupdated today

Month End Prep

anthropics

Featured

Reconciles the accounting ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) against PayPal, Shopify, Square, and Stripe settlements, flags transactions that need attention, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). This is the first link of the /close-month command; a request to close the month or the books routes there, and the command runs this skill before refreshing the forecast and distributing the packet. Use this skill directly only when the owner wants the reconciliation alone, with no forecast refresh and no distribution: "just reconcile, no packet," "what's missing from the books," "flag the duplicates and missing receipts," or "write the P&L narrative for this month."

Awaiting classification27Kupdated today