crm-setup_skill
- Python
2
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill mikefilsaime-groove/clickcampaigns-for-claude-code-in-cursor --skill crm-setup- SKILL.md3.8 KB
Overview
This skill creates practical, technical CRM implementation plans for HubSpot, Salesforce, Pipedrive, and similar platforms. It translates business processes into object models, field mappings, pipelines, automations, and migration steps to deliver a production-ready configuration. The output is focused on implementation tasks, data integrity, and reporting readiness.
How this skill works
I inspect the existing sales and marketing process, required integrations, and data sources, then design a CRM object architecture that reflects real-world relationships (contacts, companies, deals, activities, and custom objects). I produce field-level mappings, pipeline stage definitions with clear entry/exit criteria, automation rules, and a step-by-step data migration and verification plan. The deliverable includes checklists for permissions, integrations, and reporting so teams can implement and validate the configuration.
When to use it
- When you need a technical CRM implementation plan for HubSpot, Salesforce, Pipedrive, or similar platforms
- When mapping source data for migration or designing field-level data architecture
- When defining sales/marketing pipelines and stage criteria
- When automating lead routing, task creation, or deal progression
- When preparing dashboards and reports that rely on consistent data structure
Best practices
- Start with a process-first analysis: document current workflows before changing structure
- Model objects and relationships to match how your teams work (core + custom objects)
- Define precise stage criteria and win/loss reasons to reduce ambiguity
- Map every source field to a CRM field and include validation and deduplication rules
- Create automation rules that reduce manual steps but include guardrails and audit fields
Example use cases
- Design CRM object model for a B2B SaaS company with Accounts, Contacts, Opportunities, and Subscription custom object
- Create a migration plan mapping legacy CSVs to CRM fields including dedupe and validation steps
- Define a sales pipeline with stage criteria, auto-advance rules, and tracked win/loss reasons
- Configure automations for lead assignment, meeting task creation, and email sequences tied to pipeline stages
- Prepare reporting schema and dashboards for funnel conversion, deal velocity, and customer LTV
FAQ
Yes. Plans include platform-specific recommendations (workflow rules, process builder/flows, or automation sequences) and where to implement them based on platform capabilities.
How do you handle existing dirty data during migration?
I specify a staged migration: profiling, cleaning (standardization and dedupe), a test import, verification scripts, and a final cutover with rollback steps.
Will this include user permissions and role setup?
Yes. The plan lists role-based access control, sharing rules, and recommended user profiles to match data visibility needs.