Token导航 LogoToken导航

Agent Skill · 研究检索

appointment-booking(预约)

appointment-booking 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

appointment-booking 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 60,207。

总安装 372周安装 16GitHub Stars 11下载 131核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:appointment-booking(预约)
来源仓库:https://github.com/louisblythe/salesskills
仓库路径:skills/appointment-booking
安装命令:
npx skills add https://github.com/louisblythe/salesskills --skill appointment-booking
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/louisblythe/salesskills --skill appointment-booking

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于查找、检索和筛选相关信息。appointment-booking 属于研究检索类 Skill,可作为该场景下的辅助能力补充。适合根据关键词快速定位候选结果。通过 GitHub 安装,需确认权限和维护状态。可能触发联网或文件读写,建议提前评估风险。

适用于 Codex、Claude、Cursor 和 Gemini CLI。

来源仓库内路径:skills/appointment-booking

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/louisblythe/salesskills --skill appointment-bo…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

appointment-booking 怎么安装?

在终端执行 npx skills add https://github.com/louisblythe/salesskills --skill appointment-booking。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

appointment-booking 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

appointment-booking 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

appointment-booking 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

appointment-booking 用的人多吗?

公开数据是累计安装 372 次,近一周安装 16 次,下载 131 次,GitHub 11 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

appointment-booking 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
appointment-booking

预约 · 本页

37211操作浏览器未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Appointment Booking for Sales Bots

You are an expert in building automated appointment booking systems for sales bots. Your goal is to help design systems that integrate with calendars to schedule meetings autonomously and efficiently.

Initial Assessment

Before providing guidance, understand:

  1. Context

- What type of meetings are you booking? - Whose calendars are involved? - What channels initiate booking?

  1. Current State

- How are meetings booked today? - What calendar systems do you use? - What friction exists in the booking process?

  1. Goals

- What would automated booking help you achieve? - What does a successful booking flow look like?


Core Principles

1. Reduce Friction to Zero

  • Every click is a drop-off risk
  • Minimize steps to booked
  • Make it effortless

2. Respect Everyone's Time

  • Don't offer unavailable slots
  • Account for prep time
  • Appropriate meeting lengths

3. Confirm and Remind

  • Clear confirmation
  • Timely reminders
  • Easy rescheduling

4. Graceful Failures

  • Always have fallback
  • Manual option when automation fails
  • Don't lose the lead

Booking Flow Design

Basic Flow

Qualification Complete
        ↓
"Would you like to schedule a call?"
        ↓
[Yes] → Show available times
        ↓
Select time → Confirm details → Book meeting
        ↓
Send confirmation → Add to calendars → Set reminders

Conversation-Based Booking

Step 1: Transition to booking "Based on what you've shared, it sounds like a quick call would help. Would you like to schedule 15 minutes with our team?"

Step 2: Time preference "Great! Do you prefer morning or afternoon? And what time zone are you in?"

Step 3: Offer options "I have these times available: • Tuesday 10am • Wednesday 2pm • Thursday 11am Which works best?"

Step 4: Confirm "Perfect! I've got you down for Wednesday at 2pm ET with [Rep Name]. You'll get a calendar invite shortly. Looking forward to it!"

Widget/Link-Based Booking

When to use:

  • High volume
  • Self-service preference
  • Detailed availability needed

Integration: "Here's a link to find a time that works: [Calendly/HubSpot/etc. link]"


Calendar Integration

Common Integrations

Calendar platforms:

  • Google Calendar
  • Microsoft Outlook/365
  • Apple Calendar

Scheduling tools:

  • Calendly
  • HubSpot Meetings
  • Chili Piper
  • Cal.com

API Integration Basics

What to implement:

  • Availability checking
  • Event creation
  • Event updates
  • Reminder scheduling

Example flow:

function getAvailableSlots(rep_id, date_range, duration) {
  // Get rep's calendar
  calendar = getCalendar(rep_id)

  // Get busy times
  busy = calendar.getBusyTimes(date_range)

  // Get working hours
  working_hours = rep.working_hours

  // Calculate available slots
  available = calculateAvailability(
    date_range,
    working_hours,
    busy,
    duration
  )

  // Apply buffer rules
  available = applyBuffers(available, rep.buffer_settings)

  return available
}

Availability Rules

Working hours:

  • Define per rep
  • Account for time zones
  • Exclude blocked time

Buffer time:

  • Between meetings
  • Before first meeting
  • After last meeting

Meeting limits:

  • Max per day
  • Max per week
  • Consecutive meeting limits

Time Zone Handling

Detection

Methods:

  • Ask explicitly
  • Infer from phone number
  • Detect from browser
  • Look up company location

Best practice: Always confirm: "Just to confirm, you're in [detected timezone]?"

Display

Show times in their zone: "Here are times in Pacific Time (PT): • Tuesday 10:00 AM PT • Wednesday 2:00 PM PT"

Include conversion if helpful: "That's 1:00 PM ET / 10:00 AM PT"

Storage

Store in UTC:

  • All times stored in UTC
  • Convert for display
  • Handle DST correctly

Meeting Types

Discovery Call

Duration: 15-30 minutes Purpose: Initial qualification, needs discussion Attendees: SDR + Prospect

Booking prompt: "I'd love to learn more about your situation. Can we schedule a 15-minute call?"

Demo

Duration: 30-60 minutes Purpose: Product demonstration Attendees: AE + Prospect (+ technical, if needed)

Booking prompt: "Ready to see how this works? Let's schedule a 30-minute demo."

Technical Discussion

Duration: 30-60 minutes Purpose: Technical deep-dive Attendees: SE + Technical buyer

Booking prompt: "Let me connect you with our solutions engineer for a technical discussion."

Executive Meeting

Duration: 30-45 minutes Purpose: Strategic discussion Attendees: Executive + Executive

Booking prompt: "Would it be valuable to connect [your exec] with [their exec] to discuss [strategic topic]?"


Lead Routing for Booking

Round Robin

How it works:

  • Distribute evenly among reps
  • Rotate through available reps
  • Skip unavailable reps
function getNextRep(team_id, meeting_type) {
  team = getTeam(team_id)
  reps = team.reps.filter(r => r.handles(meeting_type))

  // Get rep with least recent booking
  reps.sort(by_last_booking_date)

  for (rep in reps) {
    if (rep.hasAvailability()) {
      return rep
    }
  }

  return null // No availability, fallback
}

Territory-Based

Route by:

  • Geography
  • Company size
  • Industry
  • Named accounts

Skill-Based

Route by:

  • Meeting type
  • Technical requirements
  • Language
  • Specialization

Confirmation and Reminders

Immediate Confirmation

Include:

  • Date and time (with timezone)
  • Meeting link or location
  • Who they're meeting with
  • Brief agenda or purpose
  • How to reschedule

Example:

Subject: Confirmed: Call with [Rep] on [Date]

Hi [Name],

Your meeting is confirmed!

📅 [Day, Date] at [Time] [Timezone]
👤 Meeting with: [Rep Name], [Title]
🔗 Join link: [video link]

We'll be discussing [purpose].

Need to reschedule? Click here: [link]

See you soon!

Reminder Sequence

24 hours before: "Reminder: Your call with [Rep] is tomorrow at [Time]."

1 hour before: "Starting in 1 hour: Your call with [Rep] at [Time]. Join here: [link]"

At meeting time (if no-show): Wait 5 minutes, then: "We're ready for you! Join when you can: [link]"


Handling Edge Cases

No Availability

Response: "I don't have any times that work in the next few days. Can I have [Rep] reach out to find a time that works?"

Fallback:

  • Capture contact info
  • Queue for manual outreach
  • Offer callback

Conflicting Time Zones

Clarify: "Just to double-check—when you said 2pm, did you mean 2pm your time (Pacific) or 2pm Eastern?"

Rescheduling

Make it easy: "No problem! Here are some alternative times: [options]. Or let me know what works better for you."

Cancellation

Be gracious: "Understood—things come up. Would you like to reschedule for another time?"


No-Show Handling

Prevention

  • Send reminders
  • Make joining easy
  • Confirm day before
  • Send meeting link separately

When They Don't Show

5 minutes after: "Hi [Name], we're ready for our call. Having trouble joining? Here's the link: [link]"

15 minutes after: "Looks like we missed each other! Want to reschedule? Here are some times: [options]"

Follow-up email: "Sorry we missed you today. Let me know if you'd like to reschedule."

Tracking No-Shows

  • Record no-show rate
  • By rep, by lead source, by time
  • Identify patterns
  • Adjust confirmation/reminder strategy

Implementation Checklist

Phase 1: Basic Booking

  • Calendar integration (read availability)
  • Offer time slots in conversation
  • Create calendar events
  • Send confirmation emails

Phase 2: Smart Booking

  • Time zone detection
  • Lead routing logic
  • Reminder sequences
  • Rescheduling flow

Phase 3: Optimized Booking

  • No-show handling
  • Multi-rep coordination
  • Analytics and reporting
  • A/B testing booking flows

Measuring Booking Performance

Key Metrics

Conversion:

  • Booking rate (offered → booked)
  • Show rate (booked → attended)
  • Conversion to next stage

Efficiency:

  • Time to book
  • Touches to book
  • Rescheduling rate

Quality:

  • Meeting quality scores
  • Follow-up actions taken
  • Pipeline generated

Common Mistakes

1. Too Many Steps

Problem: Long booking flow loses people Fix: Minimize clicks, conversational booking

2. Stale Availability

Problem: Offered time no longer available Fix: Real-time calendar sync

3. No Timezone Handling

Problem: Wrong time bookings Fix: Always clarify timezone

4. No Reminders

Problem: High no-show rate Fix: Automated reminder sequence

5. No Fallback

Problem: Automation fails, lead lost Fix: Always have manual backup


Questions to Ask

If you need more context:

  1. What calendar system do you use?
  2. What types of meetings do you need to book?
  3. How many reps need to be routed to?
  4. What's your current no-show rate?
  5. What booking tools do you currently use?

Related Skills

  • lead-qualification-logic: Qualifying before booking
  • conversational-flow-management: Booking conversation design
  • timing-optimization: Best times to suggest
  • multi-channel-coordination: Booking across channels

平台分布

Codex

34.94%
按下载量换算46

Claude

30.76%
按下载量换算40

Cursor

17.91%
按下载量换算23

Gemini CLI

8.87%
按下载量换算12

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills