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.
Install with Tessl CLI
npx tessl i github:microsoft/power-platform-skills --skill setup-datamodel88
Quality
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 is a strong skill description with excellent trigger term coverage and clear 'when to use' guidance. The main weakness is that the 'what it does' portion could be more specific about the concrete actions and capabilities (e.g., what types of columns, specific relationship configurations, validation rules). The description leads with trigger terms rather than capabilities, which is slightly unconventional but functional.
Suggestions
Restructure to lead with specific capabilities first (e.g., 'Creates Dataverse tables with text/number/lookup columns, configures one-to-many and many-to-many relationships, sets up schema for Power Pages sites'), then follow with the 'Use when...' clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Dataverse tables) and some actions ('create tables', 'set up data model', 'create columns and relationships'), but lacks comprehensive detail about specific capabilities like what types of columns, relationship types, or schema operations are supported. | 2 / 3 |
Completeness | Explicitly answers both what (create Dataverse tables, columns, and relationships for Power Pages sites based on a data model proposal) and when (lists specific trigger phrases with 'should be used when'). Has clear explicit trigger guidance. | 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 realistic phrases users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Dataverse and Power Pages specifically. The combination of 'Dataverse', 'Power Pages', and 'data model proposal' creates a distinct trigger profile unlikely to conflict with generic database or table creation 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 strong, well-structured skill with excellent workflow clarity and actionability. The 8-phase approach with explicit user approval gates and validation checkpoints demonstrates best practices for complex, destructive operations. Minor verbosity in repeated instructions (token refresh, progress tracking reminders) prevents a perfect conciseness score, but overall the skill is production-ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy (e.g., repeating token refresh instructions multiple times, verbose phase descriptions). Some sections could be tightened, though it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | Provides fully executable PowerShell commands, specific API endpoints, concrete JSON body references, and exact tool invocations. Commands are copy-paste ready with clear variable substitution patterns. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with 8 clearly sequenced phases, explicit validation checkpoints (Phase 5 pre-creation checks, Phase 8 verification), decision points requiring user approval, and clear error handling guidance (report failures without rollback). | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview and appropriate references to external files (odata-api-patterns.md, dataverse-prerequisites.md, datamodel-manifest-schema.md). References are one level deep and clearly signaled with file paths. | 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 | |
- 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.