.agents/skills/contact-research/SKILL.md
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.
npx skillsauth add mmahalwy/cooper contact-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Common Room supports multiple lookup methods — use whichever the user has provided:
| What the user gives | Lookup method | |---------------------|--------------| | Email address | Look up by email (most reliable) | | LinkedIn, Twitter/X, or GitHub handle | Look up by social handle — specify handle type explicitly | | Name + company | Identity resolution by name + org domain; present matches if ambiguous | | Name only | Search 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.
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:
Contact Initiated filter (last 60 days) for their actions, not your team'sIf Spark is available, use it. Spark provides:
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.
Pull an abbreviated account snapshot for this contact's parent company. Note:
Based on activity and signals, surface the strongest 2–3 hooks:
Contact Initiated activity (community post, product event, support ticket)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.
Contact Initiated activity (last 60 days) is the primary engagement signal — lead with itreferences/contact-signals-guide.md — full field descriptions, Spark persona guide, and conversation starter principlesdevelopment
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
content-media
Interactive PDF viewer. Use when the user wants to open, show, or view a PDF and collaborate on it visually — annotate, highlight, stamp, fill form fields, place signature/initials, or review markup together. Not for summarization or text extraction (use native Read instead).
documentation
Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.
development
Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Use when a new NDA arrives from sales or business development, when screening for embedded non-solicits, non-competes, or missing carveouts, or when deciding whether an NDA can be signed under standard delegation.