setup-datamodel
This skill should be used when the user asks to "create Dataverse tables", "set up the data model", "setup dataverse", "create tables for my site", "setup dataverse schema", "create the database", "build my data model", or wants to create Dataverse tables, columns, and relationships for their Power Pages site based on a data model proposal.
88
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage and completeness, providing extensive natural language phrases users might say and clearly stating both what the skill does and when to use it. Its main weakness is that the capability description could be more specific about the concrete actions performed beyond just 'create tables, columns, and relationships'. The description also uses a passive/instructional voice rather than third person active voice, though this is a minor issue.
Suggestions
Expand the capability description with more specific actions, e.g., 'Creates Dataverse tables, defines column types and constraints, configures entity relationships, and sets up security roles for Power Pages sites based on a data model proposal.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description mentions 'create Dataverse tables, columns, and relationships' which names the domain and some actions, but doesn't list comprehensive specific actions beyond creation (e.g., no mention of configuring permissions, setting data types, defining option sets, etc.). | 2 / 3 |
Completeness | The description explicitly answers both 'what' (create Dataverse tables, columns, and relationships for Power Pages sites based on a data model proposal) and 'when' (with a clear list of trigger phrases prefaced by 'This skill should be used when'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'create Dataverse tables', 'set up the data model', 'setup dataverse', 'create tables for my site', 'setup dataverse schema', 'create the database', 'build my data model'. These are varied and natural phrasings. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Dataverse and Power Pages, creating a clear niche. Terms like 'Dataverse tables', 'Power Pages site', and 'dataverse schema' are distinct enough to avoid conflicts with generic database or data modeling skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill for a complex multi-phase workflow. It excels at workflow clarity with explicit validation checkpoints, user approval gates, and error handling patterns. The progressive disclosure is excellent, keeping the main skill as an orchestration overview while delegating detailed templates and schemas to reference files. The main weakness is moderate verbosity — the skill could be tightened by reducing repetitive notes and consolidating some sections.
Suggestions
Consolidate the repeated 'report failures without rollback' and 'token refresh' notes into a single reference in the 'Important Notes' section rather than restating in individual phases.
Remove the 'Output' lines at the end of each phase — they restate what the phase already describes and add ~16 lines of redundant content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300+ lines) with some repetitive elements (e.g., restating 'report failures without rollback' multiple times, the 'Output' lines at the end of each phase). However, most content is necessary given the complexity of the 8-phase workflow. Some sections like Phase 2's detailed option table and Phase 4's approval options could be tightened. It doesn't over-explain concepts Claude knows, but the verbosity adds up. | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout (specific `node` script invocations with actual paths and API endpoints, exact OData paths, JSON body references). Each phase has clear actions with specific tool usage (Task, AskUserQuestion, Write). Commands are copy-paste ready with placeholder patterns that are well-defined. | 3 / 3 |
Workflow Clarity | The 8-phase workflow is clearly sequenced with explicit validation checkpoints: token refresh before creation (5.1), existence checks before creating (5.2), verification after creation (8.2), and explicit user approval gates at phases 2, 4, 5, and 8. Error handling is addressed (report failures, continue without rollback). The progress tracking table provides a clear overview of all phases upfront. | 3 / 3 |
Progressive Disclosure | The skill appropriately references external files for detailed content: `references/odata-api-patterns.md` for JSON body templates, `references/dataverse-prerequisites.md` for prerequisite steps, `agents/data-model-architect.md` for agent definition, and `references/datamodel-manifest-schema.md` for schema details. All references are one level deep and clearly signaled with descriptive context about what each contains. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- microsoft/power-platform-skills
- Commit
1132a35
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.