agentleFS
prosyo-aiprosyo-ai/gtm-skill/skills/meeting-booking-reply/SKILL.md

meeting-booking-reply

Skill13 starsChanged 24 days agoMITView on GitHub

Use this skill when a prospect shows interest and you need to turn it into a booked, confirmed meeting: \"they said yes, what do I send\", \"book the meeting\", \"write the meeting confirmation\", \"reduce back and forth scheduling\". Writes the booking reply with specific times or a link, the calendar invite title and agenda, the confirmation and the day-before reminder, so the meeting gets booked fast and actually happens. Handles time zones, assistants and multiple attendees.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this the moment a prospect says yes.

    line 16
  2. Distinctive:

    Multiple attendees: ask who else should join and offer to send them a one-line context.

    line 44
  3. Distinctive:

    MUST confirm the time zone explicitly.

    line 70
  4. Distinctive:

    MUST send a calendar invite with an agenda and a working video link.

    line 71
  5. Distinctive:

    NEVER book a meeting the prospect did not agree to.

    line 72
  6. Distinctive:

    NEVER add attendees from their company without asking.

    line 73

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this the moment a prospect says yes. Interest fades fast; every extra email of back and forth loses some meetings, and a vague invite causes no-shows.

Inputs

  • The positive reply and thread.
  • Availability (2-3 specific slots) or a booking link.
  • Meeting purpose and length; who else should attend.

The play

1. Reply fast with two options

Within the hour if possible. Offer two specific times in their time zone, plus the link as a fallback. Choices beat open questions ("When works for you?").

Great, Maya. 20 minutes on how your close runs and what Contoso changed. Does Tuesday 10:00 or Wednesday 14:00 (your time) work? If neither, pick any time here: <link>

2. Send a calendar invite that sells the meeting

  • Title: "<Their company> + <Your company>: <topic>" (e.g. "Lumen + Acme: month-end close").
  • Description: three bullet agenda, what they get from it, the video link, and one line on how to reschedule.
  • Their time zone in the invite; never assume.

3. Confirm in writing

A short confirmation that restates the outcome they will get, and asks one prep question ("Anything specific you want to cover?") which makes them invest in the meeting.

4. Remind the day before

A short, useful reminder: the agenda, a relevant one-line insight, the link. Not "just confirming we're still on".

5. Handle edge cases

  • Assistant schedules: give them two slots and the agenda; copy the prospect.
  • Multiple attendees: ask who else should join and offer to send them a one-line context.
  • Booked 2+ weeks out: send one value touch in between (a short story or resource) to keep it alive.

Templates

Invite description

What we'll cover (20 min):
- How month-end close runs at Lumen today
- What Contoso changed to close in 4 days
- Whether the same approach fits your team
Need to move it? Reply to this invite and I'll find a new time.

Day-before reminder

Hi Maya, looking forward to tomorrow at 10. I'll bring the approval checklist Contoso used. Link: <video link>

What good looks like

  • Booked within one or two emails of the yes.
  • Invite title and agenda make the value obvious to anyone who sees the calendar.
  • Show rate 80%+ for meetings booked within a week.
  • The common mistake is "When works for you?", followed by four emails of scheduling while interest cools.

Rules

  • MUST confirm the time zone explicitly.
  • MUST send a calendar invite with an agenda and a working video link.
  • NEVER book a meeting the prospect did not agree to.
  • NEVER add attendees from their company without asking.

Example prompts

  • "They replied 'sure, let's chat next week'. Write the booking reply."
  • "Write a calendar invite and confirmation for a discovery call with a CFO."
  • "Our show rate is 60%. Fix our confirmation and reminder emails."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.