Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gulmezeren2-byte/powerbi-dax
Measures over calculated columns, filter context, and the time-intelligence pattern that breaks on a non-standard calendar.
Passed 20 of 23 test cases with the skill, and 20 of 23 without it.
1 fixed19 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
We need a DAX measure in Power BI to compute the percentage of total sales contributed by each product category, where the denominator must ignore filters applied on `Product[Category]` but respect filters on `Date[Year]` and `Store[Region]`. A developer recommends `CALCULATE(SUM(Sales[Amount]), ALL(Sales))`. Why is using `ALL(Sales)` problematic, and what DAX function or pattern should be used instead to clear filters strictly on the Category hierarchy while retaining date and region filters?
| Checked | Without skill | With skill |
|---|---|---|
| Explain that `ALL(Sales)` removes filters from the entire sales table. | Passed | Passed |
| Recommend using `ALL(Product[Category])` to remove filters specifically from the category column. | Missed | Passed |
The instructions your model reads when the skill loads.
Measures over calculated columns, filter context, and the time-intelligence pattern that breaks on a non-standard calendar.
test cases passed, vs 20 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.