ae-user-metric-quantile
Skill6 starsChanged 30 days agoNo licenceView on GitHub
Statistical methods for aggregating metric values at the user level, covering common statistics computed by "first computing a metric value per user, then running statistics over that value" (sum, average, maximum, minimum, median, quantiles, variance, standard deviation, distinct count, average per user, etc.). Trigger when users need to compute metrics such as "the 75th percentile of each user's daily usage duration", "the average of daily per-user payment amounts over the past 7 days", or "the maximum/variance/standard deviation of each user's daily consumption" — i.e., first compute a metric value per user, then run statistics over those values. The implementation chain is "metric-value tag + first/last tag + virtual event property referencing the tag (created via CLI) + Events Analysis report (published to a dashboard)", driven entirely through the AE CLI (ae-cli), not a pure SQL approach. Do not use this Skill for simple one-shot event counting without user-level aggregation, for retention/funnel/path diagnosis, or for metric alerting.
In this repository69 other files it gives its agents.
- ad-delivery-analysisSkill
- ae-drama-creative-evaluationSkill
- channel-quality-analysisSkill
- ab-test-analysisSkill
- ae-kb-bootstrapSkill
- ae-tag-history-versionSkill
- analysis-scope-alignmentSkill
- drama-quality-assessmentSkill
- funnel-misconceptionsSkill
- generate-sqlSkill
- push-tracking-gap-analyzerSkill
- rate-change-significanceSkill
- system-field-referenceSkill
- te-model-selectorSkill
- user-property-timezoneSkill
- ae-feishu-data-permission-syncSkill
- ae-freeze-inactive-dashboardsSkill
- ae-scheduled-pushSkill
- journey-intent-parserSkill
- metric-alertSkill
- ae-data-delay-troubleshooterSkill
- ae-same-report-debugSkill
- dashboard-no-data-troubleshootingSkill
- data-inconsistency-debugSkill
- data-integration-assistantSkill
- filter-result-deviation-troubleshootingSkill
- mcp-trinoSkill
- te-user-id-debugSkill
- ltv-predictionSkill
- revenue-forecast-model-cliSkill
- ae-risk-monitoringSkill
- game-activity-evaluationSkill
- game-economy-balanceSkill
- game-economy-inspectionSkill
- game-testing-first-day-reportSkill
- game-version-compareSkill
- gift-push-strategySkill
- level-churn-analyzerSkill
- new-hero-insightSkill
- puzzle-iaa-analyticsSkill
- pvp-winrate-analyzerSkill
- first-purchase-analysisSkill
- gift-pack-penetration-analysisSkill
- ltv-analysisSkill
- payment-attribution-analysisSkill
- payment-funnel-analysisSkill
- pricing-evaluationSkill
- repeat-purchase-analysisSkill
- device-performance-analysisSkill
- sql-performance-optimizerSkill
- churn-defineSkill
- cohort-retention-deep-diveSkill
- drama-retention-analyzerSkill
- new-user-analysisSkill
- retention-metric-to-event-reportSkill
- retention-verificationSkill
- ae-first-event-builderSkill
- audit-project-usage-analysisSkill
- community-analyzing-theme-commentSkill
- community-hottopic-insightSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

