whatsapp-number-onboarding
Connect WhatsApp Business Numbers to Cloud API
WhatsApp onboarding can fail even when Meta shows a connected number. This skill provides ordered setup checks and troubleshooting guidance for registration, webhooks, and delivery.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
Review the Skillstore skill "whatsapp-number-onboarding" from https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding.md and its manifest at https://skillstore.io/api/skills/rabbitdesigns22-whatsapp-number-onboarding/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「whatsapp-number-onboarding」を使用しています。 The number shows connected, but my webhook receives nothing.
期待される結果:
- Confirm the number's platform and status directly in Meta.
- Inspect the configured callback URL, messages field subscription, and WABA app subscription.
- Check app and WABA ownership; the same-portfolio recommendation is a field observation.
- Send a controlled test message and inspect webhook delivery before changing account settings.
「whatsapp-number-onboarding」を使用しています。 Registration returned error 133016 after repeated activation attempts.
期待される結果:
- Stop registration and deregistration retries.
- The skill associates this error with registration rate limits and a 72-hour block.
- Check Meta's current registration documentation and returned details before scheduling another attempt.
- Do not delete or move the number as a routine retry strategy.
「whatsapp-number-onboarding」を使用しています。 Templates fail with error 131042.
期待される結果:
- Inspect Meta's returned error details instead of assuming a cause.
- Review the WhatsApp account's payment method, credit line, timezone, currency, and suspension status.
- Compare delivered and failed messages during the same period before describing the issue as account-wide.
セキュリティ監査
中リスクAll 46 static matches are false positives involving Markdown, documentation links, configuration descriptions, and authorized account checks. No evidence found of prompt injection, credential exfiltration, or host reconnaissance. Two semantic risks remain: account deletion without explicit consent safeguards and placing client assets in an agency portfolio to avoid onboarding blocks.
確認済みのセキュリティ上の懸念 (2)
リスク要因
⚙️ 外部コマンド (34)
🌐 ネットワークアクセス (5)
🔑 環境変数 (4)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding?utm_source=security_passport_badge)HTMLバッジ
<a href="https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/rabbitdesigns22-whatsapp-number-onboarding/security.svg" alt="Skillstore security assessment" loading="lazy"></a>埋め込みカード
<iframe src="https://skillstore.io/embed/skills/rabbitdesigns22-whatsapp-number-onboarding.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>学術引用 (APA · BibTeX · CFF)
APA形式の引用
rabbitdesigns22. (2026). whatsapp-number-onboarding security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1BibTeX形式の引用
@techreport{rabbitdesigns22-rabbitdesigns22-whatsapp-number-onboarding-2026,
author = {rabbitdesigns22},
title = {whatsapp-number-onboarding security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "whatsapp-number-onboarding security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "rabbitdesigns22"
date-released: "2026-11-11"
url: "https://skillstore.io/skills/rabbitdesigns22-whatsapp-number-onboarding/audits/1"
identifiers:
- type: other
value: "skillstore:rabbitdesigns22-whatsapp-number-onboarding:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
Prepare a first business number
Organize required business information, account identifiers, registration steps, and final delivery checks before launch.
Separate client integrations
Review app ownership, hosting projects, webhook destinations, and account identifiers to prevent cross-client configuration mistakes.
Diagnose missing or duplicate messages
Compare number status, app subscriptions, callback domains, and error details before making disruptive changes.
これらのプロンプトを試す
Prepare a WhatsApp Cloud API onboarding checklist for my business. List required information and human actions. Do not request tokens or PINs in chat.
Meta shows my number as connected, but incoming messages do not reach my bot. Suggest read-only checks first and distinguish field observations from official guidance.
Our WhatsApp bot stopped receiving messages after a hosting domain change. Review callback URLs, subscribed fields, app subscriptions, and project identity before proposing changes.
Audit our client onboarding plan for ownership, project isolation, token handling, registration limits, and delivery checks. Require approval before deletion, subscription removal, or portfolio changes.
ベストプラクティス
- Confirm account ownership and the exact hosting project before changing identifiers or webhook settings.
- Keep tokens and PINs out of chat; use secure storage and human entry for sensitive values.
- Start with read-only checks and verify current Meta guidance; obtain owner approval before destructive or ownership-changing actions.
回避
- Treating a valid token or a green dashboard as proof that messages reach the bot.
- Repeatedly registering or deregistering a number while ignoring rate limits and returned error details.
- Deleting accounts or placing client assets in an agency portfolio without informed approval and a continuity plan.
よくある質問
Does this skill connect the number automatically?
Which AI tools are supported?
Does a connected dashboard status prove delivery works?
Are all troubleshooting recommendations official Meta policy?
Should I delete an existing WhatsApp account immediately?
Should client assets use my agency's portfolio?
開発者情報
作成者
rabbitdesigns22ライセンス
不明
Skillstore リビジョン
r1
バージョンに関する注意
作者はバージョンを宣言していません。
参照
f38ac41a6255e57978dd6f276aec539d5e9b5255
メンテナンスの新しさ
2026/11/12
利用状況
0 ダウンロード · 0 閲覧
ファイル構成
📄 SKILL.md