Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/segmentation-analysis

@9449d36
Run it yourself

Customer/user segmentation with actionable insights. Use when identifying distinct customer groups, analyzing segment-specific behavior, profiling high-value segments, or testing segmentation hypotheses.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/segmentation-analysis

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈57 tokens for metadata: the name and description. ≈660 when used: this file. ≈1.1k more on demand in 2 files.

Description uses 2.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈227 characters, or 2.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Segmentation Analysis

When to use

  • The team needs to understand who the best customers are and what distinguishes them
  • Marketing wants distinct groups to target with different messages or offers
  • Product needs to prioritise features based on high-value user behaviour patterns
  • Churn is high and the team needs to identify at-risk users before they leave
  • An existing segmentation feels arbitrary and needs data validation or improvement

Process

  1. Define the segmentation goal — clarify what decisions the segments will inform (product roadmap, marketing campaigns, retention programs). The goal determines which variables matter and how many segments are useful (typically 3–7). See references/segmentation_approaches.md.
  2. Select and prepare variables — choose 3–7 attributes or behaviours that vary across users and relate to the business outcome. Handle missing values and scale continuous variables. Remove outliers only if they would distort cluster centroids.
  3. Run the segmentation — for data-driven segmentation, use k-means clustering via scripts/segmentation_runner.py. For rule-based segmentation, apply the business logic rules and validate that segments are distinct and non-overlapping.
  4. Profile each segment — compute the mean and median for each variable by segment, expressed as % above/below the overall average. Identify the 2–3 defining characteristics of each segment and assign a descriptive name.
  5. Validate and interpret — confirm segments are meaningfully different (silhouette score > 0.3 for clustering) and make business sense. Sanity-check by asking whether you would actually treat each segment differently.
  6. Map to strategy and report — assign each segment to a recommended strategy (Retain & Expand, Monetise, Activate, Win-Back, Sunset). Produce assets/segment_profile_template.md with the profiles and strategic priorities.

Inputs the skill needs

  • User-level data with attributes (demographics, plan type) and behavioural metrics (sessions, revenue, feature usage, recency)
  • Business goal the segmentation will serve
  • Any existing segmentation to validate or replace
  • Minimum of ~100 users per expected segment for clustering to be meaningful

Output

  • scripts/segmentation_runner.py — runs k-means clustering, produces elbow and silhouette plots, assigns segment labels
  • references/segmentation_approaches.md — when to use k-means vs. RFM vs. rule-based; interpretation guide
  • assets/segment_profile_template.md — filled segment profiles with size, key characteristics, recommended strategy, and tracking plan

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides a framework for customer segmentation analysis, including a Python script for profiling data segments and templates for reporting results. No security issues were detected; the provided code uses only standard Python libraries for statistical calculations and file I/O.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/segmentation-analysis