writing-dax-measures
This skill should be used when the user asks to "write DAX measures", "create Power BI calculations", "help with DAX formulas", "write time intelligence", or mentions aggregations, filters, or DAX performance. Ensures correct syntax, optimal performance, and best practices on the first attempt.
Install with Tessl CLI
npx tessl i github:back1ply/LLM-Skills --skill writing-dax-measuresOverall
score
84%
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
72%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 terms and distinctiveness, providing excellent coverage of DAX/Power BI-specific keywords that users would naturally use. However, it inverts the typical structure by leading with 'when' and ending with vague quality claims rather than concrete capabilities. The description would benefit from explicitly listing what actions the skill performs (e.g., 'create calculated columns, build iterator functions, write CALCULATE expressions').
Suggestions
Add specific concrete actions the skill performs, such as 'Creates calculated columns, builds time intelligence functions, writes CALCULATE expressions, optimizes iterator patterns'
Restructure to lead with capabilities (what it does) before the trigger conditions (when to use it) for better clarity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (DAX/Power BI) and mentions some actions like 'write DAX measures', 'create calculations', but the actual capabilities are vague - 'Ensures correct syntax, optimal performance, and best practices' describes quality attributes rather than concrete actions like 'create calculated columns, build time intelligence functions, optimize CALCULATE statements'. | 2 / 3 |
Completeness | Has a strong 'when' clause with explicit triggers ('Use when the user asks to...'), but the 'what' is weak - it only describes quality outcomes ('correct syntax, optimal performance, best practices') rather than specific capabilities. The description inverts the typical structure but still lacks concrete action descriptions. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'write DAX measures', 'create Power BI calculations', 'DAX formulas', 'time intelligence', 'aggregations', 'filters', 'DAX performance'. These are realistic phrases users would naturally use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with DAX and Power BI specific terminology. Terms like 'DAX measures', 'Power BI calculations', 'time intelligence' are highly specific and unlikely to conflict with other skills. The domain is well-defined and distinct. | 3 / 3 |
Total | 10 / 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 DAX skill with excellent actionability through concrete code examples and clear anti-pattern guidance. The workflow is well-defined with explicit validation checkpoints. Minor verbosity in conceptual explanations (context transition, BLANK behavior) could be trimmed since Claude understands these concepts, but overall the skill is highly effective.
Suggestions
Trim conceptual explanations in 'Context Transition Rules' and 'BLANK Handling' sections - Claude understands these concepts; focus on the rules/patterns only
Consider moving the 'Critical Understanding' subsection content into terse bullet points rather than numbered explanations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some explanatory content Claude already knows (e.g., explaining what context transition is, how BLANK works conceptually). Tables and patterns are efficient, but sections like 'Critical Understanding' could be trimmed. | 2 / 3 |
Actionability | Excellent executable code examples throughout with copy-paste ready DAX patterns. Clear ✅/❌ comparisons show exactly what to do and avoid. The Quick Reference Table provides immediately usable patterns for common tasks. | 3 / 3 |
Workflow Clarity | Clear mandatory pre-generation workflow with numbered steps, explicit pre-submission validation checklist with checkboxes, and logical sequencing throughout. The workflow includes verification steps (schema validation, checklist before submission). | 3 / 3 |
Progressive Disclosure | Well-structured with clear overview, appropriately references external files for advanced patterns (patterns.md) and debugging (debugging.md). Content is organized into logical sections with tables for quick scanning. One-level-deep references are clearly signaled. | 3 / 3 |
Total | 11 / 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.