Skills Plugins MCP Prompt Model 博客 我的中心
生活とツール #api #ai #web

observe-whatsapp

Observe and troubleshoot WhatsApp in Kapso: search Logs across API, Meta webhook, workflow, and webhook-delivery events; debug message delivery; inspect webhook retries; triage API errors; and run health checks. Use when investigating production issues, message failures, workflow behavior, or webhook delivery problems.

DeepseekModel キュレーション済みスキル 品質 優秀 · 78 v1.0.0

取得

https://deepseekmodel.com/api/download.php?id=gokapso-agent-skills-skills-observe-whatsapp-skill-md&format=skill
ダウンロード .skill 標準形式。system_prompt と model_config を収録し、任意の Agent で利用可能
.skill ファイルの system_prompt フィールドの実際の内容。
name observe-whatsapp description Observe and troubleshoot WhatsApp in Kapso: search Logs across API, Meta webhook, workflow, and webhook-delivery events; debug message delivery; inspect webhook retries; triage API errors; and run health checks. Use when investigating production issues, message failures, workflow behavior, or webhook delivery problems. Observe WhatsApp When to use Use this skill for operational diagnostics: Logs search, message delivery investigation, webhook delivery debugging, error triage, workflow event correlation, and WhatsApp health checks. Setup Preferred path: Kapso CLI installed and authenticated ( kapso login ) Start with kapso status to confirm project access and available WhatsApp numbers Fallback path: Env vars: KAPSO_API_BASE_URL (host only, no /platform/v1 ) KAPSO_API_KEY How to Search logs Use Logs search first when the user gives an identifier, endpoint, message ID, workflow execution ID, webhook delivery ID, request ID, or a vague "what happened?" debugging prompt. Preferred path: Search the current project: kapso logs search --query "<id-or-text>" --period 24h --source all --limit 20 --output json If the exact search is empty, retry with --period 7d before concluding there are no logs. Add --problems-only for broad error scans; leave it off when reconstructing an exact timeline. Add explicit filters only when they intentionally narrow the search: Workflow execution: kapso logs search --query "<execution-id>" --source flow_event --filter flow_execution_id=<execution-id> --period 7d --output json API endpoint/status: kapso logs search --source external_api_log --filter endpoint_contains=/messages --filter response_status=500 --period 24h --output json WhatsApp message ID: kapso logs search --query "wamid..." --source whatsapp_webhook_event --filter whatsapp_message_id=wamid... --period 7d --output json Webhook delivery: kapso logs search --source webhook_delivery --filter webhook_id=<webhook-id> --period 24h --output json Fallback path: Search via Platform API: node scripts/log-search.js --query "<id-or-text>" --period 24h --source all --limit 20 Use filters with repeated flags: node scripts/log-search.js --source flow_event --filter flow_execution_id=<execution-id> --period 7d Discover source and filter options: node scripts/log-search.js --catalog true Logs sources are external_api_log , whatsapp_webhook_event , flow_event , and webhook_delivery . The Platform API fallback returns indexed Logs payloads for the API-key project and requires Logs and Elasticsearch to be enabled. Investigate message delivery Preferred path: Search the WAMID or customer phone first: kapso logs search --query "<wamid-or-phone>" --period 7d --source all --limit 20 --output json Resolve the number: kapso whatsapp numbers resolve --phone-number "<display-number>" --output json List recent messages: kapso whatsapp messages list --phone-number "<display-number>" --limit 50 --output json Inspect a specific message: kapso whatsapp messages get <message-id> --phone-number-id <id> --output json Inspect the conversation: kapso whatsapp conversations list --phone-number "<display-number>" --output json Fallback path: List messages: node scripts/messages.js --phone-number-id <id> Inspect message: node scripts/message-details.js --message-id <id> Find conversation: node scripts/lookup-conversation.js --phone-number <e164> Triage errors Preferred path: Confirm project and number state: kapso status Run number health: kapso whatsapp numbers health --phone-number "<display-number>" --output human Search recent problem logs: kapso logs search --problems-only --period 24h --source all --limit 20 --output json Inspect related templates when relevant: kapso whatsapp templates list --phone-number "<display-number>" --output json Fallback path: Logs search: node scripts/log-search.js --problems-only true --period 24h --limit 20 Message errors: node scripts/errors.js API logs: node scripts/api-logs.js Webhook deliveries: node scripts/webhook-deliveries.js Run health checks Preferred path: Project overview: kapso status Phone number health: kapso whatsapp numbers health --phone-number "<display-number>" --output human Fallback path: Project overview: node scripts/overview.js Phone number health: node scripts/whatsapp-health.js --phone-number-id <id> Scripts Messages Script Purpose messages.js List messages message-details.js Get message details lookup-conversation.js Find conversation by phone or ID Errors and logs Script Purpose log-search.js Search Logs across API, Meta webhook, workflow, and webhook-delivery sources errors.js List message errors api-logs.js List external API logs webhook-deliveries.js List webhook delivery attempts Health Script Purpose overview.js Project overview whatsapp-health.js Phone number health check OpenAPI Script Purpose openapi-explore.mjs Explore OpenAPI (search/op/schema/where) Install deps (once): npm i Examples: node scripts/openapi-explore.mjs --spec platform search "webhook deliveries" node scripts/openapi-explore.mjs --spec platform op listWebhookDeliveries node scripts/openapi-explore.mjs --spec platform schema WebhookDelivery Notes For webhook setup (create/update/delete, signature verification, event types), use integrate-whatsapp . For Project Event definitions, event-triggered workflow setup, or emit_event graph changes, use automate-whatsapp . Prefer resolving a display phone number to the canonical phone_number_id before deep debugging. Prefer Logs search before older single-resource log endpoints when correlating across messages, workflows, API calls, and webhook deliveries. Keep the scripts as the fallback path when the CLI is unavailable or when you need API-log or webhook-delivery inspection. References references/message-debugging-reference.md - Message debugging guide references/triage-reference.md - Error triage guide references/health-reference.md - Health check guide Related skills integrate-whatsapp - Onboarding, webhooks, messaging, templates, flows automate-whatsapp - Workflows, agents, and automations [observe-whatsapp file map]|root: . |.:{package.json,SKILL.md} |assets:{health-example.json,message-debugging-example.json,triage-example.json} |references:{health-reference.md,message-debugging-reference.md,triage-reference.md} |scripts:{api-logs.js,errors.js,log-search.js,lookup-conversation.js,message-details.js,messages.js,openapi-explore.mjs,overview.js,webhook-deliveries.js,whatsapp-health.js} |scripts/lib/messages:{args.js,kapso-api.js} |scripts/lib/status:{args.js,kapso-api.js} |scripts/lib/triage:{args.js,kapso-api.js}
このスキルを起動するキーワード。クリックでコピーできます。

このスキルにはトリガーワードがありません。

ダウンロードした .skill に含まれるフィールド。
フィールド 説明
formatフォーマット識別子(skill/v1)
skill_idスキル固有 ID
nameスキル名
versionバージョン
description説明
categoryカテゴリ(配列)
trigger_wordsトリガーワード
tagsタグ
sourceソース
source_urlソース URL(本ページ)
exported_atエクスポート日時(ダウンロード毎)
system_promptシステムプロンプト本文
model_configモデル設定:provider / model / temperature / max_tokens / top_p
examplesサンプル
install_guide各プラットフォームの導入説明(Coze / Dify / Claude / カスタム)
同じスキルを各プラットフォーム形式で出力できます。
.skill 標準形式。system_prompt と model_config を収録し、任意の Agent で利用可能 ダウンロード
.skillpro 拡張形式。scripts / tools / dependencies / hooks を含む ダウンロード
.json 純粋な JSON 出力。system_prompt とモデル設定のみ ダウンロード
Coze frontmatter 付き Markdown。Coze へのインポート用 ダウンロード
Dify Dify DSL。アプリ作成後にそのままインポート ダウンロード

每日精选 Skill 推荐,免费送到你邮箱

输入邮箱,每天接收一个精选 AI Agent 技能推荐。完全免费,持续更新。

验证码 --

提交后我们会发送一封确认邮件,点击邮件里的链接才会开始收信。

完全免费,取消任意时间。我们不会发送垃圾邮件。