Menu

Individual skill

crm-health-scoring

0upvotes

Use this skill when leaders need a repeatable measure of CRM reliability, its trend, and the defects driving it. Produces a deterministic health score, object- and rule-level diagnostics, a confidence statement, and a prioritized remediation queue.

skills/ryan-iyengar/crm-health-scoring/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Use this when a team needs to measure whether CRM reliability is improving. Produce a reproducible score and diagnosis, not a decorative grade.

## Define health as rules

Translate “clean CRM” into explicit checks across identity, ownership, completeness, pipeline integrity, process conformance, and integration drift. Every rule must declare its population, condition, severity, evidence, exclusions, and owner.

Measure only fields and relationships that influence execution or decisions. Do not reward filling optional fields merely because they are easy to count. Keep rule definitions versioned; a changed rule creates a new baseline and must not be presented as organic improvement or decline.

## Score the population

Calculate rule failure rates on eligible records. Weight by business impact, not raw finding count. A handful of duplicate accounts splitting live opportunities can matter more than thousands of missing optional fields.

Score objects separately before rolling them up. Contacts, accounts, opportunities, and activities have different populations and failure modes. Use [references/scoring-model.md](references/scoring-model.md) for a deterministic 0–100 model and minimum sample rules.
Back to top