スキル messaging-performance-analyzer

📦

messaging-performance-analyzer

Name: messaging-performance-analyzer
Author: sentdm

コンテンツリビジョン r1 安全 ⚙️ 外部コマンド

Diagnose Messaging Performance

Delivery data is difficult to interpret when statuses, channels, and webhook evidence disagree. This skill builds reliable cohorts and identifies the strongest supported cause.

対応: Claude Codex Code(CC)

🥈 80 シルバー

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

Review the Skillstore skill "messaging-performance-analyzer" from https://skillstore.io/skills/sentdm-messaging-performance-analyzer.md and its manifest at https://skillstore.io/api/skills/sentdm-messaging-performance-analyzer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/sentdm-messaging-performance-analyzer.md 署名済み manifest GET /api/skills/sentdm-messaging-performance-analyzer/manifest 署名済み lockfile GET /api/skills/sentdm-messaging-performance-analyzer/lockfile

テストする

「messaging-performance-analyzer」を使用しています。 Analyze an SMS export with 1,200 routed messages and 720 delivered messages.

期待される結果:

Primary diagnosis: the largest observed loss is between routing and delivery. Verify compliance, opt-out, and provider error evidence for the affected cohort.

「messaging-performance-analyzer」を使用しています。 Explain why delivered messages are missing from our customer database.

期待される結果:

Delivery status is healthy in Sent.
Customer-side callbacks are incomplete.
Check webhook subscriptions, event history, and endpoint response failures next.

「messaging-performance-analyzer」を使用しています。 Compare WhatsApp and SMS campaign results.

期待される結果:

Report delivery for both channels, but report READ only as WhatsApp engagement. Keep counts, rates, exclusions, and cohort definitions visible.

セキュリティ監査

安全

v1 • 2026/9/11 バージョン別レポートを開く

All 57 static findings are false positives caused by Markdown code formatting, documentation terminology, Python docstrings, and ordinary error handling. The script only reads a user-selected CSV or JSON file, computes local statistics, and prints results; no prompt injection, command execution, network access, or malicious intent was found.

スキャンされたファイル

1,252

解析済み行数

レビュー項目

誤検知を無視

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/sentdm-messaging-performance-analyzer/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/sentdm-messaging-performance-analyzer/security.svg)](https://skillstore.io/skills/sentdm-messaging-performance-analyzer?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/sentdm-messaging-performance-analyzer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sentdm-messaging-performance-analyzer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/sentdm-messaging-performance-analyzer.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形式の引用

sentdm. (2026). messaging-performance-analyzer security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-messaging-performance-analyzer/audits/1

BibTeX形式の引用

@techreport{sentdm-sentdm-messaging-performance-analyzer-2026,
  author = {sentdm},
  title = {messaging-performance-analyzer security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/sentdm-messaging-performance-analyzer/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: "messaging-performance-analyzer security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "sentdm"
date-released: "2026-09-11"
url: "https://skillstore.io/skills/sentdm-messaging-performance-analyzer/audits/1"
identifiers:
  - type: other
    value: "skillstore:sentdm-messaging-performance-analyzer:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Investigate delivery drops

Compare channel funnels, isolate the largest transition loss, and identify the evidence needed for a reliable diagnosis.

Debug missing webhook events

Distinguish message delivery problems from webhook configuration, subscription, or endpoint failures.

Review campaign performance

Measure delivery and engagement by profile, template, country, channel, and time window.

これらのプロンプトを試す

Summarize a delivery export

Analyze this Sent MDR export. Report counts by channel and latest status, then identify the largest supported delivery issue.

Compare campaign periods

Compare these two campaign periods by channel, profile, template, and country. Show count and rate changes, then state the strongest supported explanation.

Diagnose webhook gaps

Sent shows delivered messages, but our database lacks callbacks. Compare status, activity, webhook history, subscriptions, and endpoint responses before naming the cause.

Build an escalation diagnosis

Analyze this multi-channel incident using explicit activity histories only. Reconcile all groups, quantify anomalies, rank hypotheses, and prepare one evidence-based escalation recommendation.

ベストプラクティス

Define the cohort by time, profile, template, channel, country, and recipient segment before calculating rates.
Use Sent message identifiers and explicit activity histories for transition analysis.
Report counts with rates, retain unknown records, and end with one evidence-based verification step.

回避

Do not infer missing lifecycle stages from a latest-status snapshot.
Do not combine SMS, WhatsApp, and RCS before checking each channel separately.
Do not label traffic as carrier filtered without a stable baseline and sufficient evidence.