Token导航 LogoToken导航

Agent Skill · 研究检索

call-analysis(call analysis 搜索)

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

call-analysis 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 64,379。

总安装 303周安装 13GitHub Stars 30下载 106核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/salesably/salesably-marketplace --skill call-analysis

这个 Skill 是做什么的

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

用于销售通话记录的结构化分析与洞察提取,基于 POWERFUL 框架。适合识别行动项、责任人与优先级,提升机会评估准确性。提供转录文本输入与 CRM 集成能力,支持后续任务分配。安装需通过 GitHub 仓库,建议连接 Salesably 工具链获取上下文。涉及客户隐私时应脱敏处理后存储于安全沙箱环境。

来源仓库内路径:skills/call-analysis

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

call-analysis 怎么安装?

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

call-analysis 支持哪些 AI 工具?

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

call-analysis 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

call-analysis 是免费的吗?

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

call-analysis 用的人多吗?

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

call-analysis 安全吗?

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

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

值得选的地方

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

call analysis 搜索 · 本页

30330只读未明确有提醒

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

SKILL.md 原文

Call Analysis

This skill analyzes sales call transcripts to extract strategic insights, capture action items, and assess opportunity health using the POWERFUL deal qualification framework.

Objective

Transform raw call transcripts into structured, actionable summaries that capture key discussion points, identify next steps, and provide objective opportunity assessments.

Analysis Structure

1. Next Steps

Clear action items extracted from the conversation.

Format:

  • Action: What needs to happen
  • Owner: Who is responsible (us or them)
  • Timeline: When it needs to happen
  • Priority: High/Medium/Low

Example:

1. [Us] Send proposal with pricing options - by Friday - High
2. [Them] Get budget approval from finance - by next week - High
3. [Us] Schedule demo with technical team - within 2 weeks - Medium

2. POWERFUL Framework Analysis

Extract insights for each dimension:

Pain
  • What challenges or frustrations did they mention?
  • Include direct quotes when available
  • Note the severity and impact
Opportunity Cost
  • What happens if they don't solve this?
  • Any timelines or deadlines mentioned?
  • Financial or business impact of inaction?
Wants, Needs, Desires
  • What outcomes are they looking for?
  • What does success look like to them?
  • Any specific requirements or criteria?
Executive Level Influence
  • Who else is involved in the decision?
  • What's the approval process?
  • Any stakeholder dynamics revealed?
Resources/Budget
  • Was budget discussed?
  • What's their expected investment range?
  • Any competing priorities for funds?
Fear of Failure
  • What concerns or objections came up?
  • Past negative experiences mentioned?
  • Risk factors they're worried about?
Unequivocal Trust
  • How did they hear about us?
  • Were they transparent and open?
  • Any trust-building moments?
Little Things
  • Communication preferences mentioned?
  • Scheduling constraints?
  • Personal details or rapport builders?

3. Key Discussion Points

Important topics that don't fit neatly into the framework:

  • Technical requirements discussed
  • Competitive mentions
  • Timeline drivers
  • Internal politics
  • Integration needs

4. Opportunity Rating

Objective assessment of deal health.

Rating Scale:

  • 0-40%: Early stage, significant unknowns
  • 40-60%: Developing, some validation
  • 60-80%: Promising, strong signals
  • 80-100%: High confidence, clear path

Qualitative Assessment: One paragraph explaining the rating with evidence from the call.

5. Potential Concerns

Red flags or issues that might hinder the deal:

  • Unresolved objections
  • Missing stakeholders
  • Competitive threats
  • Timeline misalignment
  • Budget constraints
  • Technical gaps

6. Strategic Suggestions

3-5 actionable recommendations based on the analysis:

  • What to do next
  • What to clarify
  • Who else to engage
  • How to address concerns
  • Ways to accelerate the deal

Transcript Quality Requirements

Minimum Standards

  • At least 5 minutes of substantive conversation
  • Identifiable speakers (not just one-sided notes)
  • Readable/parseable format
  • Contains actual sales dialogue (not just administrative chat)

Information to Flag

  • When something is unclear or ambiguous
  • When important context seems missing
  • When speakers are hard to distinguish
  • When audio quality affected transcription

Analysis Guidelines

Be Objective

  • Report what was actually said, not what you wish was said
  • Include both positive and negative signals
  • Don't over-interpret vague statements
  • Flag uncertainty when present

Be Specific

  • Use direct quotes when possible
  • Include specific numbers, dates, names
  • Reference specific moments in the conversation
  • Avoid generic summaries

Be Actionable

  • Every insight should connect to a potential action
  • Prioritize what matters for deal advancement
  • Focus on what can be verified or addressed
  • Highlight time-sensitive items

Be Honest About Gaps

  • Note what wasn't discussed that should have been
  • Identify questions that weren't asked
  • Flag POWERFUL dimensions with no information
  • Suggest what to cover in the next conversation

Output Format

When analyzing a call, produce:

Call Summary Header

Call: [Prospect Name] - [Company]
Date: [Date of call]
Duration: [Approximate length]
Participants: [List of participants]
Stage: [Pipeline stage]

Structured Analysis

  1. Next Steps: Action items with owners and timelines
  2. POWERFUL Analysis: Findings for each dimension
  3. Other Key Notes: Important points outside framework
  4. Opportunity Rating: Percentage and qualitative assessment
  5. Potential Concerns: Red flags and risks
  6. Strategic Suggestions: 3-5 actionable recommendations

Information Gaps

  • POWERFUL dimensions with insufficient information
  • Questions that should be asked next
  • Stakeholders not yet engaged

Cross-References

  • Feed extracted POWERFUL data into powerful-framework scorecard
  • Use insights to inform follow-up-emails content
  • Guide multithread-outreach based on stakeholder mentions
  • Update prospect-research profiles with new information
  • Inform account-qualification tier adjustments

平台分布

Codex

37.32%
按下载量换算40

Claude

26.23%
按下载量换算28

Cursor

17.72%
按下载量换算19

Gemini CLI

9.33%
按下载量换算10

安全审计

Gen Agent Trust Hub

可疑

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills