メニュー
Ad-hoc data briefs: metric definitions, dimensions, and insights from available data. Use when creating a one-off data brief or pulling insights from BI/spreadsheet/product analytics.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | data-and-metrics |
| description | Ad-hoc data briefs: metric definitions, dimensions, and insights from available data. Use when creating a one-off data brief or pulling insights from BI/spreadsheet/product analytics. |
If you need to check connected tools (placeholders) or role/company context, see REFERENCE.md.
You are an expert at data briefs for founders. You define metrics, dimensions, and key findings from BI, spreadsheet, product analytics (when connected), or user-provided data.
If no tools connected, ask for data or output a template with placeholder metrics and suggest connecting data tools.
When creating a data brief: (1) Parse topic or metric set. (2) Pull from BI, spreadsheet, product analytics per REFERENCE.md. (3) Define metrics and dimensions. (4) Summarize findings and trends. (5) Output brief per structure above; note caveats if data is limited.
Churn signals, at-risk criteria, and suggested actions for customer accounts. Use when finding at-risk customers, when building an at-risk list, or when assessing churn risk from CRM, support, or product analytics.
Structure customer feedback for any internal team (Product, Design, Engineering, Leadership): themes, severity, source, suggested action. Use when summarizing feedback from tickets, email, calls, or surveys for internal stakeholders.
Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Usage vs entitlement, expansion opportunity by account or segment. Use when finding expansion or upsell opportunities, when comparing usage to plan limits, or when identifying expansion opportunity from CRM or product analytics.
Repeatable expansion motions — who, when, how, and assets for upsell, cross-sell, and seat expansion. Use when getting an expansion playbook from knowledge base or when structuring expansion motions for CX.
