nickmeron/skills/explore-metadata
skills/explore-metadata/SKILL.md
Deep-dive into the metadata of a Dynamics 365 entity — fields, types, option sets, relationships, keys. Use this when the user wants to understand an entity's structure or says "show me the fields on...", "what does the X entity look like?", "explore the metadata".
$ install --global
skillsauthnpx skillsauth add nickmeron/Dataverse-MCP-Server skills/explore-metadataInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 23, 2026, 6:29 PM187.2s1 file scanned
SKILL.md
- description:
- Deep-dive into the metadata of a Dynamics 365 entity — fields, types, option sets, relationships, keys. Use this when the user wants to understand an entity's structure or says "show me the fields on...", "what does the X entity look like?", "explore the metadata".
- allowed-tools:
- mcp__dynamics365__list_environments, mcp__dynamics365__select_environment, mcp__dynamics365__list_entities, mcp__dynamics365__get_entity_details, mcp__dynamics365__get_entity_attributes, mcp__dynamics365__get_entity_relationships, mcp__dynamics365__get_entity_keys, mcp__dynamics365__get_picklist_options, mcp__dynamics365__get_global_option_sets, mcp__dynamics365__get_global_option_set_details
The user wants to explore or understand the metadata structure of their Dynamics 365 environment.
Argument provided: $ARGUMENTS
Process
1. Select environment
Call list_environments and ask the user which environment to explore. Call select_environment.
2. Identify what to explore
- If the user names a specific entity → proceed to deep-dive
- If the user is unsure → use
list_entities(optionally withcustom_only: true) to show what's available - If searching by keyword → use
list_entitieswith a filter
3. Deep-dive: Entity overview
For the target entity, gather all metadata in parallel where possible:
get_entity_details→ basic info (display name, logical name, primary ID/name, system vs custom)get_entity_attributes(withinclude_option_sets: true) → all fields with their types and option set valuesget_entity_relationships→ all One-to-Many, Many-to-One, Many-to-Many relationshipsget_entity_keys→ alternate keys
4. Present the metadata
Format the output clearly — think of it like the tabs in the metadata viewer app:
Entity Summary
- Display Name, Logical Name, Entity Set Name (plural for API), Object Type Code
- System vs Custom
- Primary ID field, Primary Name field
Fields
Present as a table: | Logical Name | Display Name | Type | Required | Custom | |---|---|---|---|---| Sort by logical name. Highlight:
- Required fields (RequiredLevel = ApplicationRequired or SystemRequired)
- Custom fields (IsCustomAttribute = true)
- Lookup fields — note what entity they point to (from relationships)
Option Sets
For every Picklist / Status / State field, show the values: | Value | Label | |---|---| Group by field name.
Relationships
Show separately:
- One-to-Many: This entity → related entity (field)
- Many-to-One: Related entity → this entity (field)
- Many-to-Many: Entity1 ↔ Entity2 (schema name)
Alternate Keys
If any exist, list the key name and which fields compose it.
5. Offer next steps
After presenting, ask if the user wants to:
- Explore a specific field's option set values in more detail
- See the relationships for a related entity
- Build a query against this entity
- Check official docs about this entity type
Tips
- Custom entities typically have a publisher prefix (e.g.
new_,contoso_) - The
EntitySetNameis the plural name used in API URLs — this is whatquery_recordsneeds - Look for
_valuesuffix fields — these are the raw GUID values of lookup fields statecode(State) andstatuscode(Status Reason) exist on every entity — always show their option values
Related Skills
nickmeron/skills/bulk-delete
testing
VerifiedTrustedCommunity
Create, monitor, and manage bulk deletion jobs in Dynamics 365. Use when asked "bulk delete", "delete all records of type X", "create a bulk delete job", "check bulk delete status", "cancel bulk delete", "why did bulk delete fail".
6SKILL.mdUpdated May 5, 2026
nickmeron/skills/summarize-entity
data-ai
VerifiedTrustedCommunity
Produce a business-readable summary of a Dynamics 365 record or set of records. Uses metadata to understand the schema before querying.
6SKILL.mdUpdated Apr 23, 2026
nickmeron/skills/security-audit
testing
VerifiedTrustedCommunity
Investigate users, security roles, teams, and permissions in Dynamics 365. Use when asked "who has access to...", "what roles does X have?", "compare roles", or "show me users".
6SKILL.mdUpdated Apr 23, 2026
nickmeron/skills/query-records
data-ai
VerifiedTrustedCommunity
Query Dynamics 365 records using natural language. Translates questions into OData queries with metadata-aware field selection.
6SKILL.mdUpdated Apr 23, 2026