customer-analytics SKILL.md skillA
customer-analytics from skillmedev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add skillmedev/skills/customer-analytics@git:20261005.bea4ea5Pins git:20261005.bea4ea5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- skillmedev/skills
- Path
skills/customer-analytics/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261005.bea4ea5, committed Oct 5, 2026
- First version recorded
- Jul 5, 2026
- Size
- 7,790 bytes
- Repository stars
- 19
- License
- MIT
Turns transaction data into cohort retention, lifetime value, RFM segments, and churn predictions tied to concrete actions. Use when someone asks "what's our customer LTV", "build a cohort retention table", "which customers are about to churn", "how do repeat purchase rates look by cohort", or "who should we target with a win-back offer". Do NOT use for event-level product usage and feature adoption analysis - use product-analytics instead; for defining market segments for positioning and…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Customer Analytics Transaction logs already contain the answers to "who stays, who spends, who is about to leave" - the failure mode is computing them wrong: cohort charts that include the current incomplete month, LTV built on revenue instead of margin, and churn models validated on shuffled data that collapse in production. This skill produces cohort, LTV, and churn outputs a finance or lifecycle team can act on directly. ## Operating procedure Work the steps in order: cohorts establish the retention reality that LTV math depends on, and churn modeling is only worth doing after the churn definition survives the cohort view. ### Step 1: Gather inputs Collect these first; apply defaults and label guesses as guesses. 1. Transaction table: customer_id, order_date, revenue, and cost or margin if available. 2. Business model: contractual (subscription) or non-contractual (e-commerce/retail). This decides the LTV method in Step 3. 3. Cohort granularity. Default: monthly cohorts when the natural purchase cycle is 2 weeks or longer; weekly cohorts for high-frequency products (food delivery, media). Granularity finer than the purchase cycle produces jagged, unreadable triangles. …
Read the whole file at its exact version.
How to install
mdr add skillmedev/skills/customer-analytics@sha256:3372ac2f0a8022c4The line at the top of this page pins the label git:20261005.bea4ea5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cgteu5mdav5sb5me)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 5, 2026 and Oct 5, 2026, about one every 46 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.bea4ea5 latest | 2026-10-05 | bea4ea5 | 7,790 B | A | view · diff |
| git:20260705.a28c4ce | 2026-07-05 | a28c4ce | 7,750 B | A | view · diff |
| git:20260705.acb5571 | 2026-07-05 | acb5571 | 7,784 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7790 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
skillmedev/skills · 19 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cgteu5mdav5sb5me GET https://markdownregistry.com/api/v1/resolve?ref=skillmedev/skills/customer-analytics GET https://markdownregistry.com/api/v1/blob/3372ac2f0a8022c4a1f020d206beb8d9e2d9d60b2c1592a6ea4646a4997e64f5
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from skillmedev/skills
Every file in skillmedev/skills