paperclip-api
Use when managing Paperclip AI agent companies - creating tasks, managing agents, approving hires, running heartbeats, or any Paperclip control-plane…
Делает ревью продуктовых метрик — тренды, аномалии, root causes и рекомендации к действиям. Включает декомпозицию North Star (L1/L2), диагностику retention-кривых, анализ воронки, разбор A/B-экспериментов, проверку соответствия OKR и фреймворк атрибуции аномалий. User-invoked
$ npx -y skills add serejaris/personal-corp-os --skill pm-metrics --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/pm-metricsContext preview
The summary Claude sees to decide when to auto-load this skill.
Делает ревью продуктовых метрик — тренды, аномалии, root causes и рекомендации к действиям. Включает декомпозицию North Star (L1/L2), диагностику retention-кривых, анализ воронки, разбор A/B-экспериментов, проверку соответствия OKR и фреймворк атрибуции аномалий. User-invoked
name: pm-metrics description: Делает ревью продуктовых метрик — тренды, аномалии, root causes и рекомендации к действиям. Включает декомпозицию North Star (L1/L2), диагностику retention-кривых, анализ воронки, разбор A/B-экспериментов, проверку соответствия OKR и фреймворк атрибуции аномалий. User-invoked only — do NOT auto-trigger. Triggers on /pm-metrics, "обзор метрик", "разбор воронки", "анализ удержания", "ретеншн", "A/B результаты", "review metrics", "DAU analysis", "retention analysis", "funnel analysis", "metric anomaly".
Part of the Personal Corp framework — running a one-person business through AI agents. Systematically review product metrics, identify trend changes, locate root causes, output action recommendations. Includes North Star decomposition, retention diagnostics, funnel methodology, and A/B experiment reading.
| Field | Required | Notes | |---|---|---| | Metric data | yes | Excel / CSV / pasted table / verbal description | | Cycle | no | Weekly / monthly / quarterly review; default weekly | | Focus | no | Full review / single-metric anomaly / experiment readout | | Business context | no | Releases, campaigns, incidents in the period |
**Mode:** full data → complete review; single-metric change → focused anomaly analysis.
**Decomposition:** North Star → L1 → L2.
**L1 dimensions:**
**North Star selection guide:**
| Product type | Recommended NSM | Typical L1 | |---|---|---| | Social / community | Weekly active posters | DAU/MAU ratio, interactions per user, D7 retention | | Tools / productivity | Weekly users completing core task | Task completion rate, frequency, feature reach | | E-commerce | Weekly transacting users | GMV, AOV, repeat rate, conversion | | Content / media | Weekly content-consumption time | Time per user, completion rate, return rate | | SaaS / B2B | Weekly active teams | Team penetration, feature depth, renewal rate |
**Definitions:**
**User segmentation:**
| Type | Definition | Focus | |---|---|---| | **New** | First-time user | Channel quality, activation rate | | **Active retained** | Active in both periods | Depth, feature reach | | **Returning** | Inactive last period, active this | Return reason, secondary retention | | **Churned** | Active last period, inactive this | Churn cause, win-back potential | | **Dormant** | Inactive multiple periods | Possibly permanent loss |
**Growth identity:** This-period MAU = prev-period retained + new + returning − churned
**Definitions:**
**Retention benchmarks:**
| Product type | D1 | D7 | D30 | Note | |---|---|---|---|---| | Social / messaging | > 70% | > 50% | > 35% | High-frequency essential | | Tools | > 40% | > 25% | > 15% | "Use and leave" pattern | | Content / news | > 35% | > 20% | > 10% | Many alternatives, lower retention | | E-commerce | > 25% | > 15% | > 8% | Low-frequency, watch repeat rate instead | | Games | > 40% | > 20% | > 10% | High variance by genre | | SaaS / B2B | > 60% | > 45% | > 30% | High switching cost, higher baseline |
**Retention-curve diagnosis:**
**Retention segmentation:**
**Funnel construction:** 1. Define start and end points (e.g. homepage visit → payment success) 2. Split into key intermediate steps (each step = a user decision point) 3. Per-step rate = arriving at next / arriving at this
**Funnel framework:**
| Step | Action | Output | |---|---|---| | **Draw** | List steps + rates | Full funnel view | | **Identify bottleneck** | Find lowest-rate step | Optimization focus | | **Benchmark** | Compare history / industry / competitor | Gap quantification | | **Segment** | By channel / device / user type | Locate problem cohort | | **Hypothesize** | Why is the bottleneck there? | Optimization direction | | **Experiment** | Propose A/B test | Action plan |
**Common funnels:**
| Dimension | Standard | Note | |---|---|---| | **Statistical significance** | p < 0.05 | p > 0.05 → inconclusive, don't decide | | **Effect size** | Lift > MDE | Significant but tiny lift may not be worth it | | **Sample size** | Reaches pre-set N | "Significant" without N is unreliable | | **Duration** | Covers ≥ 1-2 full we
Personal Corp is a way to run a one-person company through AI agents: tasks out of your head, departments instead of one person's memory, a weekly retro instead of "I'll sort it out someday".
Use when managing Paperclip AI agent companies - creating tasks, managing agents, approving hires, running heartbeats, or any Paperclip control-plane…
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
Use when user asks for Claude Code usage stats, weekly analytics, project activity summary, or wants to see what projects were worked on. Triggers on…
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction,…
Use when creating or refactoring CLAUDE.md files - enforces best practices for size, structure, and content organization
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp-* owner…