@luquimbo/bi-superpowers 1.0.0 → 1.1.1

package/skills/dax/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "dax"
 description: "Use when the user asks about DAX Skill, especially phrases like \"DAX\", \"CALCULATE\", \"time intelligence\", \"SUMX\", \"context transition\", \"Power BI formula\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/dax.md instead. -->
@@ -23,10 +23,13 @@ You are a **DAX Expert** specializing in efficient measure design, context manip
 
 ## MANDATORY RULES
 1. **USE VARIABLES.** Always use VAR/RETURN for any calculation used more than once.
-2. **FILTER ON DIMENSIONS.** Never filter directly on fact tables when a dimension exists.
-3. **SAFE DIVISION.** Always use DIVIDE() instead of / operator.
-4. **EXPLAIN CONTEXT.** Help users understand filter vs row context.
-5. **PERFORMANCE FIRST.** Suggest optimizations proactively.
+2. **FINAL VARIABLE IS `Result`.** Every measure with VAR/RETURN ends with `VAR Result = ... RETURN Result` (SQLBI convention).
+3. **PASCALCASE FOR VARIABLES.** No underscore prefix. `TotalSales`, not `_TotalSales`.
+4. **`@` PREFIX FOR TEMPORARY COLUMNS.** When adding columns inside `ADDCOLUMNS` or `SUMMARIZECOLUMNS`, prefix with `@` (e.g., `@Rank`, `@Sales`).
+5. **FILTER ON DIMENSIONS.** Never filter directly on fact tables when a dimension exists.
+6. **SAFE DIVISION.** Always use DIVIDE() instead of / operator.
+7. **EXPLAIN CONTEXT.** Help users understand filter vs row context.
+8. **PERFORMANCE FIRST.** Suggest optimizations proactively.
 
 ---
 
@@ -35,14 +38,26 @@ Best practices for writing and optimizing DAX in Power BI.
 
 ## Naming Conventions
 
+Conventions follow the SQLBI Style Guide. The principle: **measure names speak business language, code reads top-to-bottom**.
+
 | Element | Convention | Example |
 |---------|------------|---------|
-| Measures | PascalCase, descriptive | `TotalSalesAmount`, `AvgOrderValue` |
-| Calculated Columns | PascalCase, table prefix if ambiguous | `Sales[FullDate]`, `Product Category` |
-| Variables | Underscore prefix + PascalCase | `_Result`, `_FilteredTable`, `_CurrentDate` |
-| Measure Tables | `_Measures` or `Metrics` | `_Measures[TotalSales]` |
-| KPI Measures | Prefix with category | `KPI_Sales_Target`, `KPI_Margin_Actual` |
-| Debug/Test Measures | Underscore prefix | `_Debug_RowCount`, `_Test_SalesTotal` |
+| Measures | Auto-explicative, no prefix | `Sales`, `Margin %`, `Sales YTD` |
+| Time intelligence suffix | Space + period | `Sales YTD`, `Sales PY`, `Sales MTD` |
+| Variations | Space + variation + `%` | `Sales YoY %`, `Sales MoM %` |
+| Ratios | Space + `%` | `Margin %`, `Conversion %` |
+| Calculated Columns | Natural name | `Full Date`, `Product Category` |
+| Variables | PascalCase, no prefix | `TotalSales`, `FilteredTable`, `CurrentDate` |
+| Final variable | Always `Result` | `VAR Result = ...` `RETURN Result` |
+| Temporary columns | Prefix `@` | `@Rank`, `@Sales`, `@Delta` |
+| Measure Tables | Prefix `_`, hidden | `_Measures`, `_KPIs` |
+| Debug/Test Measures | `_` prefix, hidden | `_Debug Row Count` |
+
+**Anti-patterns:**
+- `Total Sales`, `Sum of Sales` (redundant, the aggregation is implied)
+- `_Result`, `_FilteredTable` (no underscore prefix on variables)
+- `YTD_Sales`, `Sales_YTD` (use space-separated suffix)
+- `MarginPct`, `MarginRatio` (use `Margin %` instead)
 
 ---
 
@@ -108,25 +123,47 @@ SumViaMeasure = SUMX(Products, [TotalSales])  // [TotalSales] filters to each pr
 - Intermediate calculations
 - Debugging complex measures
 
+**Conventions (SQLBI Style Guide):**
+- **PascalCase** without underscore prefix
+- **Final variable always `Result`** — clearly marks the measure's output
+- **Temporary columns prefixed with `@`** to distinguish from model columns
+
 ```dax
--- Good: Use variables
-SalesYoY =
-VAR _CurrentSales = [TotalSales]
-VAR _PriorYearSales =
+-- Good: PascalCase vars, Result final var
+Sales YoY % =
+VAR CurrentSales = [Sales]
+VAR PriorYearSales =
     CALCULATE(
-        [TotalSales],
+        [Sales],
         SAMEPERIODLASTYEAR('Date'[Date])
     )
-VAR _Change = _CurrentSales - _PriorYearSales
-RETURN
-    DIVIDE(_Change, _PriorYearSales)
+VAR Delta = CurrentSales - PriorYearSales
+VAR Result = DIVIDE(Delta, PriorYearSales)
+RETURN Result
+
+-- Good: Temporary column with @ prefix
+Top 10 Products Sales =
+VAR RankedProducts =
+    ADDCOLUMNS(
+        VALUES(Product[Product Name]),
+        "@Rank", RANKX(VALUES(Product[Product Name]), [Sales], , DESC)
+    )
+VAR Top10 = FILTER(RankedProducts, [@Rank] <= 10)
+VAR Result = SUMX(Top10, [Sales])
+RETURN Result
 
 -- Bad: Repeated calculations (slower, harder to read)
-SalesYoY_Bad =
+Sales YoY Bad =
 DIVIDE(
-    [TotalSales] - CALCULATE([TotalSales], SAMEPERIODLASTYEAR('Date'[Date])),
-    CALCULATE([TotalSales], SAMEPERIODLASTYEAR('Date'[Date]))
+    [Sales] - CALCULATE([Sales], SAMEPERIODLASTYEAR('Date'[Date])),
+    CALCULATE([Sales], SAMEPERIODLASTYEAR('Date'[Date]))
 )
+
+-- Bad: Underscore prefix on variables (old convention)
+Sales YoY Old =
+VAR _CurrentSales = [Sales]
+VAR _PriorYearSales = CALCULATE([Sales], SAMEPERIODLASTYEAR('Date'[Date]))
+RETURN DIVIDE(_CurrentSales - _PriorYearSales, _PriorYearSales)
 ```
 
 ### Safe Division
@@ -635,29 +672,30 @@ Running_Total = CALCULATE(...)  -- Use measures
 ## Formatting Standards
 
 ```dax
--- Simple measure (one line)
-TotalSales = SUM(Sales[Amount])
+-- Simple measure (one line, no VAR/RETURN needed)
+Sales = SUM(Sales[Amount])
 
 -- Medium complexity (few lines)
-Margin = DIVIDE([Profit], [Revenue], 0)
+Margin % = DIVIDE([Profit], [Revenue], 0)
 
--- Complex measure (structured with comments)
-ComplexMeasure =
-// Purpose: Calculate year-over-year change with handling for missing prior year
-VAR _CurrentSales = [TotalSales]
-VAR _PriorYearSales =
+-- Complex measure (structured with comments, Result as final var)
+Sales YoY % =
+// Purpose: Year-over-year change with handling for missing prior year
+VAR CurrentSales = [Sales]
+VAR PriorYearSales =
     CALCULATE(
-        [TotalSales],
+        [Sales],
         SAMEPERIODLASTYEAR('Date'[Date])
     )
-VAR _Change = _CurrentSales - _PriorYearSales
-VAR _HasPriorYear = NOT(ISBLANK(_PriorYearSales))
-RETURN
+VAR Delta = CurrentSales - PriorYearSales
+VAR HasPriorYear = NOT(ISBLANK(PriorYearSales))
+VAR Result =
     IF(
-        _HasPriorYear,
-        DIVIDE(_Change, _PriorYearSales),
+        HasPriorYear,
+        DIVIDE(Delta, PriorYearSales),
         BLANK()
     )
+RETURN Result
 ```
 
 ---

package/skills/dax-doctor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "dax-doctor"
 description: "Use when the user asks about DAX Doctor Skill, especially phrases like \"debug DAX\", \"wrong result\", \"DAX error\", \"slow measure\", \"context issue\", \"depurar DAX\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/dax-doctor.md instead. -->

package/skills/dax-udf/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "dax-udf"
 description: "Use when the user asks about DAX User-Defined Functions (UDFs), especially phrases like \"UDF\", \"DEFINE FUNCTION\", \"DAX Lib\", \"NAMEOF\", \"reusable DAX\", \"VAL parameter\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/dax-udf.md instead. -->

package/skills/deployment/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "deployment"
 description: "Use when the user asks about Deployment Skill, especially phrases like \"deploy\", \"CI/CD\", \"ALM\", \"git integration\", \"environment\", \"desplegar\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/deployment.md instead. -->

package/skills/excel-formulas/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "excel-formulas"
 description: "Use when the user asks about Excel Formulas Skill, especially phrases like \"Excel formula\", \"XLOOKUP\", \"dynamic array\", \"LET formula\", \"named range\", \"conditional formatting formula\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/excel-formulas.md instead. -->

package/skills/fabric-scripts/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "fabric-scripts"
 description: "Use when the user asks about Fabric Scripts Skill, especially phrases like \"Fabric scripts\", \"download dataflows\", \"diagnose connection\", \"TMDL sync\", \"scripts de Fabric\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/fabric-scripts.md instead. -->

package/skills/fast-standard/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "fast-standard"
 description: "Use when the user asks about FAST Standard Skill, especially phrases like \"FAST Standard\", \"financial model\", \"spreadsheet modeling best practices\", \"model audit\", \"calculation block\", \"modelo financiero\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/fast-standard.md instead. -->

package/skills/governance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "governance"
 description: "Use when the user asks about Governance Skill, especially phrases like \"naming convention\", \"governance\", \"documentation standard\", \"display folder\", \"convención de nombres\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/governance.md instead. -->
@@ -30,57 +30,100 @@ You are a **BI Governance Specialist** who establishes and enforces naming conve
 
 ## Naming Conventions
 
+Conventions follow SQLBI Style Guide, Chris Webb, and Microsoft's semantic model best practices. The guiding principle: **user-visible names speak business language, technical elements stay hidden**.
+
 ### Tables
 
+**Rules:**
+1. **No technical prefixes.** Never use `dim`, `fact`, `tbl`, `t_`. These are for developers; users see tables in visuals and shouldn't read SQL jargon.
+2. **Dimensions singular, facts plural.** A dimension describes one entity (`Customer`, `Product`, `Date`). A fact contains many events (`Sales`, `Orders`, `Transactions`).
+3. **Spaces allowed for user-visible tables.** Use natural language: `Purchase Orders`, not `PurchaseOrders` or `PO_Header`.
+4. **Business names, not source names.** Match the language users speak, not the database schema.
+
 | Type | Convention | Example | Anti-Pattern |
 |------|-----------|---------|-------------|
-| Dimension | Singular noun | `Customer`, `Product`, `Date` | `Customers`, `DimCustomer`, `tbl_Customer` |
-| Fact | Singular noun or verb | `Sale`, `Order`, `Inventory` | `FactSales`, `fct_Sales` |
-| Bridge | Prefix with `Bridge` | `BridgeCustomerRegion` | `CustomerRegion_Bridge` |
-| Measure table | Prefix `_` | `_Measures`, `_KPIs` | `Measures Table`, `CalcMeasures` |
-| Config/Utility | Prefix `_` | `_Parameters`, `_DateConfig` | `Parameters` |
-| Calculated table | Document clearly | `CalendarTable` (with comment) | Unmarked calculated tables |
+| Dimension | Singular, business name | `Customer`, `Product`, `Date` | `Customers`, `DimCustomer`, `tbl_Customer` |
+| Fact | Plural, business name | `Sales`, `Orders`, `Transactions` | `FactSales`, `fct_sales`, `Sale` |
+| Bridge | Prefix with `Bridge` | `Bridge Customer Region` | `CustomerRegion_Bridge` |
+| Measure table | Prefix `_` (hidden) | `_Measures`, `_KPIs` | `Measures Table` |
+| Config/Utility | Prefix `_` (hidden) | `_Parameters`, `_DateConfig` | `Parameters` |
 
 ### Columns
 
+**Rules:**
+1. **Descriptive and readable.** `Order Date`, not `OrdDt`. Spaces allowed.
+2. **Foreign keys hidden with special marker.** Use `CustomerKey` suffix or `_Customer` prefix to sort them together. **Always hide from report view.**
+3. **No abbreviations** except universal ones (`YTD`, `PY`, `MTD`, `QTD`, `YoY`). Avoid `Qty`, `Amt`, `Vta`, `Cant`.
+4. **Consistency.** If you use spaces in one table, use them everywhere.
+
 | Type | Convention | Example |
 |------|-----------|---------|
-| Key (primary) | `[TableName]Key` | `CustomerKey`, `ProductKey` |
-| Key (alternate) | `[TableName]ID` or `[TableName]Code` | `CustomerID`, `ProductCode` |
-| Attribute | PascalCase, descriptive | `FirstName`, `OrderDate`, `ProductCategory` |
-| Flag/Boolean | `Is[Condition]` | `IsActive`, `IsDeleted`, `HasDiscount` |
-| Amount/Currency | Suffix with `Amount` | `SalesAmount`, `DiscountAmount` |
-| Count | Suffix with `Count` | `OrderCount`, `ItemCount` |
-| Date | Suffix with `Date` | `OrderDate`, `ShipDate`, `HireDate` |
+| Primary key (surrogate) | `[Table]Key`, hidden | `CustomerKey`, `ProductKey` |
+| Primary key (business) | `[Entity] ID` or `[Entity] Code` | `Customer ID`, `Product Code` |
+| Attribute | Natural language | `First Name`, `Order Date`, `Product Category` |
+| Flag/Boolean | `Is [Condition]` or `Has [Condition]` | `Is Active`, `Has Discount` |
+| Amount/Currency | Include unit in name | `Sales Amount`, `Discount Amount` |
+| Count | Include `Count` suffix | `Order Count`, `Item Count` |
+| Date | Include `Date` suffix | `Order Date`, `Ship Date` |
 
 ### Measures
 
-| Type | Convention | Example |
-|------|-----------|---------|
-| Base aggregation | PascalCase, descriptive | `TotalSales`, `OrderCount` |
-| Time intelligence | Suffix with period | `TotalSales_YTD`, `Revenue_PY` |
-| Ratio/Percentage | Suffix with `Pct` or `Ratio` | `MarginPct`, `ConversionRatio` |
-| KPI | Prefix with `KPI_` | `KPI_Revenue_Actual`, `KPI_Revenue_Target` |
-| Ranking | Prefix with `Rank_` | `Rank_TopProducts` |
-| Debug/Test | Prefix with `_` | `_Debug_RowCount`, `_Test_Total` |
-| Format string | Include in measure | Use format strings, not calculated strings |
+**Rules:**
+1. **Auto-explicative names.** The name alone should tell you what it calculates. No documentation required.
+2. **No redundant prefixes.** Use `Sales`, not `Total Sales`, `Sum of Sales`, or `Amount of Sales`. The aggregation is implied.
+3. **Space-separated suffixes for time intelligence.** `Sales YTD`, `Sales PY`, `Sales YoY %`, `Sales MTD`.
+4. **Space-separated suffixes for ratios and percentages.** `Margin %`, `Growth %`, `Conversion Rate`.
+5. **Never prefix with the table name.** Just `Sales`, not `Transactions[Sales]` in the visible name.
+6. **Explicit measures, hidden source columns.** Create DAX measures for every numeric calculation. Hide sumable columns (or set summarization to `Don't summarize`) so users can't drag raw columns into visuals.
+7. **Organize in display folders** when the measure count grows: `Sales`, `Sales\Time Intelligence`, `Sales\Comparatives`.
+
+| Type | Convention | Example | Anti-Pattern |
+|------|-----------|---------|-------------|
+| Base aggregation | Noun, no prefix | `Sales`, `Customers`, `Units Sold` | `Total Sales`, `Sum of Sales`, `Sales Amount Total` |
+| Time intelligence | Noun + period suffix | `Sales YTD`, `Sales PY`, `Sales MTD` | `YTD_Sales`, `Sales_PriorYear` |
+| Variation | Noun + variation + `%` | `Sales YoY %`, `Sales MoM %` | `YoY_Pct_Sales` |
+| Ratio/Percentage | Noun + ` %` | `Margin %`, `Conversion %` | `MarginPct`, `ConversionRatio` |
+| KPI vs target | Noun + vs Target | `Sales vs Target`, `Sales vs Budget %` | `KPI_Sales` |
+| Ranking | `Rank: ` prefix or `Rank` suffix | `Rank: Top Products`, `Product Rank` | `RANK_Products` |
+| Debug/Test | `_` prefix (hidden) | `_Debug Row Count` | `Debug: Row Count` (visible) |
 
 ### Variables (DAX)
 
-| Convention | Example |
-|-----------|---------|
-| Prefix with `_` + PascalCase | `_CurrentSales`, `_PriorYear` |
-| Descriptive names | `_FilteredTable`, `_MaxDate` |
-| Avoid single letters | `_Result` not `_R` |
+**Rules:**
+1. **PascalCase.** No underscore prefix. `TotalSales`, `AverageMargin`, `FilteredTable`.
+2. **Final variable always named `Result`.** SQLBI convention for readability — the reader knows immediately where the measure ends.
+3. **Temporary columns prefixed with `@`.** When you add a column inside `ADDCOLUMNS` or `SUMMARIZECOLUMNS`, use `@Rank`, `@Sales`, `@Delta`. Distinguishes them from model columns.
+
+```dax
+// Good: PascalCase vars, Result final var, @ for temp columns
+Sales YoY % =
+VAR CurrentSales = [Sales]
+VAR PriorYearSales =
+    CALCULATE([Sales], SAMEPERIODLASTYEAR('Date'[Date]))
+VAR Delta = CurrentSales - PriorYearSales
+VAR Result = DIVIDE(Delta, PriorYearSales)
+RETURN Result
+
+// Temporary column example
+Top Products =
+VAR RankedProducts =
+    ADDCOLUMNS(
+        VALUES(Product[Product Name]),
+        "@Rank", RANKX(VALUES(Product[Product Name]), [Sales], , DESC)
+    )
+VAR Result =
+    FILTER(RankedProducts, [@Rank] <= 10)
+RETURN Result
+```
 
 ### Power Query
 
 | Element | Convention | Example |
 |---------|-----------|---------|
-| Query name | PascalCase matching table | `Customer`, `Sale` |
-| Staging query | Prefix with `stg_` | `stg_Customer_Raw` |
-| Helper function | Prefix with `fn` | `fnCleanText`, `fnGetFiscalYear` |
-| Parameter | Prefix with `prm` | `prmServerName`, `prmStartDate` |
+| Query name | Matches destination table | `Customer`, `Sales` |
+| Staging query | Prefix `stg `, hidden | `stg Customer Raw` |
+| Helper function | Prefix `fn` | `fnCleanText`, `fnGetFiscalYear` |
+| Parameter | Prefix `prm` | `prmServerName`, `prmStartDate` |
 | Step names | Descriptive, PascalCase | `FilteredActiveRows`, `RenamedColumns` |
 
 ---
@@ -89,26 +132,28 @@ You are a **BI Governance Specialist** who establishes and enforces naming conve
 
 ### Recommended Folder Structure
 
+Display folders separate measures with `\` (backslash). Use them as soon as you have more than ~10 measures.
+
 ```
 _Measures/
-├── 📁 Core Metrics
-│   ├── TotalSales
-│   ├── TotalCost
-│   └── GrossMargin
+├── 📁 Core
+│   ├── Sales
+│   ├── Cost
+│   └── Gross Margin
 ├── 📁 Time Intelligence
-│   ├── TotalSales_YTD
-│   ├── TotalSales_PY
-│   └── TotalSales_YoY
-├── 📁 KPIs
-│   ├── KPI_Revenue_Actual
-│   ├── KPI_Revenue_Target
-│   └── KPI_Revenue_Status
+│   ├── Sales YTD
+│   ├── Sales PY
+│   └── Sales YoY %
+├── 📁 Targets
+│   ├── Sales Target
+│   ├── Sales vs Target
+│   └── Sales vs Target %
 ├── 📁 Rankings
-│   ├── Rank_TopProducts
-│   └── Rank_TopCustomers
+│   ├── Rank: Top Products
+│   └── Rank: Top Customers
 └── 📁 _Debug (hidden in production)
-    ├── _Debug_RowCount
-    └── _Test_Total
+    ├── _Debug Row Count
+    └── _Test Sales
 ```
 
 ---
@@ -147,11 +192,13 @@ Every model should have:
 ### Measure Documentation Template
 
 ```dax
-// Description: Calculates total sales for the current year to date
+// Description: Calculates sales for the current year to date
 // Business rule: Includes all confirmed and shipped orders, excludes cancelled
 // Owner: [team/person]
 // Last modified: [date]
-TotalSales_YTD = TOTALYTD([TotalSales], 'Date'[Date])
+Sales YTD =
+VAR Result = TOTALYTD([Sales], 'Date'[Date])
+RETURN Result
 ```
 
 ---
@@ -173,11 +220,17 @@ TotalSales_YTD = TOTALYTD([TotalSales], 'Date'[Date])
 ### Code Review Checklist
 
 - [ ] Measures use VAR/RETURN for repeated calculations
+- [ ] Final variable in every measure is named `Result`
+- [ ] Variables use PascalCase (no underscore prefix)
+- [ ] Temporary columns use `@` prefix (e.g., `@Rank`)
 - [ ] DIVIDE() used instead of / operator
 - [ ] No FILTER on fact tables (use dimension filters)
-- [ ] Variables follow naming conventions
 - [ ] Complex measures have comments
 - [ ] No hardcoded values (use parameters)
+- [ ] No technical prefixes on tables (`Dim_`, `Fact_`)
+- [ ] Foreign keys hidden from report view
+- [ ] Sumable source columns hidden (only explicit measures visible)
+- [ ] Measure names are auto-explicative (no `Total`, `Sum of`)
 
 ---
 

package/skills/migration-assistant/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "migration-assistant"
 description: "Use when the user asks about Migration Assistant Skill, especially phrases like \"migrate\", \"move to Fabric\", \"Desktop to PBIP\", \"deprecated feature\", \"migrar\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/migration-assistant.md instead. -->

package/skills/model-documenter/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "model-documenter"
 description: "Use when the user asks about Model Documenter Skill, especially phrases like \"document model\", \"document measures\", \"generate documentation\", \"describe tables\", \"documentar modelo\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/model-documenter.md instead. -->

package/skills/pbi-connect/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "pbi-connect"
 description: "Use when the user asks about Power BI MCP Connection Skill, especially phrases like \"connect Power BI\", \"modeling mcp\", \"Power BI Desktop\", \"conectar Power BI\", \"can't connect to Power BI\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/pbi-connect.md instead. -->

package/skills/power-query/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "power-query"
 description: "Use when the user asks about Power Query Skill, especially phrases like \"Power Query\", \"query folding\", \"ETL\", \"source connection\", \"refresh\", \"parameters\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/power-query.md instead. -->

package/skills/project-kickoff/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "project-kickoff"
 description: "Project Kickoff Skill: Project analysis and planning."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/project-kickoff.md instead. -->

package/skills/query-performance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "query-performance"
 description: "Use when the user asks about Query Performance Skill, especially phrases like \"slow\", \"DAX Studio\", \"taking too long\", \"reduce refresh time\", \"rendimiento\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/query-performance.md instead. -->

package/skills/report-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "report-design"
 description: "Use when the user asks about Report Design Skill, especially phrases like \"report design\", \"chart type\", \"IBCS\", \"accessibility\", \"mobile layout\", \"diseño de reporte\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/report-design.md instead. -->

package/skills/report-layout/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "report-layout"
 description: "Use when the user asks about Report Layout Skill, especially phrases like \"report layout\", \"visual placement\", \"report wireframe\", \"navigation design\", \"diseño de reporte\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/report-layout.md instead. -->

package/skills/rls-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "rls-design"
 description: "Use when the user asks about RLS Design Skill, especially phrases like \"RLS\", \"user can only see their data\", \"restrict access\", \"security role\", \"seguridad a nivel de fila\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/rls-design.md instead. -->

package/skills/semantic-model/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "semantic-model"
 description: "Use when the user asks about Semantic Model Skill, especially phrases like \"semantic model\", \"TMDL\", \"DirectLake\", \"calculation group\", \"storage mode\", \"modelo semántico\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/semantic-model.md instead. -->

package/skills/testing-validation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "testing-validation"
 description: "Use when the user asks about Testing & Validation Skill, especially phrases like \"test\", \"unit test DAX\", \"regression test\", \"deployment checklist\", \"data reconciliation\", \"pruebas\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/testing-validation.md instead. -->

package/skills/theme-tweaker/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: "theme-tweaker"
 description: "Use when the user asks about Theme Tweaker Skill, especially phrases like \"modificar tema\", \"cambiar colores Power BI\", \"personalizar tema\", \"ajustar estilo\", \"theme tweaker\"."
-version: "1.0.0"
+version: "1.1.1"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/theme-tweaker.md instead. -->

package/src/content/mcp-requirements.json

@@ -42,6 +42,19 @@
         "POWERBI_MODELING_MCP_PATH",
         "PBI_MODELING_MCP_PATH"
       ]
+    },
+    {
+      "name": "microsoft-learn",
+      "displayName": "Microsoft Learn MCP",
+      "source": "http",
+      "url": "https://learn.microsoft.com/api/mcp",
+      "docs": "https://learn.microsoft.com/en-us/training/support/mcp",
+      "requiresAuth": false,
+      "platforms": ["win32", "darwin", "linux"],
+      "config": {
+        "type": "http",
+        "url": "https://learn.microsoft.com/api/mcp"
+      }
     }
   ],
   "toolConfigs": {