MCP Skills

---
name: "meeting-prep"
description: Build a meeting prep report for each customer or prospect call on the user's calendar, grounded in live Starbridge buyer data (Signal Score, Fit Score, signals, team activity, contacts) and the user's CRM. Use whenever the user asks to prep for today's meetings or calls, "run my meeting prep", "prep me for my calls today", "what do I need to know before my meetings", "meeting prep for [buyer]", or wants to set up a recurring morning prep report. Also use when the user asks for prep on a single upcoming call with a public-sector buyer, even if they don't say "report" or "prep".
---

# Meeting prep

Produce one prep brief per external customer or prospect meeting on the user's calendar, using Starbridge as the main source of buyer intelligence and the user's CRM where it's connected. The goal is a report a rep can read in about three minutes per meeting before the call.

## What this needs

- **Starbridge MCP** (required).
- **A calendar connector** (required for the daily report), such as Google Calendar or Outlook. If none is connected, tell the user and stop. For a single-meeting request, ask for the buyer name instead.
- **A CRM connector** (optional), such as Salesforce or HubSpot. Starbridge's synced CRM data is used either way.
- **A call recorder** (optional), such as Gong, Chorus, Zoom, Fathom, or Granola, for transcripts of past calls.
- **Email** (optional), such as Gmail or Outlook, for recent threads with the buyer.

The optional connectors add detail when they're available. If one isn't connected, skip it without comment.

## Step 1: Find today's customer meetings

Pull today's events in the user's time zone. Keep a meeting if at least one attendee has an email domain outside the user's own company. Skip internal-only meetings, declined events, all-day events, holds, and events with no attendees.

For each meeting you keep, identify the buyer:

1. Match external attendee email domains to a Starbridge buyer using buyer search. Public-sector domains vary a lot (for example `k12.xx.us`, `.gov`, district or department subdomains), so if an exact domain match fails, try the organization name the domain points to.
2. If there's no domain match, look for an organization name in the meeting title or description.
3. If a CRM is connected, check for a matching account.

If attendees come from more than one buyer (a consortium or a county and a district), prep each buyer. If the external attendees are from a commercial company with no Starbridge buyer match, they're likely a partner or vendor: list the meeting under "Other external meetings" without a full brief. If you can't identify the buyer with reasonable confidence, include the meeting with a one-line note on what you tried. Don't guess.

## Step 2: Gather data for each buyer

From Starbridge:

- Buyer summary, key attributes, and hierarchy (parent district, county, or system).
- Signal Score tier (Hot, Warm, Cool, None) and the signals behind it.
- Fit Score (0–100) and the attributes that drive it most. If the organization hasn't set up account scoring, skip the scores without comment.
- Recent signals from the last 90 days: board meetings, RFPs, purchases, contract awards.
- Open RFPs, contracts expiring in the next 12 months, and competitor or complementary vendor presence.
- The team's recent activity on the buyer in Starbridge, such as signal statuses and sequence enrollments.
- CRM records Starbridge has synced for the buyer.
- Contacts at the buyer, especially those matching the organization's ICP titles.

From the CRM, if connected:

- Account owner and the rest of the account team.
- Open opportunities: stage, amount, close date, created date, and how long the deal has been in its current stage.
- Recently closed opportunities from the last 12 months, won or lost, with the loss reason if recorded. A recent loss or a renewal changes how the call should go.
- Any qualification fields the team uses (for example MEDDICC or SPICED fields, next step, decision date). Use whatever fields exist; don't assume a methodology.
- Recent activities, notes, and contacts with their roles.

When the direct CRM and Starbridge's synced data disagree, use the direct CRM, since it's more current, and mention the difference only if it matters for the call.

From the call recorder, if connected:

- Find the most recent calls with the buyer (up to 10 from the last 12 months), with date, title, and participants. Use these for the call count, the date of the last call, and who has been on calls. Don't list them in the report.
- Read the transcripts of the 3 most recent calls. Look for what was discussed, action items or promises made by either side, questions left unanswered, objections or concerns, competitor mentions, and agreed next steps.
- If full transcripts aren't available, use call summaries or highlights and say so in the report.

From email, if connected: threads with anyone at the buyer from the last 14 days. Look for outstanding asks, promised follow-ups, and context the calls don't cover.

### Contacts and credits

Don't enrich locked contacts on your own, and never during a scheduled run. Enrichment costs credits (2 per contact). Show locked ICP-title contacts by title only and offer to unlock them when the user reads the report. Enrich only when the user asks.

## Step 3: Write the report

Use plain, direct language. Keep sections short, and when a section has nothing, say so in a few words ("No CRM activity in the last 90 days") rather than padding it.

That applies only when you checked a source and found nothing. When a source isn't available (an optional connector isn't set up, or a Starbridge feature such as account scoring isn't turned on), leave out the sections, lines, and fields that depend on it, and don't mention that it's missing anywhere in the report. For example, with no call recorder, drop "Last conversation" or fill it from email and CRM notes. Without account scoring, drop the "Fit" section and the Fit Score from the summary line and headings. Date every signal and link to it in Starbridge where a link is available. Order meetings by start time.

Use this structure:

```
# Meeting prep: [Weekday, Month D]

[N] customer meetings today.
- [Time] · [Buyer] · Signal: [tier] · Fit: [score] · [the one thing to know]
- ...

---

## [Time] · [Buyer name]: [Meeting title]

**Attendees:** [buyer-side names and titles]; [internal attendees]

### Deal context
[Open opportunity: stage, amount, close date, owner, days in current stage. What should be established by this stage based on the team's qualification fields, and what's missing. Any recently closed opportunities.]
[Or: "No open opportunity, likely a first conversation."]

### Buyer summary · Signal Score: [Hot / Warm / Cool / None]
[2–4 sentences on what's going on at the buyer and why the score is where it is.]

### Fit · Fit Score: [0–100]
[1–2 sentences on the strongest fit attributes and any gaps. Competitor and complementary vendor presence.]

### Recent activity
**Buyer activity (Starbridge):** [up to 5 dated signals, newest first]
**Your team's activity:** [last touch from CRM, email, or calls; Starbridge sequences and signal statuses]

### Last conversation
[Date and attendees of the most recent call, and 2–3 sentences on what was discussed and agreed. Note how many calls there have been in the last 12 months.]
[Relevant email threads from the last 14 days, one line each.]

### Open threads
[Action items, promises, and unanswered questions from recent calls and emails, noting who owes what.]

### Procurement and timing
[Open RFPs, contracts expiring in the next 12 months, upcoming board meetings, fiscal year or budget timing.]

### Key contacts
[Meeting attendees first, with title and role.]
[Other contacts from the CRM or previous conversations.]
[ICP-title contacts from Starbridge. Unlocked: name, title, email. Locked: title only, marked "available to unlock".]

### Suggested talking points
[2–3 points, each tied to a specific signal, open thread, or deal gap above.]
[1–2 questions to fill the biggest gaps.]

### Watch-outs
[Risks worth knowing before the call: competitor mentions, objections from transcripts, a stalled stage, a slipped close date, a recent loss, or a key contact who left.]

### Gaps
[Anything you looked for in an available source but couldn't find or verify, in one or two lines. Don't list unconnected sources or features that aren't set up. Omit this section if there's nothing to say.]

---

## Other external meetings
[Time · organization · one line, for partner or vendor meetings and anything you couldn't match.]
```

If there are no customer meetings today, send a one-line note saying so.

For existing customers (an open renewal or a closed-won account in the CRM), weight the brief toward renewal timing, expansion signals, and recent support or usage notes rather than first-call discovery.

## Step 4: Deliver

Deliver to the destination the user chose at setup. If none was chosen, deliver in the chat.

- **Chat thread:** Post the report as the response. In a scheduled run, this becomes its own conversation or session the user can open.
- **Email:** Send the report to the user's own email address only, using their connected Gmail or Outlook. Use the subject "Meeting prep: [Weekday, Month D] ([N] customer meetings)". Never send to buyers, attendees, or anyone else. If the email connector can only create drafts, create a draft and note that in the chat.
- **Slack:** Send the report as a DM to the user only.

If the chosen destination isn't available during a run (for example, the email connector was disconnected), post the report in the chat and add a one-line note that delivery failed and why.

## Step 5: Offer a daily schedule

When the user runs this skill themselves and the client supports scheduled tasks (for example, Cowork), end the response by asking once whether they'd like the report to run automatically every weekday morning. Ask this even when there were no customer meetings today. Keep it to one short question, and if the client offers a tappable-options tool, use it.

Don't ask if:

- This is a scheduled run.
- A recurring meeting prep task already exists.
- The user already declined earlier in the conversation.
- The client doesn't support scheduled tasks.

If they say yes, follow "Setting up the weekday 7am report" below.

## Setting up the weekday 7am report

When the user asks to set this up, or says yes to the offer in Step 5, confirm two things: their time zone and where the report should go (chat, email to themselves, or Slack DM). The report runs Monday through Friday unless the user asks for a different schedule. Check that the calendar connector, the Starbridge MCP, and the delivery connector are all connected before creating the task.

Then create a recurring task with the client's scheduling feature that runs at 7:00am on weekdays in their time zone, with a prompt like: "Run meeting prep for today's calendar and email it to me at [address]." If the client asks for an approval mode, tell the user that the email or Slack send needs to be allowed for the task to run unattended.

If the client doesn't support scheduled tasks, tell the user and suggest running the prompt each morning instead.

---
name: slack-digest
description: Post a short digest of the user's top Starbridge Feed signals to a Slack channel or DM, grouped by urgency (act today, this week, monitor) with a next step for anything urgent, and set it up to run every weekday morning. Use whenever the user asks for a Slack digest, a daily or morning signal digest, to "post my feed to Slack", "send top signals to #channel", or to have Starbridge signals show up in Slack automatically. Also use for a one-off "what are today's top signals" when the user wants the result posted to Slack.
---

# Slack digest

Post a short digest of the top signals from the user's Starbridge Feed to Slack, grouped by urgency. It's the same triage as asking Claude to sort the Feed each morning, except it posts on a schedule so nobody has to remember to ask. The main audience is sales leaders and RevOps posting to a team channel, but it works as a personal DM too.

## What this needs

- **Starbridge MCP** (required).
- **Slack connector** (required to post). If it isn't connected, tell the user and, for a manual run, show the digest in the chat instead.

The digest is built from the Feed of the person who runs it: the signals from the Bridges they're subscribed to. When it posts to a team channel, it shows that person's Feed, not every Bridge in the organization. Mention this once during setup so the user can subscribe to the Bridges the team cares about.

## Settings

Use these defaults unless the user chose something else at setup:

- **Destination:** the Slack channel named at setup (for example #sales-signals), or a DM to the user.
- **Number of signals:** up to 3 in each group, so up to 9 in total.
- **Schedule:** 7:00am, Monday through Friday, in the user's time zone.

## Step 1: Pull the Feed

Follow Starbridge's `buyer-signals` skill for the cross-buyer Feed. Call `listTopRecentSubscribedSignals` with status `New`, sorted by Hotness, over the last 7 days, with a page size of about 30 so there's room to fill each group.

Keep signals that came in since the previous digest: since yesterday morning on Tuesday through Friday, and since Friday morning on Monday. Use the row's signal date or the date it was added. Don't fill the digest with signals from earlier days that were probably posted already.

If the user has no Bridge subscriptions, the Feed will be empty. On a manual run, say so and suggest subscribing to the Bridges they want in the digest. On a scheduled run, post the no-signals line below.

## Step 2: Pick and group the signals

Drop duplicates from the fresh signals (the same event at the same buyer from two Bridges counts once). Then put each in one of three groups:

- **Act today:** time-bound and close. An open RFP or bid with a near due date, funding just approved for a specific need, a board vote or decision this week, or an urgent problem the buyer is trying to fix now.
- **This week:** worth reaching out about soon, with no hard deadline. A new initiative, a new or changed leadership role, a budget approval, a strategic plan that names a relevant priority.
- **Monitor:** worth tracking, not acting on yet. An item tabled or pushed to a later budget cycle, early discussion, a contract that expires more than a few months out.

Keep up to 3 signals in each group, choosing the hottest ones. A group can have fewer than 3, and a group with no signals is left out. Don't move a signal into a group just to fill it.

## Step 3: Write the digest

Keep it easy to scan. One line per signal: the buyer, what happened, and the signal date if it isn't from today. Link the buyer name to the signal in Starbridge using the row's `url`. Apart from the "See all signals" link below, only use links the tool returned.

Use Slack formatting (`*bold*`, `<url|text>`), not Markdown headers:

```
*Starbridge Daily Digest · [Weekday, Month D]*

*Act today*
• <url|[Buyer]> — [what happened]
   ↳ Next step: [the single best next step]
• <url|[Buyer]> — [what happened]
   ↳ Next step: [the single best next step]

*This week*
• <url|[Buyer]> — [what happened]

*Monitor*
• <url|[Buyer]> — [what happened]

<https://dashboard.starbridge.ai/|See all signals in Starbridge>
```

Within each group, list signals hottest first. Always end the digest with the "See all signals in Starbridge" link on its own line.

For each signal in Act today, add the single best next step on the line below it. Make it specific to the signal: who to contact, about what, and by when if there's a deadline (for example, "Reach out to the IT Director about the records-management replacement before the Nov 20 bid deadline"). Base it on what the signal says. If there isn't enough detail for a specific step, leave it out rather than writing a generic one. Signals in This week and Monitor don't get a next step.

If there are no new signals, post one line, "No new Starbridge signals since [yesterday / Friday].", followed by the "See all signals in Starbridge" link.

Write each line from what the signal says. Don't add scores or commentary the Feed doesn't support.

## Step 4: Post to Slack

Post the digest with the Slack connector to the destination chosen at setup. If none was chosen, show the digest in the chat and ask where it should go.

- **Channel:** post to that channel only. Don't post to any other channel, and don't @-mention people.
- **DM:** send to the user only.

If the post fails (the connector was disconnected, or the channel was renamed or archived), show the digest in the chat with a one-line note on why it didn't post.

## Step 5: Offer a weekday schedule

When the user runs this skill themselves and the client supports scheduled tasks (for example, Cowork), end the response by asking once whether they'd like the digest to post automatically every weekday morning. Keep it to one short question, and if the client offers a tappable-options tool, use it.

Don't ask if:

- This is a scheduled run.
- A recurring digest task already exists.
- The user already declined earlier in the conversation.
- The client doesn't support scheduled tasks.

If they say yes, follow "Setting up the weekday digest" below.

## Setting up the weekday digest

When the user asks to set this up, or says yes to the offer in Step 5, confirm:

1. **Where it goes:** a channel name, or a DM to themselves. For a channel, check that it exists and read its topic and description first; if they suggest the digest belongs somewhere else, tell the user before going further.
2. **Their time zone.**

Use the defaults for everything else (up to 3 signals per group, 7:00am, Monday through Friday) unless the user asks for something different. Check that the Starbridge MCP and Slack are both connected, and remind the user that the digest reflects their own Bridge subscriptions.

Before creating the task, run the digest once and show it in the chat as a preview, without posting it, so the user can check the format. Then create a recurring task with the client's scheduling feature for 7:00am on weekdays in their time zone, with a prompt like: "Run the Slack digest and post today's top Starbridge signals to #sales-signals, up to 3 per urgency group." If the client asks for an approval mode, tell the user that sending Slack messages needs to be allowed for the task to run unattended.

If the client doesn't support scheduled tasks, tell the user and suggest running the prompt each morning instead.