Token导航 LogoToken导航

Agent Skill · 开发

sinch-in-app-calling(应用程序调用中的 sinch)

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

sinch-in-app-calling 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 12,087。

总安装 1,444周安装 59GitHub Stars 7下载 467核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/sinch/skills --skill sinch-in-app-calling

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

sinch-in-app-calling 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。

通过 npx skills add 命令从指定 GitHub 仓库安装,需结合原始 README 确认具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。当前无原始 SKILL.md 内容可参考,实际功能以来源仓库为准。

来源仓库内路径:skills/sinch-in-app-calling

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

sinch-in-app-calling 怎么安装?

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

sinch-in-app-calling 支持哪些 AI 工具?

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

sinch-in-app-calling 需要什么权限?

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

sinch-in-app-calling 是免费的吗?

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

sinch-in-app-calling 用的人多吗?

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

sinch-in-app-calling 安全吗?

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

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

值得选的地方

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

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

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

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
sinch-in-app-calling

应用程序调用中的 sinch · 本页

1,4447操作浏览器未明确有提醒

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

SKILL.md 原文

Sinch In-App Calling

Overview

Real-time voice and video SDK for Android, iOS, and JavaScript (Web). Connects to Sinch's cloud for signaling and routing.

Supported call types

  • App-to-App (VoIP/WebRTC between users)
  • App-to-Phone (call PSTN numbers)
  • App-to-SIP (connect to PBXs, contact centers)
  • App-to-Conference (multi-party calls)
  • Phone-to-App / SIP-to-App (inbound calls)

Agent Instructions

Prerequisites

The user needs a Sinch account with an application key and secret from the Sinch Build Dashboard. See sinch-authentication for credential setup — In-App Calling uses application-scoped auth (Application Key + Application Secret).

Integration workflow

  1. Detect the platform from the user's project (language, build system, framework):

- Android (Kotlin/Java, Gradle) → Read references/android.md - iOS (Swift/ObjC, Xcode) → Read references/ios.md - JavaScript/Web (npm, browser) → Read references/js.md - If unclear, ask the user.

  1. Walk through the integration steps in the platform reference. Go step by step — confirm each step is in place before moving to the next.
  2. Ask about auth approach: Can the Application Secret be embedded (prototyping only) or must JWTs come from a backend (production)?
  3. Ask about call types: Which types does the user need? This determines which sections to cover.
  4. For Phone-to-App / SIP-to-App: The user needs a backend ICE callback handler. See the "Phone-to-App / SIP-to-App backend" section below.

SDK Init References

For detailed SDK initialization code per platform:

Phone-to-App / SIP-to-App backend

Receiving inbound PSTN or SIP calls requires:

  1. A Sinch voice number from the Build Dashboard assigned to the app (or SIP origination configured).
  2. A callback URL in the app's Voice settings.
  3. A backend ICE handler that routes calls via connectMxp:
{
  "action": {
    "name": "connectMxp",
    "destination": {
      "type": "username",
      "endpoint": "target-user-id"
    }
  }
}

Key Concepts

  • SinchClient — The core SDK object. Must be initialized with Application Key and started before any calls can be made or received.
  • User Identity — A string identifier (e.g., user ID) that uniquely identifies a user in the Sinch system. Set during SinchClient initialization.
  • Call Types — App-to-App (VoIP), App-to-Phone (PSTN), App-to-SIP, App-to-Conference, and inbound (Phone-to-App, SIP-to-App).
  • Managed Push — Sinch-managed push notifications for incoming calls when the app is backgrounded. Required on all platforms.
  • JWT Authentication — Production apps must use backend-generated JWTs (not embedded secrets) for SDK authentication.
  • ICE Callback — Incoming Call Event. A backend webhook handler required for Phone-to-App and SIP-to-App calls that routes calls via connectMxp.
  • Environment Host — Regional endpoint for the SDK connection (e.g., ocra.api.sinch.com for global routing).

Common Patterns

  • App-to-App voice call — Initialize SinchClient with user identity, call callUser("recipient-id"). Both users must have active SinchClient instances.
  • App-to-Phone (PSTN) — Call callPhoneNumber("+15551234567") with a CLI (caller ID) set to a Sinch number.
  • Receive incoming calls — Register push notifications, implement call listener/delegate, handle onIncomingCall event.
  • Phone-to-App routing — Assign a Sinch number to the app, set up backend ICE callback that returns connectMxp action targeting the user.
  • Video calling — Use callUserVideo("recipient-id") (or platform equivalent). Requires camera permissions.

Troubleshooting

SymptomLikely causeFix
onClientFailed / clientDidFailJWT issue — token missing, expired, wrong secret, or malformedVerify JWT generation: correct app key + secret, kid matches key ID, token not expired. See auth section in platform reference
onClientFailed / clientDidFailInvalid app key or wrong environment hostVerify key in Dashboard; check environmentHost matches your region
No incoming calls (JS)Managed push not enabledCall sinchClient.setSupportManagedPush() before starting — required even for the caller side
No incoming calls (Android)FCM misconfigurationVerify FCM credentials in Dashboard ("In-app Voice & Video SDKs" → "Google FCM Identification"); check that the device receives FCM tokens
No incoming calls (iOS)APNs push not configured or token staleVerify push certificate/key in Dashboard; ensure registerPushNotificationData is called with a fresh device token
No incoming calls (general)SinchClient not running on the receiver's deviceThe receiver's app must have an active, started SinchClient to receive calls. Verify start() completed successfully
App-to-Phone fails immediatelyMissing CLI (caller ID)Set callerIdentifier / cli with a Sinch number
Audio only in foreground (iOS)CallKit not reporting callsReport outgoing calls to CallKit for background audio

If the above steps don't resolve the issue, instruct the user to contact Sinch Support with their app key, platform, and a description of the problem.

Public endpoints

Set environmentHost when creating the Sinch client:

EndpointRegion
ocra.api.sinch.comGlobal (auto-routed)
ocra-euc1.api.sinch.comEurope
ocra-use1.api.sinch.comNorth America
ocra-sae1.api.sinch.comSouth America
ocra-apse1.api.sinch.comSouth East Asia 1
ocra-apse2.api.sinch.comSouth East Asia 2

Links

平台分布

Codex

35.35%
按下载量换算165

Claude

30%
按下载量换算140

Cursor

20.23%
按下载量换算94

Gemini CLI

9.26%
按下载量换算43

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

操作浏览器

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

安装前确认

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

继续浏览同类 Skills