Use to enforce stage definitions, next-step requirements, and data completeness
Scanned 2/12/2026
Install to Claude Code
npx -y skills add gtmagents/gtm-agents --skill crm-hygiene --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Crm Hygiene?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gtmagents-crm-hygiene)More formats (shields.io, HTML) on the badges page.
---
name: crm-hygiene
description: Use to enforce stage definitions, next-step requirements, and data completeness
across the pipeline.
---
# CRM Hygiene Playbook Skill
## When to Use
- Preparing for pipeline inspections or forecast calls.
- Auditing data quality before exec reviews or board decks.
- Coaching reps on consistent CRM updates.
## Framework
1. **Stage Definitions** – document entry/exit criteria and mandatory fields for each stage.
2. **Data Completeness** – ensure next steps, close dates, contacts, and products are filled.
3. **Aging Thresholds** – define acceptable days-in-stage and automatic escalation triggers.
4. **Exception Handling** – outline how to request overrides or re-open closed deals.
5. **Monitoring** – schedule hygiene dashboards + alerts for missing data.
## Templates
- Stage checklist (fields + approvers per stage).
- Hygiene scorecard for reps/managers.
- Escalation request form for data overrides.
## Tips
- Automate reminders for missing next steps or overdue close dates.
- Pair with forecasting enablement to keep assumptions grounded.
- Share hygiene scores transparently to drive accountability.
---
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!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.