免费在 GitHub 公开

crm-hygiene-audit

Use this skill when CRM data is messy and reports cannot be trusted: "audit our CRM", "clean up our CRM data", "duplicates and missing fields", "why is our pipeline report wrong". Checks duplicates, missing required fields, stale and past-due opportunities, ownership gaps, lifecycle stage errors, bad picklist values and unlinked records, quantifies each issue, ranks them by impact on reporting and selling, and produces a cleanup plan plus the rules that stop the mess coming back. Proposes changes for approval, never bulk-edits on its own.

中文简介正在准备中。当前显示原文说明。

prosyo-ai/gtm-skill星标 11(GitHub 11 + cccskills 0)

实测评分未实测

查看安装方法

包含的文件（1）

SKILL.md3.6 KB

SKILL.md（原文）

安装前可以查看交给 AI 代理的指令内容。

Use this when the pipeline report and reality disagree. It produces a ranked list of data problems, a cleanup plan and the rules that keep data clean afterwards.

Inputs

Exports of accounts, contacts and opportunities (or read access).
The fields and stages the business relies on.
The reports leadership uses, so impact can be judged.

The play

1. Inventory issues

Area	Check
Duplicates	Accounts by domain; contacts by email; similar names
Completeness	Required fields empty: industry, size, owner, lifecycle stage, source
Opportunities	Past close dates, no next step, no activity in 30 days, amount empty or zero, stage without required fields
Ownership	Records owned by former employees or unassigned
Lifecycle	Customers without closed-won deals; leads with won deals
Picklists	Free-text values where picklists should be; outdated values
Relationships	Contacts not linked to accounts; deals without contacts
Compliance	Opted-out contacts still in active sequences

2. Quantify and rank

Count each issue and score impact: does it break forecasting, routing, outreach or compliance? Compliance and forecast issues come first.

3. Plan the cleanup

For each issue: the fix, who decides (some merges need a human), whether it can be done in bulk safely, and the order. Merges and deletions are proposed with a sample for approval, then run in batches with a backup export first.

4. Prevent recurrence

Required fields at stage changes, validation rules, duplicate checks on create, ownership reassignment when people leave, a monthly hygiene report.

Output format

Health score: X/100
Issues (ranked): <issue - count - % of records - impact - fix - bulk-safe? - owner>
Cleanup plan: <week by week, with approval points>
Prevention: <rules to add>
Monthly report: <metrics to track>

What good looks like

Every issue has a count and an impact, not just "data is messy".
Opt-out compliance issues are fixed first.
The prevention rules are light enough that reps follow them.
The common mistake is a one-time cleanup sprint with no rules, so the data is dirty again in a quarter.

Rules

MUST export a backup before any bulk change.
MUST get approval with a sample before merges, deletions or bulk updates.
MUST fix opted-out contacts in active sequences immediately.
NEVER permanently delete records without explicit approval.

Example prompts

"Audit these CRM exports and tell me what's wrong, ranked by impact."
"Our forecast is off every month. Check our opportunity data."
"Write the hygiene rules and monthly report for our CRM."

评价

还没有评价。欢迎分享你的使用感受。

无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

同一仓库的技能

abm-account-plan

免费

Use this skill when you run account-based marketing or sales on a short list of named accounts: "build an ABM plan", "account plan for our top 20", "how do we break into this enterprise account", "1:1 ABM program". Picks the accounts and the ABM tier (1:1, 1:few, 1:many), maps the buying group, writes the account insight and value hypothesis, plans coordinated sales and marketing plays by stage, and sets the metrics (engagement, meetings, pipeline) that show it is working.

中文简介正在准备中。当前显示原文说明。