power-bi-model-design-review
Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities.
Install with Tessl CLI
npx tessl i github:github/awesome-copilot --skill power-bi-model-design-review44
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (Power BI data model review) but suffers from missing explicit trigger guidance and lacks the concrete action specificity needed for reliable skill selection. The absence of a 'Use when...' clause is a significant gap that would make it difficult for Claude to know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks to review a Power BI model, analyze DAX performance, check relationship configurations, or optimize a .pbix file'
Include more natural trigger terms users would say: 'DAX', 'measures', 'calculated columns', 'star schema', 'PBIX', 'Power BI Desktop'
List specific concrete actions: 'Reviews relationship cardinality, identifies missing indexes, validates star schema design, checks for circular dependencies, analyzes measure performance'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Power BI data model) and some actions (design review, evaluating architecture, relationships, optimization), but lacks concrete specific actions like 'analyze star schema compliance' or 'identify circular dependencies'. | 2 / 3 |
Completeness | Describes what it does (Power BI model review) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'Power BI' and 'data model' which are relevant keywords, but misses common variations users might say like 'DAX', 'measures', 'calculated columns', 'PBIX', or 'tabular model'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Power BI data model' is fairly specific and wouldn't conflict with generic document or code skills, but could overlap with other data modeling or BI-related skills without clearer triggers. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an exhaustive but verbose reference document that explains Power BI data modeling concepts Claude already understands. It provides extensive checklists and frameworks but lacks concrete, executable examples (no actual DAX code, no specific commands). The content would benefit significantly from condensing to essential guidance and splitting detailed checklists into separate reference files.
Suggestions
Reduce content by 70%+ by removing explanations of concepts Claude knows (star schema basics, what referential integrity means) and keeping only project-specific patterns or non-obvious guidance
Add concrete, executable examples: actual DAX code snippets, specific Power BI Desktop actions, real validation queries that can be copy-pasted
Split detailed checklists and templates into separate reference files (e.g., CHECKLISTS.md, TEMPLATES.md) and keep SKILL.md as a concise overview with clear navigation
Add explicit validation steps with specific tools or queries to verify findings (e.g., 'Run this DAX query to identify circular relationships: ...')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with extensive checklists and templates that explain concepts Claude already knows (what star schema is, what referential integrity means, basic data modeling principles). The content is heavily padded with checkbox lists that could be condensed significantly. | 1 / 3 |
Actionability | Provides structured checklists and frameworks but lacks concrete, executable examples. No actual DAX code, no specific Power BI commands, no copy-paste ready solutions. The guidance is descriptive rather than instructive with specific implementations. | 2 / 3 |
Workflow Clarity | Has a phased review process (Phase 1, 2, 3) with clear sections, but lacks explicit validation checkpoints or feedback loops. The workflow describes what to assess but not how to verify findings or iterate on issues discovered. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. All content is inline despite being over 300 lines. Content that could be split into separate reference files (checklists, templates, specialized review types) is all embedded in one document. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.