メニュー
Compute customer lifetime value (LTV), realized or predicted, by cohort or segment, with optional gross-margin and discount-rate adjustments. Use when the user asks "what is a customer worth", wants to size a CAC budget, or compares channels by long-term value.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create, update, or apply a Holistics dashboard theme (library/themes/) from any input: a brand name, website, screenshot, brand guidelines, explicit colors, or a mood description. Use when the user wants to theme, brand, restyle, or change a dashboard's look and feel. Typical phrasings: build a theme, match our brand, use these colors, make it dark, make it warm/minimal/premium/editorial, glow up this dashboard. Do NOT trigger for building a dashboard, authoring block content, or adding controls.
Create or refine a Holistics custom chart (CustomChartDef in library/custom_charts/) for a chart type the built-in viz can't cover. Use when the user wants to create a custom chart, convert a Vega/Vega-Lite spec into Holistics AML, or scaffold or refine a chart template — or when a dashboard needs a chart form with no built-in equivalent (heatmap matrix, sankey, waterfall, box plot, ...). Typical phrasings: create a custom chart for X, turn this Vega-Lite spec into a Holistics chart, we need a sankey of X. Do NOT trigger for a standard built-in chart or a dynamic content block.
Create, update, or apply a Holistics dashboard theme (library/themes/) from any input: a brand name, website, screenshot, brand guidelines, explicit colors, or a mood description. Use when the user wants to theme, brand, restyle, or change a dashboard's look and feel. Typical phrasings: build a theme, match our brand, use these colors, make it dark, make it warm/minimal/premium/editorial, glow up this dashboard. Do NOT trigger for building a dashboard, authoring block content, or adding controls.
Review a past conversation between a Holistics data-analyst AI agent and a user, then produce insight report with three sections (`Summary`, `Recap`, and `Suggestions`). Use this whenever the user wants to assess, grade, debrief, or critique how the agent performed on a chat, including phrasings like " this conversation", "how did the agent do", "grade this chat", "what could the AI have done better", or "what context should I add to improve the agent", even if they don't say the word "review".
Use this whenever working in a (Holistics) AMQL project (i.e. with AML files). It guides you to set up and review the AMQL development environment and tooling so that the development can be done accurately and efficiently. Tooling includes CLI, MCP, code synchronization, etc.
Address suggestions in a past conversation's insight by performing each suggestion's actionable fix. Use when the user asks to implement, apply, address, or act on the suggestions from a conversation insight. Requires a conversation ID. Do NOT use this to generate a new insight.
| name | ltv-analysis |
| description | Compute customer lifetime value (LTV), realized or predicted, by cohort or segment, with optional gross-margin and discount-rate adjustments. Use when the user asks "what is a customer worth", wants to size a CAC budget, or compares channels by long-term value. |
LTV = ARPU × gross_margin / churn_rateLTV(t) = sum of revenue from cohort across [0, t] / cohort sizeARPU / churn_rate implicitly assumes constant churn forever. Check whether churn is stable or rising.