metrics-digest
Build the Monday metrics email from the analytics CLI's signups, activation, and churn numbers — pull last week and the prior week, flag any metric that moved more than 10%, and render the fixed template. Use when compiling the Monday metrics email.
- License 许可
- MIT
- 最近更新
- 2026-11-02
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- metrics-digest
- description
- Build the Monday metrics email from the analytics CLI's signups, activation, and churn numbers — pull last week and the prior week, flag any metric that moved more than 10%, and render the fixed template. Use when compiling the Monday metrics email.
02 资源文件 2
- 参考文档grading.json1.0 KB
- 参考文档meta.json215 B
03 SKILL.md 正文
Pull the numbers
Run the analytics CLI for the reporting week and the week before it:
an4 query --metric signups,activation,churn --last 7d --json
For the prior week, check an4 query --help for the correct offset/date-range flag rather than guessing one — CLI flags drift and a wrong guess produces a silently wrong comparison. Run the equivalent query for the 7 days immediately before the reporting week.
Parse both JSON outputs before doing any comparison.
Handle missing or zero-baseline metrics
The three metrics are signups, activation, churn. For each one, check both weeks' output before computing anything:
- Metric absent from either week's JSON: do not compute a change and do not drop the row. Write it as
<metric>: not available in analytics outputin its section. - Prior week value is 0 and current week value is nonzero: percent change is undefined, not zero. Write the row as
<metric>: <current value> (up from 0)instead of a percentage, and treat it as flagged.
Compute change and flag movers
For every metric with a real value in both weeks:
pct_change = (current - prior) / prior * 100
A metric is flagged when abs(pct_change) > 10. This is the only threshold — do not round it or treat 10.0 as a pass.
Render the email
Plain text only — no #, *, -, backticks, or other markdown syntax anywhere in the output.
Subject: Metrics week of <YYYY-MM-DD of the reporting week's start date>
Growth
signups: <value>, <+/-X%> vs prior week
Engagement
activation: <value>, <+/-X%> vs prior week
churn: <value>, <+/-X%> vs prior week
Flags
<one line per flagged metric, e.g. "signups moved +14% vs prior week">
<or, if none qualify: "No metrics moved more than 10% this week.">
Every metric row uses the missing-data or zero-baseline wording above in place of a percentage when those cases apply, in whichever section (Growth or Engagement) it normally belongs to.
Done when
- Subject line reads exactly
Metrics week of <date>with the real start date substituted. - All three metrics — signups, activation, churn — appear exactly once each, in Growth or Engagement, either with a value and percent change or with the explicit missing/zero-baseline wording. None are silently dropped.
- Flags lists every metric with
abs(pct_change) > 10, or the exact no-movers sentence if none qualify. - The rendered output contains zero markdown characters — reread it once and confirm before sending.
04 同仓库更多 Skills
tune
Find and fix real defects in a skill, AGENTS.md, or CLAUDE.md, then prove the description still routes. Runs the bundled token-spending runner, so it starts only on the human's explicit instruction.
skill-tuner
Evidence-tagged rules for writing documents agents consume. Use when creating, editing, or shortening skills, AGENTS.md, or CLAUDE.md.
portfolio
Inventory every skill the agent is shown, with its per-turn listing cost, usage count and visibility knob, then decide one skill at a time whether the model should start it on its own. Reads files only; starts on the human's explicit instruction.
shipit
Release builds with the shipit CLI. Use when releasing or promoting a build to staging or prod, checking a release manifest, or rolling back a shipit deployment.
shipit
Release builds with the shipit CLI. Use when releasing or promoting a build to staging or prod, checking a release manifest, or rolling back a shipit deployment.
shipit
Release builds with the shipit CLI. Use when releasing or promoting a build to staging or prod, checking a release manifest, or rolling back a shipit deployment.