setup-datamodel
Creates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal. Use when the user wants to set up the data model, create database tables, or build the Dataverse schema for their site.
92
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 is a well-crafted skill description that clearly specifies concrete actions (creating tables, columns, relationships), targets a distinct technology domain (Dataverse/Power Pages), and includes an explicit 'Use when' clause with natural trigger terms. It follows the third-person voice convention and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Creates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal.' This clearly names the domain (Dataverse/Power Pages) and specific actions (tables, columns, relationships). | 3 / 3 |
Completeness | Clearly answers both 'what' (creates Dataverse tables, columns, and relationships for a Power Pages site) and 'when' (explicit 'Use when' clause covering data model setup, database table creation, and Dataverse schema building). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'data model', 'database tables', 'Dataverse schema', 'tables', 'columns', 'relationships', 'Power Pages site'. These cover common variations of how a user would phrase this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Dataverse tables/schema specifically for Power Pages sites. The combination of 'Dataverse', 'Power Pages', and 'data model proposal' makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 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 clear error handling policies. The progressive disclosure is well-executed with appropriate delegation to reference files. The main weakness is moderate verbosity — some sections could be tightened without losing clarity, particularly around repeated mentions of token refresh and the detailed progress tracking table that largely duplicates phase headers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long (~300 lines) but most content is necessary given the complexity of the 8-phase workflow. However, there's some redundancy — token refresh is mentioned multiple times, the progress tracking table duplicates phase descriptions, and some explanatory text could be tightened (e.g., Phase 2's option table format is verbose for what could be a simpler prompt). | 2 / 3 |
Actionability | The skill provides concrete, executable commands throughout (specific node script invocations with arguments, exact API endpoints, JSON body examples, specific tool invocations). Each phase has clear actions with copy-paste-ready commands and references to external files for full JSON templates. | 3 / 3 |
Workflow Clarity | The 8-phase workflow is clearly sequenced with explicit validation checkpoints: pre-creation checks verify existing tables before creating (Phase 5), token refresh before batch operations, verification queries after creation (Phase 8.2), and explicit user approval gates at 4 key decision points. Error handling is addressed with a 'report failures without rollback' policy and the feedback loop of 'Request changes → modify → re-present' in Phase 4. | 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 auth setup, `agents/data-model-architect.md` for agent definition, and `references/datamodel-manifest-schema.md` for the manifest schema. All references are one level deep and clearly signaled with their purpose. | 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
48e49c4
- 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.