| name | make-a-warm-introduction |
| description | Find a credible path between people and prepare a considerate warm introduction using approved relationship context. Use when someone wants to connect a founder, investor, customer, candidate, expert, partner, or colleague; verify the relationship, protect private context, and keep drafting, asking, sending, and recording the introduction separately controlled. |
Make a Warm Introduction
Help the user make a connection that is useful to both sides. A shared contact or old message is a
lead to inspect, not proof of a current relationship or willingness to introduce.
1. Understand the connection
Identify who should meet, why the connection could help each person, the timing, and whether the
user wants to find a path, ask an intermediary, draft the introduction, or send an approved message.
Resolve ambiguous identities before searching or drafting.
Use only the context needed for this connection. Sensitive investment, customer, candidate,
employment, health, financial, or personal details stay private unless the user has approved what
may be shared with each person.
2. Find and verify a credible path
Search approved contacts, email, calendar, meetings, CRM, team messages, professional networks,
files, memory, and relevant public profiles. Use visible logged-in sites when relationship evidence
lives there, keeping the path inspectable for the user.
For each plausible path, distinguish:
- a verified direct relationship from a shared affiliation or inferred connection;
- recent interaction from stale history;
- evidence that the intermediary knows each side from evidence that they merely appear connected;
- the likely relevance of the introduction from the strength of the relationship; and
- private context from details safe to share.
Never claim that someone is close, willing, or able to introduce without evidence. If no credible
path exists, say so and offer a respectful direct approach only when useful.
3. Recommend the best approach
Present the strongest path or a small set of alternatives with the evidence, freshness, likely
friction, and why each may work. Recommend whether to ask the intermediary first, seek consent from
one or both sides, prepare a double-opt-in introduction, or avoid the connection.
The user owns the relationship judgment. Do not optimize only for reach; consider relevance,
burden, confidentiality, conflicts, and the cost of a poorly framed ask.
4. Prepare the messages
Draft only what the chosen approach needs. This may include:
- a concise ask to the intermediary, with an easy way to decline;
- a forwardable note that explains who the requester is and why the meeting may be useful;
- a double-opt-in message for each side; or
- the final introduction after consent is clear.
Use the user's established voice and verified facts. Share the minimum useful context, state why
the connection may help both sides, avoid manufactured familiarity, and make the next step easy.
5. Send and verify only the approved action
Treat finding a path, drafting an ask, contacting an intermediary, contacting either participant,
sending the introduction, scheduling, and updating a record as separate actions. Before sending,
confirm the sender identity, recipients, channel, exact message, and context being disclosed unless
an active scoped permission already covers them.
After an approved send, verify the recipients and delivery state in the actual destination. Do not
treat a draft or accepted API request as proof of delivery. Use strawberry/sales/keep-crm-updated
for separately approved CRM changes and strawberry/operations/close-open-loops when a promised
introduction needs later follow-through.
Use feedback to remember the user's tone, consent preference, trusted relationship signals, and
review behavior. Save a custom or team skill only when those choices prove durable; warm
introductions usually remain on demand rather than becoming an automated Routine.
