Skip to main content

measure-content-performance

Measure whether content helps an audience progress, not only whether it attracts attention. Use when teams need a decision-ready model connecting reach, comprehension, action, support, trust, conversion, retention, or risk.

ソース情報

リポジトリ
protosphinx/sphinxstack
ソースの最終更新活動
2026年7月29日 13:55
検出された SKILL.md の言語
英語
スター
3
フォーク
0

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

ソースファイルを確認

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

ファイルエクスプローラー
2 ファイル

SKILL.md を表示中

SKILL.md
ソースの指示 · 読み取り専用プレビュー
name
measure-content-performance
category
web
description
Measure whether content helps an audience progress, not only whether it attracts attention. Use when teams need a decision-ready model connecting reach, comprehension, action, support, trust, conversion, retention, or risk.
# measure-content-performance Start with the audience decision and measurement limitations. ## Procedure 1. Define content purpose, audience, lifecycle stage, decision, owner, and action that measurement should inform. 2. Map an outcome chain from exposure through useful engagement, comprehension, next action, and downstream result. 3. Choose primary, guardrail, diagnostic, and qualitative measures with clear units and windows. 4. Write event and attribution definitions, identity boundaries, exclusions, consent, retention, and data-quality checks. 5. Establish baselines, comparison groups, seasonality, channel differences, and known external influences. 6. Separate content contribution from unsupported causal claims about revenue or behavior. 7. Segment only where privacy, sample size, and decision value justify it. 8. Reconcile analytics with search, support, user research, accessibility, sales, and content-change records. 9. Build a dashboard or report that shows counts, rates, coverage, uncertainty, and decision thresholds. 10. Review on a fixed cadence, record decisions, and verify whether changes improve the intended outcome without harming guardrails. ## Guardrails - Do not track people beyond consent, purpose, or approved retention. - Treat missing and blocked analytics as coverage gaps, not zero behavior. - Avoid ranking content on a single vanity metric. - Do not call correlation or attribution model output proven causation. ## Done - A measurement model links content to an audience outcome and decision - Event, denominator, attribution, privacy, and quality definitions are verified - Reports show coverage, uncertainty, and guardrails with headline metrics - Decisions and forecast-versus-actual outcomes are recorded
GitHubで見る