Token导航 LogoToken导航

Agent Skill · 待分类

sales-happyscribe(销售 快乐抄写员)

sales-happyscribe 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

sales-happyscribe 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为权限未标注;许可证信息还不明确,暂无第三方扫描结果,按安装量在待分类类的 11,209 个 Skill 里排第 10,614。

总安装 194周安装 8GitHub Stars 13下载 63核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

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

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

sales-happyscribe 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中整理协作事项。适用于围绕仓库状态、代码变更或协作事项进行信息梳理的场景。

通过仓库路径或协作线索调用,结合原始 README 可进一步核验具体用法。安装命令为 npx skills add https://github.com/sales-skills/sales --skill sales-happyscribe。使用前需确认权限范围、维护状态,以及是否涉及联网、命令执行或文件读写操作。

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

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    权限没有明确标注,第一次使用时只给一个无关紧要的任务,观察它到底读了哪些文件和网络。

常见问题

6 条

sales-happyscribe 怎么安装?

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

sales-happyscribe 支持哪些 AI 工具?

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

sales-happyscribe 需要什么权限?

权限级别没有明确标注。第一次使用时建议只给无关紧要的任务,观察它实际读写了哪些内容。

sales-happyscribe 是免费的吗?

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

sales-happyscribe 用的人多吗?

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

sales-happyscribe 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

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

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
sales-happyscribe

销售 快乐抄写员 · 本页

19413权限未标注未明确未收录

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

SKILL.md 原文

name
sales-happyscribe
description
HappyScribe platform help — AI + human transcription, subtitle generation, and translation in 120+ languages with SOC 2 / GDPR compliance. Use when uploading audio or video for batch transcription across many languages, generating SRT/VTT/Premiere subtitles for video production, ordering human transcription for 99% accuracy on legal or broadcast content, integrating HappyScribe REST API into a transcript pipeline, troubleshooting accuracy with accents or multiple speakers, comparing HappyScribe vs Sonix vs Rev vs Trint for media transcription, choosing between AI and human transcription tiers, or debugging export format issues. Do NOT use for live meeting recording or real-time note-taking (HappyScribe is upload-only — use /sales-note-taker for live meeting tools).
argument-hint
[describe what you need help with in HappyScribe]
license
MIT
version
1.0.0
tags
[sales, transcription, subtitles, translation, platform]
github
https://github.com/happyscribe

HappyScribe Platform Help

Step 1 — Gather context

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

  1. What's your primary goal?

- A) Transcribe audio/video files (batch transcription) - B) Generate subtitles/captions for video - C) Translate transcripts or subtitles into other languages - D) Order human transcription for high-accuracy needs - E) Integrate HappyScribe API into a pipeline - F) Compare HappyScribe to alternatives for my use case - G) Troubleshoot a specific issue (accuracy, editor, exports)

  1. What type of content are you transcribing?

- A) Meetings / calls - B) Interviews / podcasts - C) Legal / compliance recordings - D) Media production (film, TV, marketing videos) - E) Research / academic - F) Mixed / high volume

  1. What plan are you on (or considering)?

- A) Free trial (10 min) - B) Basic ($17/mo — 120 AI minutes) - C) Pro ($29/mo — 600 AI minutes) - D) Business ($89/mo — 6,000 AI minutes) - E) Enterprise (custom) - F) Not sure yet

Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.

Step 2 — Route or answer directly

Problem domainRoute to
Choosing a live meeting recorder or note-taker/sales-note-taker {user's question}
Building a coaching program from call recordings/sales-coaching {user's question}
General CRM-to-tool integration (Zapier, webhooks, iPaaS)/sales-integration {user's question}
Comparing batch transcription tools broadly/sales-note-taker {user's question}

When routing, provide the exact command: "This is a {problem domain} question — run: /sales-{skill} {user's original question}"

Otherwise, answer directly below.

Step 3 — HappyScribe platform reference

Read references/platform-guide.md for the full platform reference — modules, pricing, integrations, data model, workflows.

If the question involves the API, also read references/happyscribe-api-reference.md.

Answer the user's question using only the relevant section. Don't dump the full reference.

Step 4 — Actionable guidance

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

Plan selection framework:

  • One-off or light use (<2 hrs/mo) → Basic ($17/mo for 120 min, or $8.50/mo annual)
  • Regular transcription (up to 10 hrs/mo) → Pro ($29/mo for 600 min, 3 seats included)
  • High-volume production (up to 100 hrs/mo) → Business ($89/mo for 6,000 min, 5 seats, style guides)
  • Overflow credits: $0.20/min ($12/hr) once monthly allotment is exhausted
  • Human transcription: $2.00/min ($120/hr) — order separately from subscription

AI vs Human decision:

  • AI (85% accuracy) → drafts, internal use, content with clear audio and common accents
  • Human (99% accuracy) → legal, broadcast, publication, heavy accents, poor audio quality

Accuracy optimization:

  1. Upload highest quality audio (minimize background noise, crosstalk)
  2. Use custom glossaries (Business+) for domain-specific terms
  3. Use style guides for formatting consistency across team projects
  4. Review speaker labels after transcription — diarization is imperfect

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

*Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.*
  • No live/real-time transcription. HappyScribe is upload-only — it does not join meetings or capture audio live. For live transcription, use Fathom, Fireflies, or Otter.
  • 85% AI accuracy requires manual cleanup. Expect significant corrections with background noise, multiple speakers, or strong accents. Budget editor time into your workflow.
  • Free trial is 10 minutes total, not recurring. Exports are watermarked on free tier. You cannot evaluate properly without paying.
  • Pricing can change suddenly. Multiple users report unexpected price increases. Lock in annual billing to protect your rate.
  • Style guides are Business-only. Teams needing formatting consistency across projects must be on Business ($89/mo) or Enterprise.
  • API rate limit is 200 req/hour. Lower than most transcription APIs — queue requests and cache responses for high-volume pipelines.
  • Editor can lose unsaved work. Some users report page refresh bugs that wipe edits. Save frequently and export drafts.
  • Human transcription is billed separately. The $2.00/min cost is on top of your subscription fee, not instead of it.

Related skills

  • /sales-note-taker — Comparing AI meeting note-takers and conversation intelligence platforms (Fathom, Fireflies, Gong, etc.). HappyScribe is a batch transcription option, not a live meeting tool.
  • /sales-sonix — Sonix platform help (closest competitor — batch AI transcription, 53+ languages, REST API, SOC 2/HIPAA)
  • /sales-integration — General tool integration patterns (Zapier, webhooks, iPaaS)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: Choosing HappyScribe vs Sonix for subtitle production

User says: "I produce marketing videos in 5 languages and need subtitles. Should I use HappyScribe or Sonix?" Skill does:

  1. Notes HappyScribe supports 120+ languages vs Sonix's 53+ — wider coverage for multilingual workflows
  2. Compares subtitle editors: HappyScribe has styling/positioning controls and more export formats (SRT, VTT, STL, Premiere XML, FCP XML); Sonix has video burn-in
  3. Compares pricing: HappyScribe Pro $29/mo for 600 min vs Sonix Premium $22/mo + $5/hr — HappyScribe is cheaper at moderate volumes
  4. Recommends HappyScribe for multi-language subtitle workflows with extensive format needs

Result: Clear recommendation based on language coverage and subtitle feature comparison.

Example 2: Building an API pipeline for transcription

User says: "I want to auto-transcribe uploaded recordings using the HappyScribe API and export as SRT." Skill does:

  1. Reads the API reference for endpoint details
  2. Sketches the pipeline: Upload via signed S3 URL → Create Order with is_subtitle: true → Poll or webhook for completion → Create Export with format: srt → Download from export URL
  3. Notes: use Orders endpoint (Transcriptions endpoint is deprecated), 200 req/hr rate limit, Bearer token auth
  4. Flags: confirm: true on order creation to auto-submit, or create then confirm separately for review

Result: Working pipeline architecture with HappyScribe-specific endpoint details.

Example 3: Transcription accuracy is terrible with accented speakers

User says: "HappyScribe keeps getting names and technical terms wrong — the transcript is unusable for our legal team." Skill does:

  1. Explains 85% AI accuracy is typical — for legal-grade work, recommends human transcription ($2.00/min, 99% accuracy)
  2. For AI transcription improvement: create a custom glossary with names and technical terms (Business+ required), upload highest quality audio, ensure clear speaker separation
  3. Suggests a hybrid workflow: AI transcription first for speed, then order human proofreading on critical sections

Result: Practical fix with cost/accuracy trade-off guidance.

Troubleshooting

AI transcription accuracy drops with multiple speakers or accents

Symptom: Transcript has frequent word errors, especially with non-native English speakers or cross-talk Cause: HappyScribe's AI engine (Whisper-based) struggles with overlapping speech, strong accents, and domain-specific terminology Solution: Upload the highest quality audio available. Create a custom glossary (Business+) with proper nouns, technical terms, and acronyms. For critical content, use human transcription ($2.00/min). If accuracy is consistently below 70%, the audio quality may be the limiting factor — consider using a dedicated recording tool with noise cancellation.

Editor loses changes on page refresh

Symptom: Edits disappear after the browser refreshes or the page reloads unexpectedly Cause: Known intermittent bug where the editor fails to auto-save before a page refresh Solution: Save manually and frequently (Ctrl/Cmd+S). Export a draft after major edits as a backup. Use Chrome or Firefox (most tested). Avoid editing on unstable internet connections. If the issue persists, contact HappyScribe support with your browser version.

Translation quality is poor or nonsensical

Symptom: Translated transcripts contain gibberish, made-up content, or completely wrong translations Cause: HappyScribe changed their AI translation model and quality regressed for some language pairs Solution: Review translations immediately after generation — don't publish without human review. For critical translations, order human translation instead of AI. If a specific language pair consistently fails, report it to HappyScribe support and use a dedicated translation service in the interim.

平台分布

Codex

33.28%
按下载量换算21

Claude

30.99%
按下载量换算20

Cursor

20.69%
按下载量换算13

Gemini CLI

10.3%
按下载量换算6

安全审计

暂无安全审计结果可展示。

权限和风险

权限未标注

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

继续浏览同类 Skills