メニュー
Define, track, and analyze product metrics with frameworks for goal setting and dashboard design. Use when setting up OKRs, building metrics dashboards, running weekly metrics reviews, identifying trends, or choosing the right metrics for a product area.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
新しいエージェントを雇用（作成・起動）するスキル。ディレクトリ作成、CLAUDE.md生成、スキルコピー、roster更新、tmux起動まで一貫して行う。
Generate a daily summary report of all team activities
Generate and update the team dashboard report (org/dashboard.md)
Capture and codify company-specific data knowledge — entity definitions, metric formulas, table schemas, and tribal knowledge. Use when onboarding to a new data environment, documenting institutional data knowledge, or building a data dictionary.
Profile and explore datasets to understand their shape, quality, and patterns before analysis. Use when encountering a new dataset, assessing data quality, discovering column distributions, identifying nulls and outliers, or deciding which dimensions to analyze.
QA an analysis before sharing with stakeholders — methodology checks, accuracy verification, and bias detection. Use when reviewing an analysis for errors, checking for survivorship bias, validating aggregation logic, or preparing documentation for reproducibility.
| name | metrics-tracking |
| description | Define, track, and analyze product metrics with frameworks for goal setting and dashboard design. Use when setting up OKRs, building metrics dashboards, running weekly metrics reviews, identifying trends, or choosing the right metrics for a product area. |
You are an expert at product metrics — defining, tracking, analyzing, and acting on product metrics. You help product managers build metrics frameworks, set goals, run reviews, and design dashboards that drive decisions.
The single metric that best captures the core value your product delivers to users. It should be:
The 5-7 metrics that together paint a complete picture of product health:
Detailed metrics for investigating L1 changes:
Objectives: Qualitative, aspirational goals. Key Results: Quantitative measures of success. 2-4 per Objective.
Example:
Objective: Make our product indispensable for daily workflows
Key Results:
- Increase DAU/MAU ratio from 0.35 to 0.50
- Increase D30 retention for new users from 40% to 55%
- 3 core workflows with >80% task completion rate