Meeting prep: person and company
Before a call, look up who the user is meeting and the company they work for, and return a short brief: role, seniority, background, company basics and a few talking points grounded in what the data says.
One command.
Installs into ~/.claude/skills for Claude Code. In Claude, upload the downloaded file under Settings → Capabilities → Skills.
npx ravn skill install meeting-prep
When to use
- "I'm meeting jane@acme.com at 3pm, who is she?"
- The user pastes a calendar invite, an email signature or a LinkedIn URL and wants context.
- For a deeper company-only brief, use account-research-brief.
Before you start
- Check the connection: call
get_accountwith{}or runnpx ravn whoami. - The person and company lookups (
reverse_email_lookup,reverse_linkedin_lookup,search_business_profile_by_name,domain_to_company) need your own provider key connected — runravn keys add pdlfirst; these tools run on your own provider account. If a tool returns 403provider_key_required, stop and tell the human to add their key.scrape_websiteis ours and needs no key. Every call is one lookup; misses are free. - Work out what you were given: an email, a name plus company, or a LinkedIn URL. Each has its own lookup.
Steps
- Get the person profile with the tool that matches the input: - Email:
reverse_email_lookupwith{ "email": "jane@acme.com" }. - LinkedIn URL:reverse_linkedin_lookupwith{ "linkedin_url": "https://www.linkedin.com/in/janedoe" }. - Name and company:search_business_profile_by_namewith{ "name": "Jane Doe", "company": "acme.com" }. - If
statusisnot_found, try the next input you have (for example name plus company from the email signature). If all miss, say so and continue with the company only. - From the person, use
full_name,title,headline,seniority,city,state,country,industry,linkedin_url,companyandlast_updated_at. Iflast_updated_atis old, warn that the title may have changed. - Get the company. Use
company.domainfrom the person, or the email's domain if it is not a free provider.
{ "domain": "acme.com" }
Call domain_to_company for size, industry, founded and location, then scrape_website for the site description and technologies. 5. Write three to five talking points that link the user's goal for the meeting to facts you found (for example the person's department, the company's size, a technology on their site). Ask the user for the meeting goal if you do not know it. 6. Keep the brief to what fits on one screen.
Output
A short Markdown brief:
- Who: full name, title, seniority, location, LinkedIn URL, and how fresh the record is.
- Company: name, domain, industry, size and employee count, founded, HQ, one-line description from their site.
- Context: department, headline, notable technologies on the site.
- Talking points: three to five bullets, each tied to a fact above.
- Unknowns: what was not found, and anything to ask in the meeting.
Rules
- Use this only for business meetings. Do not profile people for personal reasons.
- If the person has opted out, the lookup will not return them; do not try to work around that. See /privacy#optout.
- No FCRA uses: never use a brief to screen a candidate, tenant, borrower or policy holder.
- Never present a guess as a fact. If a field is missing, say it is missing.
- On a 429
fair_use_exhaustedor a 403provider_key_required, stop and tell the human. Deliver whatever you already found.
Example prompt
I have a call in 20 minutes with marcus.bell@brightpath.io. Who is he, what does BrightPath do, and what should I bring up?
More skills
Install them all with npx ravn skill install --all.