crm-best-practices

Codify CRM customization governance for Dynamics 365 and Dataverse projects.

Updated Jun 11, 2026
One-click install
npx skills add https://github.com/klemensms/mcp-consultant-tools --skill crm-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crm-best-practices
Source: https://github.com/klemensms/mcp-consultant-tools/tree/main/.claude/skills/crm-best-practices
Command: npx skills add https://github.com/klemensms/mcp-consultant-tools --skill crm-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines consistent CRM customization guidelines to reduce rework and errors across Dynamics 365, Dataverse, and Power Platform projects.

Core Features & Use Cases

  • Standardized naming conventions for tables and columns
  • Prefixed reference data and robust entity design practices
  • Guidance for plugins, flows, and integrations across Azure services

Quick Start

Implement a new CRM entity with sic_ prefixes, apply naming conventions, and document the data model according to the CRM best practices.

Frequently Asked Questions about crm-best-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the best practices for naming conventions in Dynamics 365 and Dataverse?

Standard CRM naming conventions enforce schema prefixes like sic_ for tables and columns to maintain consistent entity design and reduce rework across teams in Dataverse.

How do I standardize reference data and entity design in a Power Platform project?

You standardize reference data in Power Platform by applying RefData conventions and lifecycle checks during entity creation to ensure robust schema design and consistent deployments.

Does this CRM governance approach apply to plugin development and Azure integrations?

Yes, CRM customization governance provides specific plugin development guidelines and automation standards to ensure consistent security and deployment practices across Azure service integrations.

Can I use these CRM standards for team-based Dataverse customization projects?

Yes, these CRM standards apply to team-based Dataverse projects by codifying table standards and entity design practices to streamline customization governance across multiple developers.

Why do I need schema prefixes and lifecycle checks for Dataverse entity creation?

You need schema prefixes and lifecycle checks during Dataverse entity creation to enforce consistent security practices, prevent naming collisions, and validate reference data conventions before deployment.