Token导航 LogoToken导航

Agent Skill · 研究检索

sales-meeting-scheduler(销售会议安排)

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

sales-meeting-scheduler 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,674 个 Skill 里排第 41,189。

总安装 1,211周安装 52GitHub Stars 13下载 424核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-meeting-scheduler

这个 Skill 是做什么的

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

sales-meeting-scheduler 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于关键词驱动的信息搜索与筛选任务场景。通过 npx skills add 命令从 GitHub 仓库安装并使用。

安装前需评估权限、维护状态及可能的联网或文件操作。建议结合原始文档核验具体实现逻辑。

来源仓库内路径:skills/sales-meeting-scheduler

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

sales-meeting-scheduler 怎么安装?

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

sales-meeting-scheduler 支持哪些 AI 工具?

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

sales-meeting-scheduler 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

sales-meeting-scheduler 是免费的吗?

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

sales-meeting-scheduler 用的人多吗?

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

sales-meeting-scheduler 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 同时适配 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调用外部服务未明确有提醒
sales-meeting-scheduler

销售会议安排 · 本页

1,21113需要联网未明确有提醒

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

SKILL.md 原文

Schedule Sales Meetings Efficiently

Help the user set up and optimize meeting scheduling for their sales workflow — from booking page creation and round-robin assignment through reminder sequences, no-show recovery, and meeting page optimization. This skill is tool-agnostic and applies to any scheduling platform (Calendly, Chili Piper, HubSpot Meetings, Cal.com, SavvyCal, Yesware).

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

  1. What's your scheduling challenge?

- A) Setting up booking links for the first time - B) Configuring round-robin or routing for a team - C) Reducing no-shows - D) Optimizing meeting page conversion - E) Choosing a scheduling tool - F) Something else

  1. What type of meetings?

- A) Discovery/qualification calls - B) Product demos - C) Follow-up meetings - D) Onboarding/kickoff calls - E) Mix of types

  1. Team size?

- A) Just me (solo seller) - B) Small team (2-5 reps) - C) Mid-size team (6-20) - D) Large team (20+)

  1. What scheduling tool do you use?

- A) Yesware Meeting Scheduler - B) Calendly - C) Chili Piper - D) HubSpot Meetings - E) Cal.com - F) SavvyCal - G) Vimcal - H) None yet - I) Other

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Step 2 — Strategy and best practices

Read references/platform-guide.md for detailed module documentation, pricing, integrations, and data model.

*You no longer need the platform guide details — focus on the user's specific situation.*

Step 3 — Actionable guidance

Based on the user's context, provide:

  1. Step-by-step setup for their chosen tool — specific clicks and configurations
  2. Optimization recommendations based on their challenge (no-shows, conversion, routing)
  3. Metrics to track with targets specific to their team size and meeting type
  4. 30-day improvement plan if they're fixing an existing problem

Setup checklist (universal)

  • Create event types for each meeting type (discovery, demo, follow-up)
  • Set working hours and buffer times
  • Configure calendar sync (Google Calendar or Outlook)
  • Set up video conferencing integration (Zoom, Google Meet, or Teams)
  • Create reminder sequence (24hr + 1hr before)
  • Design booking page (title, description, branding, minimal form fields)
  • Connect to CRM (Salesforce or HubSpot)
  • Set up round-robin routing (if team)
  • Test the full flow — book a test meeting as if you were a prospect
  • Share booking links in email signatures, cadences, and website

Gotchas

  • Don't skip reminder sequences. No-show rates jump from 10% to 30%+ without reminders. Always set up at least a 24hr and 1hr reminder. This is the single highest-ROI scheduling optimization.
  • Don't use long booking pages. Every extra field reduces conversion. Minimum: name, email. Everything else is optional or can be pulled from enrichment post-booking. Three qualifying questions is the absolute max.
  • Don't ignore timezone display. If the booking page shows times in YOUR timezone instead of the booker's, you'll get mis-booked meetings and confused prospects. Always verify timezone auto-detection is working.
  • Don't set up round-robin without weighting. Equal distribution sounds fair but ignores capacity. A rep with 30 meetings this week shouldn't get the same allocation as one with 10. Weight by current load or quota attainment.
  • Don't forget CRM integration. Every booked meeting should auto-create/update a CRM record. Manual logging means meetings fall through the cracks, pipeline data is inaccurate, and managers can't report on meeting volume.
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Before recommending a specific platform skill

This skill covers a strategy domain across many platforms. Before pointing the user to any specific platform skill (any /sales-{platform} listed in ## Related skills, e.g., /sales-mailshake, /sales-klaviyo, /sales-apollo), read that platform skill's actual SKILL.md first. The 1-line description in ## Related skills is enough to *identify* a candidate — it's not enough to *commit* to it or to write a prompt that invokes it well.

How to read it:

  • If ~/.claude/skills/{skill-name}/SKILL.md exists locally, Read it.
  • For sales-* skills, WebFetch directly from this repo: https://raw.githubusercontent.com/sales-skills/sales/main/skills/{skill-name}/SKILL.md — e.g., for sales-mailshake: https://raw.githubusercontent.com/sales-skills/sales/main/skills/sales-mailshake/SKILL.md.
  • For non-sales-* skills (third-party), look up {org}/{repo} in ~/.claude/skills/sales-do/references/skill-sources.md if installed and fetch the same skills/{skill-name}/SKILL.md path under that repo.

After reading, ground your recommendation in something concrete from the SKILL.md (its scope, a sub-flow, its argument-hint shape, or a "Do NOT use for..." negative trigger). Align any generated invocation with the platform skill's argument-hint. If the platform skill turns out not to fit the user's situation, swap to another or handle the question here directly rather than recommending a poor fit.

Related skills

  • /sales-qualified — Qualified platform help (Piper Meetings instant booking from chat)
  • /sales-yesware — Yesware platform help including Meeting Scheduler setup
  • /sales-cadence — Design outbound cadences that drive meeting bookings
  • /sales-lead-routing — Lead routing rules (complementary to meeting round-robin)
  • /sales-integration — Connect scheduling tools to CRM and other sales tools
  • /sales-mixmax — Mixmax platform help (for Mixmax-specific setup)
  • /sales-lindy — Lindy platform help (AI agent builder with natural language scheduling via iMessage/Slack)
  • /sales-vimcal — Vimcal platform help (keyboard-first calendar with drag-to-share availability and time zone management)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill.

Examples

Example 1: Solo seller setting up Calendly for discovery calls

User says: "I'm a solo AE and need to set up Calendly for booking discovery calls with inbound leads." Skill does:

  1. Recommends Calendly Standard plan for a solo seller
  2. Walks through creating a 30-min discovery call event type with proper title, description, and branding
  3. Configures availability — working hours, 15-min buffer, 4-hour minimum notice, 2-week rolling window
  4. Sets up Zoom integration for auto-generated meeting links
  5. Creates a reminder workflow (24hr email + 1hr email) to reduce no-shows
  6. Connects to CRM and adds booking link to email signature Result: Fully configured Calendly with booking page, reminders, calendar sync, and CRM integration — ready to share with prospects

Example 2: Team configuring round-robin with Chili Piper for inbound demos

User says: "We have 8 AEs and need to route inbound demo requests from our website form to the right rep." Skill does:

  1. Recommends Chili Piper Concierge for highest inbound conversion
  2. Designs routing rules: by territory first, then weighted round-robin within territory
  3. Configures Instant Booker on the website form — prospect books immediately after form submission
  4. Sets up Handoff flow for SDR-qualified leads to book on behalf of AEs
  5. Integrates with Salesforce for account-owner routing on existing accounts
  6. Creates reporting dashboard for meetings booked per rep, conversion rate, and no-show rate Result: Automated inbound routing that qualifies, routes, and books meetings in one flow — no manual rep assignment needed

Example 3: Reducing no-show rate from 25% to under 15%

User says: "Our demo no-show rate is 25%. How do I fix this?" Skill does:

  1. Benchmarks 25% as high (target <15%, great is <10%) and identifies the improvement opportunity
  2. Audits current reminder setup — likely missing reminders or sending only one
  3. Implements a 3-touch reminder sequence: 24hr email with agenda, 1hr email with meeting link, 5-min SMS
  4. Adds a "pre-meeting hook" — send a personalized prep doc or relevant case study 24hr before to increase perceived value
  5. Creates a no-show recovery workflow: auto-send "missed you" email at 5 min past, include one-click reschedule link, follow up next day
  6. Recommends tracking no-show reasons in CRM to identify patterns (specific days, times, lead sources) Result: Multi-touch reminder sequence, pre-meeting value delivery, and automated no-show recovery workflow — targeting <15% no-show rate within 30 days

Troubleshooting

High no-show rate (>15%)

Cause: Missing or insufficient reminder sequences, low perceived meeting value, or too much time between booking and meeting Solution: Implement a 3-touch reminder sequence (24hr, 1hr, 5-min). Add a pre-meeting value hook — send a relevant case study or personalized agenda 24hr before. Shorten your rolling availability window from 3+ weeks to 2 weeks to reduce the gap between booking and meeting. Track no-show rates by day of week and time of day to identify patterns — Tuesday-Thursday 10am-3pm typically has the lowest no-show rates.

Low booking page conversion (<20%)

Cause: Too many form fields, unclear meeting value, poor page design, or friction in the booking flow Solution: Reduce form fields to name + email only (add qualifying questions only if you're filtering out bad-fit prospects). Rewrite your booking page title and description to focus on what the prospect gets ("See how [Company] reduced churn by 30% — 30-min walkthrough") rather than what you want ("Schedule a demo"). Ensure timezone auto-detection is working. Test on mobile — 30%+ of bookings happen on phones. If using a redirect link, switch to an embedded scheduler to reduce drop-off.

Double-booking issues

Cause: Calendar sync not configured properly, multiple scheduling tools not connected, or personal calendar not linked Solution: Verify bi-directional calendar sync is active (not just one-way). If using multiple scheduling tools (e.g., Calendly for inbound + Yesware for outbound), ensure both check the same calendar for conflicts. Link personal Google/Outlook calendars in addition to work calendar so personal appointments block availability. Set buffer time (10-15 min) between meetings to prevent back-to-back bookings from overlapping due to meetings running over.

平台分布

Codex

31.82%
按下载量换算135

Claude

29.44%
按下载量换算125

Cursor

19.19%
按下载量换算81

Gemini CLI

9.96%
按下载量换算42

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills