Choose the right clustering algorithm based on data shape, noise, and constraints. Use when you need help with skill clustering guide.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add anubhavg-icpl/vibe --skill skill-clustering-guide --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skill Clustering Guide?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/anubhavg-icpl-skill-clustering-guide)More formats (shields.io, HTML) on the badges page.
---
name: skill-clustering-guide
description: Choose the right clustering algorithm based on data shape, noise, and constraints. Use when you need help with skill clustering guide.
license: CC-BY-NC-SA-4.0
phase: 2
lesson: 7
metadata:
version: 1.0.0
tags: [clustering, k-means, dbscan, hierarchical, gmm, unsupervised]
---
# Clustering Algorithm Selection Guide
Clustering has no single best algorithm. The right choice depends on cluster shape, whether you know the number of clusters, how much noise is in the data, and how large the dataset is.
## Decision Checklist
1. Do you know the number of clusters?
- Yes: K-Means or GMM
- No: DBSCAN (finds clusters automatically), or hierarchical (cut the dendrogram at different levels)
2. What shape are the clusters?
- Roughly spherical (blob-like): K-Means
- Elliptical with different sizes: GMM
- Arbitrary shapes (crescents, rings, chains): DBSCAN
- Nested or hierarchical: hierarchical clustering
3. Does the data contain noise or outliers?
- Yes: DBSCAN (labels noise points explicitly) or GMM (low-probability points are outliers)
- No: K-Means is fine
4. Do you need soft assignments (probabilities)?
- Yes: GMM gives P(cluster | data point) for each cluster
- No: K-Means or DBSCAN give hard assignments
5. How large is the dataset?
- Under 10,000: any algorithm works
- 10,000 to 1,000,000: K-Means (fast), Mini-Batch K-Means (faster)
- Over 1,000,000: Mini-Batch K-Means or BIRCH. Hierarchical is too slow.
## When to use each approach
**K-Means**: the default starting point. Fast (O(n * k * iterations)), simple, and good enough for many problems. Use the elbow method or silhouette score to pick K. Limitations: assumes spherical clusters, sensitive to initialization (use K-Means++ or run multiple times), cannot handle varying cluster sizes well.
**DBSCAN**: best for discovering clusters of arbitrary shape and automatically detecting outliers. Two parameters: eps (neighborhood radius) and min_samples (minimum density). Does not require specifying K. Limitations: struggles when clusters have very different densities, and tuning eps can be tricky. Use a k-distance plot to estimate eps: compute the distance to each point's k-th nearest neighbor, sort, and look for an elbow.
**Hierarchical (Agglomerative)**: builds a tree of merges. Useful when you want to explore cluster structure at multiple granularities (cut the dendrogram at different heights). Ward's linkage works best for compact clusters. Single linkage finds elongated clusters but is sensitive to noise. Limitations: O(n^2) memory and O(n^3) time, so impractical for large datasets.
**GMM (Gaussian Mixture Models)**: soft clustering with probabilistic assignments. Models each cluster as a Gaussian distribution with its own mean and covariance. Better than K-Means when clusters are elliptical or overlapping. Use BIC (Bayesian Information Criterion) to select the number of components. Limitations: assumes Gaussian distributions, can fail on non-convex shapes, sensitive to initialization.
## Evaluating cluster quality (no labels)
| Metric | What it measures | Range | Use when |
|--------|-----------------|-------|----------|
| Silhouette score | Cohesion vs separation | -1 to 1 (higher is better) | Comparing K values or algorithms |
| Inertia (within-cluster SS) | Tightness of clusters | 0 to inf (lower is better) | Elbow method for K-Means |
| BIC / AIC | Model fit with complexity penalty | Lower is better | Choosing number of GMM components |
| Calinski-Harabasz index | Ratio of between to within variance | Higher is better | Quick comparison |
| Davies-Bouldin index | Average similarity between clusters | Lower is better | Penalizes overlapping clusters |
## Common mistakes
- Running K-Means without scaling features (features on larger scales dominate the distance calculation)
- Picking K by eyeballing data in 2D when the actual data is high-dimensional (use silhouette scores)
- Using K-Means on non-spherical clusters (crescent or ring-shaped data needs DBSCAN)
- Setting DBSCAN eps too large (everything in one cluster) or too small (everything is noise)
- Treating cluster labels as ground truth (clustering is exploratory; validate with domain knowledge)
- Running hierarchical clustering on datasets with more than 20,000 points (memory and time explode)
## Quick reference
| Algorithm | Cluster shape | Finds K | Handles noise | Soft assignments | Scalability |
|-----------|--------------|---------|---------------|-----------------|-------------|
| K-Means | Spherical | No (you set K) | No | No | Millions |
| Mini-Batch K-Means | Spherical | No | No | No | Tens of millions |
| DBSCAN | Arbitrary | Yes | Yes | No | Hundreds of thousands |
| Hierarchical | Any (linkage-dependent) | Flexible (cut dendrogram) | Depends on linkage | No | Under 20k |
| GMM | Elliptical | No (you set K) | Partial (low probability) | Yes | Under 100k |
| HDBSCAN | Arbitrary | Yes | Yes | Partial | Hundreds of thousands |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!