PluginBench
Skill
Pass
Audit score 90

sent-account-readiness

sentdm/sent-plugin

Verify Sent account authorization, balance, and onboarding readiness before sending.

What is sent-account-readiness?

Checks whether your Sent account is authorized, funded, and ready to send messages. Use this to diagnose account scope, balance sufficiency, KYC/onboarding status, and blocking issues before launching campaigns or channels.

  • Identifies the authorized account context, organization, and Sender Profile scope via OAuth 2.1/PKCE
  • Retrieves current account balance and currency to confirm sufficient funds
  • Checks onboarding and KYC status to surface incomplete, pending, approved, or blocked steps
  • Performs preflight validation before high-volume sends or channel launches
  • Routes remediation requests to specialized onboarding or compliance skills

How to install sent-account-readiness

npx skills add https://github.com/sentdm/sent-plugin --skill sent-account-readiness
Prerequisites
  • Sent MCP client configured and authorized via OAuth 2.1/PKCE
  • Active Sent account with at least one organization and Sender Profile
Claude Code
Cursor
Windsurf
Cline

How to use sent-account-readiness

  1. 1.Call `account.get` to retrieve the authorized account context, organization, and Sender Profile
  2. 2.Call `balance.get` to check current balance and currency before high-volume sends
  3. 3.Call `onboarding.status` to identify any incomplete, pending, approved, or blocked onboarding steps
  4. 4.Review the returned status to determine readiness or blocking issues
  5. 5.Route remediation requests (e.g., A2P registration, WhatsApp Embedded Signup) to the appropriate specialized skill if needed

Use cases

Good for
  • Verify account readiness before launching an SMS or WhatsApp campaign
  • Check available balance to confirm funds are sufficient for a bulk send
  • Diagnose why onboarding is blocked and identify the required remediation step
  • Confirm MCP authorization scope matches the intended organization and Sender Profile
  • Validate account status as part of a pre-launch checklist for a new messaging channel
Who it's for
  • Messaging operations teams planning campaigns or channel launches
  • Account managers troubleshooting onboarding or compliance blockers
  • Developers integrating Sent messaging into applications
  • Finance or compliance roles verifying account funding and KYC status

sent-account-readiness FAQ

What happens if MCP authentication fails?

The skill will explain what can still be planned without authorization and direct you to authorize or reauthorize in your MCP client. Do not paste credentials; use your client's built-in OAuth flow.

Can this skill fix onboarding or compliance issues?

No. This skill diagnoses readiness only. For remediation, it routes you to specialized skills like `sms-10dlc-registration`, `waba-embedded-signup`, or `rcs-agent-onboarding`.

When should I check balance?

Check balance before high-volume sends or when insufficient funds may block messaging. The skill returns currency and freshness information when available.

What does 'Sender Profile scope' mean?

The Sender Profile is the authorized identity selected during OAuth. It defines which phone numbers, WhatsApp accounts, or RCS profiles you can use. Reauthorize in your MCP client to change scope.

Will this skill store or print my API keys or tokens?

No. This skill never requests, accepts, prints, or stores tokens, API keys, authorization headers, client IDs, or secrets. Authorization is handled entirely by your MCP client.

Full instructions (SKILL.md)

Source of truth, from sentdm/sent-plugin.


name: sent-account-readiness description: Checks the authorized Sent account, organization and Sender Profile scope, balance, onboarding/KYC status, and readiness with the Sent MCP tools. Use when a user asks whether the account can send, what the MCP connection authorized, whether funds are sufficient, why onboarding is blocked, or for a preflight check before a mutation or channel launch. Route remediation to the relevant onboarding or compliance skill.

Sent Account Readiness

Inspect readiness with account.get, balance.get, and 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.

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.

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.