sent-account-readiness

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sent Account Readiness

Sent账户就绪状态检查

Inspect readiness with
account.get
,
balance.get
, and
onboarding.status
.
使用
account.get
balance.get
onboarding.status
检查就绪状态。

Authorize safely

安全授权

Let the MCP client perform OAuth 2.1/PKCE. Never request, accept, print, or store tokens, API keys, authorization headers, client IDs, or secrets. The authorization grant is scoped to the organization and Sender Profile selected during the client flow. Reauthorize in the client to change that scope, and revoke the grant through the client or applicable Sent account controls when it is no longer needed.
If MCP is unsupported or authentication fails, explain what can still be planned from the skill and direct the user to authorize or reauthorize in their MCP client. Do not ask them to paste credentials.
让MCP客户端执行OAuth 2.1/PKCE流程。切勿请求、接收、打印或存储令牌、API密钥、授权头、客户端ID或密钥。授权权限范围限于客户端流程中选择的组织和Sender Profile。如需更改权限范围,请在客户端中重新授权;当不再需要授权时,通过客户端或相应的Sent账户控制撤销授权。
如果MCP不被支持或认证失败,请说明该skill仍可规划的内容,并引导用户在其MCP客户端中进行授权或重新授权。切勿要求用户粘贴凭据。

Check readiness

检查就绪状态

  1. Use
    account.get
    to identify the authorized account context and surface the selected organization and Sender Profile. Return only the minimum account fields needed for the task.
  2. Use
    balance.get
    before high-volume sends or when insufficient funds may block messaging. Report the currency and returned timestamp or freshness information when available.
  3. Use
    onboarding.status
    to identify incomplete, pending, approved, or blocked onboarding steps. Preserve the distinction between an observed status and a remediation action.
Mask identifiers where practical. Do not repeat account, KYC, contact, or billing details unnecessarily.
  1. 使用
    account.get
    识别已授权的账户上下文,并显示所选的组织和Sender Profile。仅返回任务所需的最少账户字段。
  2. 在高发送量操作前或当资金不足可能阻碍消息发送时,使用
    balance.get
    。若有可用信息,需报告货币类型以及返回的时间戳或新鲜度信息。
  3. 使用
    onboarding.status
    识别未完成、待处理、已批准或已阻止的入职步骤。需区分观察到的状态与整改操作。
尽可能屏蔽标识符。无需重复账户、KYC、联系人或账单详情。

Route remediation

整改路由

This skill diagnoses readiness but does not mutate onboarding state.
  • Route Sender Profile boundary or tenancy design to
    sender-profile-architect
    .
  • Route US A2P registration preparation to
    sms-10dlc-registration
    .
  • Route WhatsApp Embedded Signup to
    waba-embedded-signup
    .
  • Route RCS Business Messaging launch preparation to
    rcs-agent-onboarding
    .
When the user asks only whether an account is ready, report the blocking status and recommended public skill without inventing an operational fix.
该skill仅诊断就绪状态,不修改入职状态。
  • 将Sender Profile边界或租户设计问题转至
    sender-profile-architect
    处理。
  • 将美国A2P注册准备工作转至
    sms-10dlc-registration
    处理。
  • 将WhatsApp嵌入式注册工作转至
    waba-embedded-signup
    处理。
  • 将RCS商业消息启动准备工作转至
    rcs-agent-onboarding
    处理。
当用户仅询问账户是否就绪时,报告阻碍状态并推荐公开skill,切勿自行编造操作解决方案。