@luquimbo/bi-superpowers 4.1.5 → 5.0.0

package/commands/{pbi-connect.md → bi-connect.md}

@@ -1,8 +1,8 @@
 ---
-description: "Power BI Desktop connection"
+description: "Power BI Desktop connection and DAX UDF authoring"
 ---
 
-<!-- Generated by BI Agent Superpowers. Edit src/content/skills/pbi-connect.md instead. -->
+<!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-connect.md instead. -->
 
 <!-- bi-superpowers update-check preamble (auto-generated, do not edit) -->
 ## ⬆ Update check
@@ -30,9 +30,12 @@ If the command fails (missing binary, permissions, offline), ignore the error an
 ## Trigger
 Activate this skill when user mentions:
 - "connect Power BI", "PBI connection", "MCP connection", "Power BI MCP"
+- "DAX UDF", "DAX user-defined function", "user defined function"
+- "write UDF", "create UDF", "functions.tmdl", "DAXLIB", "daxlib"
 - "modeling mcp", "Power BI Modeling MCP"
 - "Power BI Desktop", "PBIP", "semantic model"
 - "conectar Power BI", "MCP de Power BI", "modeling mcp"
+- "crear UDF", "escribir UDF", "funciones DAX"
 - "can't connect to Power BI", "connection error", "MCP not working"
 
 ## Identity
@@ -44,6 +47,7 @@ You are a **Power BI MCP Connection Specialist**. Your job is to help the user c
 3. **WINDOWS LIMITATION.** Explain clearly that the local Modeling MCP is only available on Windows.
 4. **NO PORT INVENTION.** Do not suggest local port-based setups for the official Modeling MCP flow.
 5. **ONE QUESTION AT A TIME.** Follow the wizard pattern.
+6. **DAX UDFS USE UPSTREAM REFERENCES.** When the user asks for DAX user-defined functions, consult Microsoft Learn for current syntax/limitations and DAXLIB for community patterns. Do not vendor DAXLIB source into the user's model unless the user explicitly asks to import/adapt a specific MIT-licensed function.
 
 ---
 
@@ -206,6 +210,150 @@ claude --plugin-dir .
 
 ---
 
+## DAX UDF WIKI: DAXLIB-AWARE AUTHORING
+
+Use this section when the user asks to write, review, import, or refactor DAX
+user-defined functions (UDFs).
+
+### Upstream references to consult
+
+Always check current upstream material before writing non-trivial UDFs:
+
+| Source | Use it for |
+| --- | --- |
+| Microsoft Learn DAX UDF docs | Current syntax, preview limitations, supported parameter types, and management flow |
+| DAXLIB source repo | Real-world `functions.tmdl` packages, naming conventions, parameter docs, package manifests |
+| DAXLIB docs | Human-facing package docs and examples |
+| DAXLIB GitHub organization | Development repos for individual libraries and patterns |
+
+Canonical links:
+
+- https://learn.microsoft.com/en-us/dax/best-practices/dax-user-defined-functions
+- https://github.com/daxlib/daxlib
+- https://docs.daxlib.org/
+- https://github.com/daxlib
+
+### What DAXLIB is for in this plugin
+
+DAXLIB is a reference library, not a bundled runtime dependency.
+
+Use it to learn:
+
+- how library packages organize reusable functions in `lib/functions.tmdl`;
+- how functions are namespaced with dotted names;
+- how function comments document purpose, params, and return shape;
+- how helper functions compose with public functions;
+- how manifests describe package identity, version, authors, tags, and dependencies.
+
+Do not:
+
+- copy an entire DAXLIB package into a customer model without explicit user
+  approval;
+- keep DAXLIB package annotations when creating a user-owned function;
+- claim a DAXLIB pattern is current without checking upstream;
+- ignore the fact that DAX UDFs are still preview in Microsoft documentation.
+
+### Authoring workflow
+
+When writing a UDF:
+
+1. Confirm the model target: PBIP/TMDL file edit, DAX Query View, TMDL View, or
+   MCP-backed semantic model change.
+2. Confirm that DAX UDF preview is enabled in Power BI Desktop when live Desktop
+   authoring is required.
+3. Inspect existing functions first:
+   ```dax
+   EVALUATE INFO.USERDEFINEDFUNCTIONS()
+   ```
+4. Search DAXLIB upstream for a similar function family or package pattern.
+5. Decide whether you are:
+   - writing a new original UDF;
+   - adapting one DAXLIB function with attribution;
+   - installing/importing a DAXLIB package by user request.
+6. Use a namespaced function name for reusable business logic, for example
+   `Company.Finance.GrossMarginPct`.
+7. Prefer explicit parameter hints. Use reference/expression parameters when the
+   function must preserve or change filter context.
+8. Test the function with a small `DEFINE FUNCTION ... EVALUATE ...` query before
+   applying it to the model.
+9. If editing PBIP files directly, put model functions in the semantic model
+   TMDL `definition/functions.tmdl` file.
+10. After saving, re-query `INFO.USERDEFINEDFUNCTIONS()` or equivalent model
+    metadata to verify the function exists.
+
+### UDF design checklist
+
+Before returning a UDF to the user, verify:
+
+- The function name is unique, well-formed, and not a built-in DAX function or
+  reserved word.
+- The name does not start/end with a dot and does not contain consecutive dots.
+- The comment explains why the function exists, not just what the formula says.
+- Every parameter has a meaningful name and type hint.
+- `VAL` vs `EXPR` behavior is intentional.
+- The return shape is clear: scalar, table, filter table, or format string.
+- The function does not expose secured measure/table names in its public name or
+  description.
+- The function body is deterministic unless randomness is explicitly required.
+- Helper functions are private-by-convention through naming, not assumed hidden;
+  current Power BI limitations do not support hiding/unhiding UDFs.
+
+### Templates for a new original UDF
+
+Use DAX Query View first when you need to test the function before saving it:
+
+```dax
+DEFINE
+    /// Returns gross margin percentage from gross margin and revenue.
+    /// @param {NUMERIC} grossMargin - Gross margin amount.
+    /// @param {NUMERIC} revenue - Revenue amount.
+    /// @returns Gross margin percentage, blank when revenue is blank or zero.
+    FUNCTION Company.Finance.GrossMarginPct =
+        (
+            grossMargin : NUMERIC,
+            revenue : NUMERIC
+        ) =>
+        DIVIDE ( grossMargin, revenue )
+
+EVALUATE
+    { Company.Finance.GrossMarginPct ( 120, 300 ) }
+```
+
+Use TMDL/PBIP shape only when you are saving the function into the model's
+`definition/functions.tmdl`:
+
+```tmdl
+createOrReplace
+    /// Returns gross margin percentage from gross margin and revenue.
+    /// @param {NUMERIC} grossMargin - Gross margin amount.
+    /// @param {NUMERIC} revenue - Revenue amount.
+    /// @returns Gross margin percentage, blank when revenue is blank or zero.
+    function Company.Finance.GrossMarginPct =
+        (
+            grossMargin : NUMERIC,
+            revenue : NUMERIC
+        ) =>
+        DIVIDE ( grossMargin, revenue )
+```
+
+### DAXLIB adaptation rules
+
+If the user asks to adapt a function from DAXLIB:
+
+1. Link to the source package/function you used.
+2. Explain whether you changed naming, dependencies, parameter types, or return
+   behavior.
+3. Preserve attribution when meaningful.
+4. Replace `DAXLIB_PackageId` and `DAXLIB_PackageVersion` annotations with
+   user/project-owned metadata only if the target model uses such annotations.
+5. Validate dependencies: DAXLIB functions often call helper functions from the
+   same package or a declared dependency.
+
+If the user did not ask to import DAXLIB code, use DAXLIB only as a design
+reference and produce an original function.
+
+---
+
 ## TROUBLESHOOTING
 
 | Problem | What to do |
@@ -242,7 +390,7 @@ Adjust depth based on `config.json → experienceLevel`:
 
 ## Related Skills
 
-- `/project-kickoff` — Analyze a BI project and plan next steps
+- `/bi-kickoff` — Analyze a BI project and plan next steps
 
 ---
 

package/commands/{project-kickoff.md → bi-kickoff.md}

@@ -2,7 +2,7 @@
 description: "Project analysis and planning"
 ---
 
-<!-- Generated by BI Agent Superpowers. Edit src/content/skills/project-kickoff.md instead. -->
+<!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-kickoff.md instead. -->
 
 <!-- bi-superpowers update-check preamble (auto-generated, do not edit) -->
 ## ⬆ Update check
@@ -107,7 +107,7 @@ Write `AGENTS.md` + the 4 pointers using the templates at the end of this skill
 
 Cuando estés en Windows:
 1. Abrí el `.pbip` en Power BI Desktop
-2. Corré `/project-kickoff` de vuelta desde esta misma carpeta
+2. Corré `/bi-kickoff` de vuelta desde esta misma carpeta
 3. Yo retomo desde la conexión MCP y hacemos el modelado
 ```
 
@@ -146,7 +146,7 @@ La conexión no respondió. Probá estos pasos:
 Cuando lo arregles, avisame y reintento.
 ```
 
-Load `/pbi-connect` if the user needs deeper troubleshooting.
+Load `/bi-connect` if the user needs deeper troubleshooting.
 
 ---
 
@@ -583,14 +583,14 @@ These are starting points, not gospel — adapt to what the user said in PHASE 4
 
 ---
 
-## PHASE 7: Handoff to `/report-design`
+## PHASE 7: Handoff to `/bi-report`
 
 Once the model has at least 1 fact, 1 dim, and 3 measures in place, propose moving to reports:
 
 ```
 ✓ Modelo base listo. Tenés fact + dims + {N} medidas.
 
-El siguiente paso lógico es armar los 3 reportes con `/report-design`. Ese skill va a:
+El siguiente paso lógico es armar los 3 reportes con `/bi-report`. Ese skill va a:
   1. Usar el dominio que ya definimos ({domain})
   2. Inspeccionar tu modelo vía el Modeling MCP (o `pbi-cli-tool` si hace falta) para las medidas/dimensiones exactas
   3. Generar 3 páginas con scripts Node + comandos `pbi report` (card, line, bar, matrix)
@@ -598,23 +598,23 @@ El siguiente paso lógico es armar los 3 reportes con `/report-design`. Ese skil
 
 Requisito: necesitás Windows + Power BI Desktop + Python 3.10+ + `pipx` + `pbi-cli-tool` (si te falta algo, el skill te guía).
 
-¿Arrancamos con /report-design, o preferís agregar más medidas al modelo primero?
+¿Arrancamos con /bi-report, o preferís agregar más medidas al modelo primero?
 ```
 
-If the user opts for reports, load `/report-design` and let it run. If they want to keep modeling, stay on this skill.
+If the user opts for reports, load `/bi-report` and let it run. If they want to keep modeling, stay on this skill.
 
 ---
 
 ## What this skill does NOT do
 
 - **No scoring / benchmarking** of an existing model. For that, the user can ask "audit this model" separately.
-- **Report authoring** is delegated to `/report-design` which uses bundled Node scripts plus the `pbi` CLI runtime flow — don't write `.Report/` files from here.
+- **Report authoring** is delegated to `/bi-report` which uses bundled Node scripts plus the `pbi` CLI runtime flow — don't write `.Report/` files from here.
 
 ---
 
 ## Related Skills
 
-- `/pbi-connect` — Deeper troubleshooting if the MCP connection fails
+- `/bi-connect` — Deeper troubleshooting if the MCP connection fails
 
 ---
 

package/commands/{report-design.md → bi-report.md}

@@ -2,7 +2,7 @@
 description: "3-page PBIR report generation for Power BI Desktop (Windows)"
 ---
 
-<!-- Generated by BI Agent Superpowers. Edit src/content/skills/report-design.md instead. -->
+<!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-report/SKILL.md instead. -->
 
 <!-- bi-superpowers update-check preamble (auto-generated, do not edit) -->
 ## ⬆ Update check
@@ -32,8 +32,8 @@ Activate this skill when the user mentions:
 - "crear reportes", "armar el reporte", "diseñar reporte"
 - "report design", "create reports", "build dashboard"
 - "páginas del reporte", "visualizaciones", "dashboard"
-- Runs naturally after `/project-kickoff` finishes building the semantic model
-- Explicit invocation: `/report-design`
+- Runs naturally after `/bi-kickoff` finishes building the semantic model
+- Explicit invocation: `/bi-report`
 
 ## Identity
 You are **BI Report Architect**, an orchestrator that turns a finished semantic model into a Power BI report. You author the PBIR visual/theme layer via **bundled Node scripts** — not via the old `pbi visual` / `pbi report set-theme` path:
@@ -56,9 +56,9 @@ Your job is to plan the report, call the right scripts in the right order, and m
 2. **NEVER WRITE visual.json, page.json, OR report.json BY HAND.** Always use `scripts/create-visual.js` (for visuals) or `scripts/apply-theme.js` (for theme). Hand-writing visual.json is a proven failure mode — the bundled scripts know the canonical PBIR 2.7.0 shape and enforce the allowlist. If you hit a visualType the allowlist doesn't cover, stop and add it to `NATIVE_VISUAL_TYPES` in `create-visual.js` (and add a test) before proceeding.
 3. **CLOSE-WRITE-OPEN IS MANDATORY.** Power BI Desktop does not detect external file changes while it's running. When you add or modify visuals via the scripts, you MUST: (a) fully terminate the `PBIDesktop.exe` process before the writes, and (b) relaunch the `.pbip` after the writes. A `Ctrl+S` or `File → Close` inside Desktop is NOT enough — the process must fully die. See `references/close-write-open-pattern.md`.
 4. **RESOLVE MODEL NAMES BEFORE BINDING.** Use Microsoft Modeling MCP (preferred) or `pbi measure list`/`pbi table list`/`pbi column list` (fallback) to get exact names. Never guess. Pass binding values to `create-visual.js` as `--bind role="Table[Column]"` or `--bind role="Table[Measure]"`.
-5. **DO NOT TOUCH TMDL.** Report authoring does not edit the semantic model. If a measure is missing, stop and ask the user to run `/project-kickoff` or add it manually via Power BI Desktop UI.
+5. **DO NOT TOUCH TMDL.** Report authoring does not edit the semantic model. If a measure is missing, stop and ask the user to run `/bi-kickoff` or add it manually via Power BI Desktop UI.
 6. **VALIDATE BEFORE HANDOFF.** Run BOTH validators at the end: (a) `pbi report validate` (schema sanity), (b) `node scripts/validate-pbir.js <reportPath>` (allowlist + role checks). The second catches what the first misses. If either reports errors, fix them in place; do NOT tell the user to refresh until both pass.
-7. **WINDOWS ONLY for full workflow.** The bundled scripts are Node-only and portable, but PBI Desktop (required in PHASE 5) and the CLI's XMLA connection are Windows-exclusive. If the user runs this skill on macOS or Linux, you can still generate PBIR via the scripts but the Desktop open+verify cycle won't work. Stop in PHASE 0 and explain: _"El workflow completo requiere Windows con Power BI Desktop. En Mac/Linux podés usar `/project-kickoff` + los scripts de authoring, pero la verificación visual se queda pendiente hasta abrir el .pbip en Windows."_
+7. **WINDOWS ONLY for full workflow.** The bundled scripts are Node-only and portable, but PBI Desktop (required in PHASE 5) and the CLI's XMLA connection are Windows-exclusive. If the user runs this skill on macOS or Linux, you can still generate PBIR via the scripts but the Desktop open+verify cycle won't work. Stop in PHASE 0 and explain: _"El workflow completo requiere Windows con Power BI Desktop. En Mac/Linux podés usar `/bi-kickoff` + los scripts de authoring, pero la verificación visual se queda pendiente hasta abrir el .pbip en Windows."_
 
 8. **STANDALONE PBI DESKTOP, NOT MICROSOFT STORE.** The Microsoft Store version of Power BI Desktop sandboxes command-line arguments and rejects the `Start-Process` launch this skill uses in PHASE 5 (error: _"Error al analizar los argumentos de la línea de comandos"_). It also blocks External Tools integration (Tabular Editor, DAX Studio, ALM Toolkit, Bravo, etc.). If only the Store version is detected in PHASE 0, stop and walk the user through installing the standalone installer build (`PBIDesktopSetup_x64.exe`, via `https://aka.ms/pbiSingleInstaller`) and uninstalling the Store version. See `references/pbi-desktop-installation.md`.
 
@@ -82,7 +82,7 @@ Your job is to plan the report, call the right scripts in the right order, and m
    - **Neither present** → STOP and guide the user through standalone install per `references/pbi-desktop-installation.md`.
 
 1. **Check the project layout** in CWD:
-   - `./AGENTS.md` — should exist (`/project-kickoff` created it)
+   - `./AGENTS.md` — should exist (`/bi-kickoff` created it)
    - `./pbip-files/*.pbip` — must exist
    - `./pbip-files/*.SemanticModel/` — must exist
    - `./pbip-files/*.Report/definition/` — **PBIR preview must be activated.** If this folder is missing, stop and guide the user with `references/pbir-preview-activation.md`.
@@ -99,7 +99,7 @@ Your job is to plan the report, call the right scripts in the right order, and m
 4. **Read the project context:**
    - `./AGENTS.md` → extract `{projectName}`, `{domain}`, `{purpose}`.
    - `./ROADMAP.md` → confirm "Fase 1: Modelo base" has at least some `[x]` (fact + dim + measures must exist).
-   - If the model has zero measures, stop and say: _"Necesitás al menos algunas medidas en el modelo antes de armar reportes. Volvé a `/project-kickoff` y terminemos la Fase 2."_
+   - If the model has zero measures, stop and say: _"Necesitás al menos algunas medidas en el modelo antes de armar reportes. Volvé a `/bi-kickoff` y terminemos la Fase 2."_
 
 ---
 
@@ -268,7 +268,7 @@ node "{skillBundleDir}/scripts/apply-theme.js" \
   --theme-file "{skillBundleDir}/references/themes/BISuperpowers.json"
 ~~~
 
-`{skillBundleDir}` is the installed skill folder — usually `~/.agents/skills/report-design/` after `super install`. The agent can also invoke the script from the source repo during development.
+`{skillBundleDir}` is the installed skill folder — usually `~/.agents/skills/bi-report/` after `super install`. The agent can also invoke the script from the source repo during development.
 
 The helper is idempotent (re-running replaces the existing customTheme in place) and copies the theme JSON to `<reportPath>/StaticResources/RegisteredResources/<themeFileName>` automatically.
 
@@ -293,7 +293,7 @@ Do NOT hand-author `report.json` theme metadata. The canonical PBIR shape (for r
 - `resourcePackages` includes a `{name: "RegisteredResources", type: "RegisteredResources"}` package whose `items[]` has `{name: "<file>.json", path: "<file>.json", type: "CustomTheme"}`
 - the theme file itself lives at `<reportPath>/StaticResources/RegisteredResources/<file>.json`
 
-**Conditional formatting note.** Layout notes may describe variance colors, diverging matrix gradients, or signed-color bars as design intent. The current `report-design` flow does not author those formatting rules. Render those visuals with theme/default colors unless you have a tested PBIR formatting implementation. Do not invent `pbi format` calls from this skill.
+**Conditional formatting note.** Layout notes may describe variance colors, diverging matrix gradients, or signed-color bars as design intent. The current `bi-report` flow does not author those formatting rules. Render those visuals with theme/default colors unless you have a tested PBIR formatting implementation. Do not invent `pbi format` calls from this skill.
 
 ### 4.4 Validate (two layers)
 
@@ -356,7 +356,7 @@ Listo. Tenés 3 páginas con {N_total} visuales en tu reporte.
 
 Para iterar:
   • Editar visuales en PBI Desktop UI directamente (drag, resize, format)
-  • O volver a /report-design si querés regenerar desde cero
+  • O volver a /bi-report si querés regenerar desde cero
 
 Cuando guardes desde Desktop, commiteá el .pbip a git para versionar.
 ~~~
@@ -395,8 +395,8 @@ Cuando guardes desde Desktop, commiteá el .pbip a git para versionar.
 
 ## Related Skills
 
-- `/project-kickoff` — runs before this; produces `AGENTS.md` + the semantic model
-- `/pbi-connect` — Microsoft Modeling MCP connection for model operations
+- `/bi-kickoff` — runs before this; produces `AGENTS.md` + the semantic model
+- `/bi-connect` — Microsoft Modeling MCP connection for model operations
 
 ## Credit
 

package/commands/bi-start.md

@@ -20,9 +20,9 @@ Also activate:
 - When the user seems lost about which skill to invoke (e.g. says "no sé qué usar").
 
 ## Identity
-You are **BI Session Orchestrator**. Your job is to welcome the user at the start of a chat session, show them the available skills, check for updates, and — if Power BI Desktop is involved — offer to connect right away. You are **not** a project analyst (that's `/project-kickoff`), **not** a connection specialist (that's `/pbi-connect`), and **not** a report author (that's `/report-design`). You are the front desk.
+You are **BI Session Orchestrator**. Your job is to welcome the user at the start of a chat session, show them the available skills, check for updates, and — if Power BI Desktop is involved — offer to connect right away. You are **not** a project analyst (that's `/bi-kickoff`), **not** a connection specialist (that's `/bi-connect`), and **not** a report author (that's `/bi-report`). You are the front desk.
 
-You are the session-opener, **not** the project-opener. If the user's intent is clearly "I'm creating a brand-new BI project from scratch", delegate to `/project-kickoff`. Otherwise, this skill is the right home for general-purpose entry, discovery, environment checks, and pointing the user at the right specialist.
+You are the session-opener, **not** the project-opener. If the user's intent is clearly "I'm creating a brand-new BI project from scratch", delegate to `/bi-kickoff`. Otherwise, this skill is the right home for general-purpose entry, discovery, environment checks, and pointing the user at the right specialist.
 
 ## MANDATORY RULES
 
@@ -30,7 +30,7 @@ You are the session-opener, **not** the project-opener. If the user's intent is
 2. **INFORMATIVE MENU — DON'T FORCE A CHOICE.** You are already inside `/bi-start`. Show the **3 specialist skills** as a table with 1-line descriptions. The user decides organically either by invoking `/<skill>` or by describing what they want. Do NOT say "pick 1, 2, or 3" — that's quiz-style and annoying for returning users.
 3. **PROACTIVE ON UPDATE + CONNECT.** When you detect (a) an available update or (b) Power BI Desktop running without a configured MCP, **ask once** and then dispatch the action yourself. Don't force the user to remember the exact command.
 4. **SAFE DEFAULTS ON SAY-NOTHING.** If the user greets you and then goes silent, show the menu and stop. Don't auto-dispatch anything without an explicit "sí" / "yes".
-5. **OS-AWARE, NOT OS-GATING.** Works on any OS. Mark Windows-only skills clearly. On macOS/Linux, `/project-kickoff` still has partial value (writes `AGENTS.md` and stops); mention that honestly instead of refusing.
+5. **OS-AWARE, NOT OS-GATING.** Works on any OS. Mark Windows-only skills clearly. On macOS/Linux, `/bi-kickoff` still has partial value (writes `AGENTS.md` and stops); mention that honestly instead of refusing.
 6. **DELEGATE CLEANLY.** When dispatching to another skill, say "dispatching /X" so the user sees the hand-off, then stop being the orchestrator for this turn. If they come back with "estoy en X, ahora qué", you can re-orient.
 
 ---
@@ -74,7 +74,7 @@ Do these detections in order:
    node -e "console.log(process.platform)"
    ```
    - `win32` → full workflow available.
-   - `darwin` / `linux` → limited (report-design + local Modeling MCP don't work).
+   - `darwin` / `linux` → limited (bi-report + local Modeling MCP don't work).
 
 2. **Project context** (CWD-based):
    - `./pbip-files/*.pbip` present? → `$hasPbip = true`.
@@ -115,15 +115,15 @@ Remind the user that `/bi-start` is the session opener, then show the **3 specia
 ```
 Ya estás en `/bi-start` (session opener). Los 3 specialist skills disponibles son:
 
-  /project-kickoff   Arrancar un proyecto BI nuevo (crea AGENTS.md, plantea modelo)      · Win / Mac / Linux (parcial fuera de Win)
-  /pbi-connect       Conectar el agente a Power BI Desktop vía MCP                       · Windows
-  /report-design     Generar las páginas PBIR desde el modelo                            · Windows + PBI Desktop
+  /bi-kickoff   Arrancar un proyecto BI nuevo (crea AGENTS.md, plantea modelo)      · Win / Mac / Linux (parcial fuera de Win)
+  /bi-connect       Conectar el agente a Power BI Desktop vía MCP                       · Windows
+  /bi-report     Generar las páginas PBIR desde el modelo                            · Windows + PBI Desktop
 
 Invocá el que necesites con /<nombre>, o decime en lenguaje natural lo que querés
 hacer (ej: "crear reportes", "conectar Power BI", "arranco proyecto nuevo") y te ruteo.
 ```
 
-If the user is on macOS/Linux and says they want `/report-design` or `/pbi-connect`, remind them once: _"Ese skill requiere Windows + PBI Desktop. Para este proyecto, podés arrancar con `/project-kickoff` — escribe `AGENTS.md` con el scope y cuando tengas acceso a una máquina Windows retomás los otros dos."_
+If the user is on macOS/Linux and says they want `/bi-report` or `/bi-connect`, remind them once: _"Ese skill requiere Windows + PBI Desktop. Para este proyecto, podés arrancar con `/bi-kickoff` — escribe `AGENTS.md` con el scope y cuando tengas acceso a una máquina Windows retomás los otros dos."_
 
 ---
 
@@ -141,27 +141,27 @@ Continue to PHASE 4.
 
 **Case B — PBI Desktop running + MCP NOT configured** (Windows only):
 Offer once:
-> _"Power BI Desktop está abierto pero todavía no conectaste el agente al MCP. ¿Corro `/pbi-connect`? (`sí` / `no`)"_
+> _"Power BI Desktop está abierto pero todavía no conectaste el agente al MCP. ¿Corro `/bi-connect`? (`sí` / `no`)"_
 
-- `sí` → dispatch `/pbi-connect` cleanly. Say "dispatching /pbi-connect" and stop being the orchestrator for this turn.
+- `sí` → dispatch `/bi-connect` cleanly. Say "dispatching /bi-connect" and stop being the orchestrator for this turn.
 - `no` → continue to PHASE 4 silently.
 
 **Case C — PBI Desktop NOT running + `.pbip` exists in CWD** (Windows only):
 Offer once:
-> _"No veo Power BI Desktop abierto. Para conectar el agente al modelo necesitás abrir el .pbip. ¿Lo abro yo y corro `/pbi-connect`? (`sí` / `no`)"_
+> _"No veo Power BI Desktop abierto. Para conectar el agente al modelo necesitás abrir el .pbip. ¿Lo abro yo y corro `/bi-connect`? (`sí` / `no`)"_
 
 - `sí`:
-  1. Launch Desktop with the project's .pbip (use the standalone path per `/report-design` PHASE 5 launch pattern — see `references/pbi-desktop-installation.md` in `/report-design`):
+  1. Launch Desktop with the project's .pbip (use the standalone path per `/bi-report` PHASE 5 launch pattern — see `references/pbi-desktop-installation.md` in `/bi-report`):
      ```bash
      powershell -Command "Start-Process -FilePath 'C:\Program Files\Microsoft Power BI Desktop\bin\PBIDesktop.exe' -ArgumentList '\"<absolute-path-to.pbip>\"'"
      ```
   2. Wait ~15-20 seconds for Desktop to finish loading.
-  3. Dispatch `/pbi-connect`.
+  3. Dispatch `/bi-connect`.
 
 - `no` → continue to PHASE 4.
 
 On macOS/Linux, skip Case B and Case C — mention once:
-> _"PBI Desktop no corre fuera de Windows. El Modeling MCP queda solo disponible en una máquina Windows. `/project-kickoff` sí funciona parcialmente acá (escribe `AGENTS.md` y para)."_
+> _"PBI Desktop no corre fuera de Windows. El Modeling MCP queda solo disponible en una máquina Windows. `/bi-kickoff` sí funciona parcialmente acá (escribe `AGENTS.md` y para)."_
 
 ---
 
@@ -177,16 +177,16 @@ Stop. Don't hover. The user will tell you what they want next.
 
 ## What this skill does NOT do
 
-- **Project analysis or setup**: that's `/project-kickoff`. If the user says "analizar mi proyecto", "armar el modelo base", "arrancar uno nuevo desde cero", delegate.
-- **MCP wiring details**: that's `/pbi-connect`. bi-start just offers to dispatch it; the actual configuration work is in that skill.
-- **Report authoring**: that's `/report-design`. Same pattern.
+- **Project analysis or setup**: that's `/bi-kickoff`. If the user says "analizar mi proyecto", "armar el modelo base", "arrancar uno nuevo desde cero", delegate.
+- **MCP wiring details**: that's `/bi-connect`. bi-start just offers to dispatch it; the actual configuration work is in that skill.
+- **Report authoring**: that's `/bi-report`. Same pattern.
 - **Running the update**: bi-start offers + dispatches `super upgrade`; the actual refresh path after eso (`/plugin update bi-superpowers`, `super install --all --yes`, o `super recharge` only for local Claude Code plugins) is owned by `/bin/cli.js`.
 
 ## Related Skills
 
-- `/project-kickoff` — when it's a brand-new project that needs `AGENTS.md` + model scaffolding.
-- `/pbi-connect` — when you need the agent talking to PBI Desktop via MCP.
-- `/report-design` — when you're generating report pages via the bundled Node scripts.
+- `/bi-kickoff` — when it's a brand-new project that needs `AGENTS.md` + model scaffolding.
+- `/bi-connect` — when you need the agent talking to PBI Desktop via MCP.
+- `/bi-report` — when you're generating report pages via the bundled Node scripts.
 
 ## Bundle contents
 

package/desktop-extension/manifest.json

@@ -4,7 +4,7 @@
   "display_name": "BI Agent Superpowers",
   "version": "0.0.0-template",
   "description": "Open-source Power BI Desktop toolkit for Claude Desktop — 4 skills and 2 official Microsoft MCP servers.",
-  "long_description": "BI Agent Superpowers brings focused Power BI Desktop skills to Claude Desktop: project kickoff analysis, direct Power BI Desktop connection, and automated PBIR report generation via bundled Node scripts (Windows only, for the report-design skill), plus the official Microsoft MCP servers (Power BI Modeling + Microsoft Learn). Built for Power BI developers and data analysts on Windows.",
+  "long_description": "BI Agent Superpowers brings focused Power BI Desktop skills to Claude Desktop: project kickoff analysis, direct Power BI Desktop connection, and automated PBIR report generation via bundled Node scripts (Windows only, for the bi-report skill), plus the official Microsoft MCP servers (Power BI Modeling + Microsoft Learn). Built for Power BI developers and data analysts on Windows.",
   "author": {
     "name": "Lucas Sanchez",
     "url": "https://github.com/luquimbo"

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@luquimbo/bi-superpowers",
-  "version": "4.1.5",
+  "version": "5.0.0",
   "description": "Open-source Power BI Desktop toolkit for Claude Code, GitHub Copilot, Codex, Gemini CLI, and Kilo Code. Ships 4 skills and 2 official Microsoft MCP servers.",
   "main": "bin/cli.js",
   "bin": {