@luquimbo/bi-superpowers 5.0.0 → 5.0.2

package/bin/lib/mcp-config.js

@@ -31,6 +31,19 @@ const os = require('os');
 const MICROSOFT_LEARN_URL = 'https://learn.microsoft.com/api/mcp';
 const MODELING_SERVER_NAME = 'powerbi-modeling-mcp';
 const LEARN_SERVER_NAME = 'microsoft-learn';
+const CODEX_POWERBI_WRITE_TOOLS = [
+  'column_operations',
+  'database_operations',
+  'function_operations',
+  'measure_operations',
+  'object_translation_operations',
+  'partition_operations',
+  'perspective_operations',
+  'query_group_operations',
+  'relationship_operations',
+  'table_operations',
+  'user_hierarchy_operations',
+];
 
 /**
  * Resolves the absolute path to the Power BI Modeling MCP launcher
@@ -418,18 +431,25 @@ function writeCodexConfig(packageDir) {
   // Remove any previous bi-superpowers MCP sections so re-running install
   // doesn't duplicate them. Strips each section from its header to the
   // next [ header or EOF. Server names are escaped for regex safety even
-  // though current values are literal — defensive against future renames.
+  // though current values are literal. The optional suffix removes child
+  // sections like [mcp_servers.powerbi-modeling-mcp.tools.measure_operations].
   const namePattern = [MODELING_SERVER_NAME, LEARN_SERVER_NAME].map(escapeRegex).join('|');
   const stripPattern = new RegExp(
-    `\\n?\\[mcp_servers\\.(${namePattern})\\][\\s\\S]*?(?=\\n\\[|$)`,
+    `\\n?\\[mcp_servers\\.(${namePattern})(?:\\.[^\\]]+)?\\][\\s\\S]*?(?=\\n\\[|$)`,
     'g'
   );
   existing = existing.replace(stripPattern, '');
 
+  const writeToolApprovals = CODEX_POWERBI_WRITE_TOOLS.map(
+    (toolName) =>
+      `\n[mcp_servers.${MODELING_SERVER_NAME}.tools.${toolName}]\n` + 'approval_mode = "approve"\n'
+  ).join('');
+
   const newSections =
     `\n\n[mcp_servers.${MODELING_SERVER_NAME}]\n` +
     'command = "node"\n' +
     `args = ["${tomlEscape(launcher)}"]\n` +
+    writeToolApprovals +
     `\n[mcp_servers.${LEARN_SERVER_NAME}]\n` +
     `url = "${MICROSOFT_LEARN_URL}"\n`;
 

package/bin/lib/skills.js

@@ -38,7 +38,7 @@ function loadFlatSkill(filePath) {
       bundleDir: null,
     };
   } catch (err) {
-    console.warn(`⚠ No pude leer el skill ${filePath}: ${err.message}`);
+    console.warn(`⚠ Could not read skill ${filePath}: ${err.message}`);
     return null;
   }
 }
@@ -63,7 +63,7 @@ function loadFolderSkill(folderPath) {
       bundleDir: folderPath,
     };
   } catch (err) {
-    console.warn(`⚠ No pude leer el skill ${skillMd}: ${err.message}`);
+    console.warn(`⚠ Could not read skill ${skillMd}: ${err.message}`);
     return null;
   }
 }
@@ -89,7 +89,7 @@ function readSkillDirectory(directory) {
   try {
     entries = fs.readdirSync(directory, { withFileTypes: true });
   } catch (err) {
-    console.warn(`⚠ No pude leer el directorio de skills ${directory}: ${err.message}`);
+    console.warn(`⚠ Could not read skills directory ${directory}: ${err.message}`);
     return [];
   }
 
@@ -138,16 +138,16 @@ function loadSkills(options = {}) {
 /**
  * Normalize any user-facing skill identifier into its canonical name.
  *
- * Accepts `dax`, `dax.md`, `bi-report`, `bi-report/SKILL.md`,
- * or `bi-report\SKILL.md` (Windows separator) and returns the
+ * Accepts `dax`, `dax.md`, `folder-skill`, `folder-skill/SKILL.md`,
+ * or `folder-skill\SKILL.md` (Windows separator) and returns the
  * canonical skill name used as the key in readSkillDirectory's
- * output map (`dax`, `bi-report`).
+ * output map (`dax`, `folder-skill`).
  *
  * Uses a single alternation regex so the longer suffix `/SKILL.md`
  * is tried BEFORE the bare `.md`. Earlier callers chained two
  * `.replace()` calls and stripped `.md` first, which meant the
- * `/SKILL.md` alternative never matched — `bi-report/SKILL.md`
- * came out as `bi-report/SKILL` and the lookup failed.
+ * `/SKILL.md` alternative never matched — `folder-skill/SKILL.md`
+ * came out as `folder-skill/SKILL` and the lookup failed.
  *
  * @param {string} input - User-supplied skill identifier
  * @returns {string} Canonical skill name

package/bin/mcp/powerbi-modeling-launcher.js

@@ -18,10 +18,14 @@ if (!executablePath) {
   process.exit(1);
 }
 
-const child = spawn(executablePath, ['--start', ...process.argv.slice(2)], {
-  stdio: 'inherit',
-  env: process.env,
-});
+const child = spawn(
+  executablePath,
+  ['--readwrite', '--skip-confirmation', ...process.argv.slice(2)],
+  {
+    stdio: 'inherit',
+    env: process.env,
+  }
+);
 
 child.on('error', (error) => {
   console.error(`Failed to launch Power BI Modeling MCP: ${error.message}`);

package/bin/postinstall.js

@@ -2,7 +2,7 @@
 
 /**
  * Post-install script for BI Agent Superpowers
- * Shows helpful information after npm install
+ * Shows helpful information after npm install.
  * Developed by Lucas Sanchez (@luquimbo)
  */
 
@@ -12,32 +12,34 @@ console.log(`
 ╔═══════════════════════════════════════════════════════════╗
 ║                                                           ║
 ║   BI Agent Superpowers v${VERSION.padEnd(34)}║
-║   Plugin para Power BI Desktop — open source (MIT)        ║
+║   Power BI Desktop toolkit — open source (MIT)            ║
 ║   Developed by Lucas Sanchez (@luquimbo)                 ║
 ║                                                           ║
 ╚═══════════════════════════════════════════════════════════╝
 
-Instalado correctamente.
+Installed successfully.
 
 Quick Start:
-  super install              # Instalá skills + MCPs en tus agentes AI
+  super install              # Install skills + MCPs in your AI agents
 
-Funciona con los 5 agentes:
+Works with 5 agents:
   • Claude Code
   • GitHub Copilot
   • Codex (OpenAI)
   • Gemini CLI
   • Kilo Code
 
-4 skills iniciales:
-  /bi-start          — Arrancar una sesión (menú + update + conexión)
-  /bi-kickoff   — Analizá tu proyecto BI (proyecto nuevo)
-  /bi-connect       — Conectá tu agente a Power BI Desktop
-  /bi-report     — Generá reportes PBIR para Power BI Desktop (Windows)
+6 skills:
+  /bi-start          — Session opener and specialist routing
+  /bi-kickoff        — New BI project bootstrap
+  /bi-modeling       — Semantic model design and audit
+  /bi-dax            — DAX authoring, debugging, and optimization
+  /bi-performance    — Performance profiling, VertiPaq, and BPA
+  /bi-connect        — Power BI Desktop MCP connection and DAX UDFs
 
 2 MCP servers:
-  powerbi-modeling-mcp — Conexión local a Power BI Desktop (XMLA)
-  microsoft-learn    — Docs de Microsoft Learn en contexto
+  powerbi-modeling-mcp — Local Power BI Desktop connection (XMLA)
+  microsoft-learn      — Microsoft Learn docs in context
 
 Documentation: https://github.com/luquimbo/bi-superpowers
 `);

package/bin/utils/mcp-detect.js

@@ -179,33 +179,33 @@ function getMcpStatus() {
  */
 function getInstallInstructions() {
   return {
-    title: 'Power BI Modeling MCP no detectado',
+    title: 'Power BI Modeling MCP not detected',
     options: [
       {
         name: 'VS Code / Cursor',
         steps: [
-          'Abrir VS Code o Cursor',
-          'Ir a Extensions (Ctrl+Shift+X)',
-          'Buscar "Power BI Modeling MCP"',
-          'Instalar la extensión de Microsoft',
-          'Ejecutar: super install --all --yes',
+          'Open VS Code or Cursor',
+          'Go to Extensions (Ctrl+Shift+X)',
+          'Search for "Power BI Modeling MCP"',
+          'Install the Microsoft extension',
+          'Run: super install --all --yes',
         ],
         link: 'https://aka.ms/powerbi-modeling-mcp-vscode',
       },
       {
         name: 'Manual',
         steps: [
-          'Descargar VSIX desde VS Code Marketplace',
-          'Renombrar .vsix a .zip',
-          `Extraer a ${path.join(os.homedir(), '.bi-superpowers', 'mcp')}`,
-          'Configurar BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH con la ruta al .exe',
+          'Download the VSIX from VS Code Marketplace',
+          'Rename .vsix to .zip',
+          `Extract to ${path.join(os.homedir(), '.bi-superpowers', 'mcp')}`,
+          'Set BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH to the .exe path',
         ],
         link: 'https://marketplace.visualstudio.com/items?itemName=analysis-services.powerbi-modeling-mcp',
       },
     ],
     note:
       os.platform() !== 'win32'
-        ? 'El MCP local solo está disponible en Windows. En Mac/Linux tenés microsoft-learn para docs oficiales.'
+        ? 'The local MCP is only available on Windows. On macOS/Linux, microsoft-learn still provides official docs.'
         : null,
   };
 }

package/commands/bi-connect.md

@@ -1,5 +1,5 @@
 ---
-description: "Power BI Desktop connection and DAX UDF authoring"
+description: "Power BI Desktop MCP connection and DAX UDF authoring"
 ---
 
 <!-- Generated by BI Agent Superpowers. Edit src/content/skills/bi-connect.md instead. -->
@@ -15,7 +15,7 @@ node "{skillBundleDir}/scripts/update-check.js" --silent-if-uptodate --silent-if
 
 - Empty output or `UPTODATE` — proceed with the skill silently. No message.
 - `UPDATE_AVAILABLE <installed> <latest>` — tell the user exactly once this conversation, before diving into the skill:
-  > "Hay **bi-superpowers v{latest}** disponible (estás en v{installed}). Actualizá con `super upgrade` (o `/plugin update bi-superpowers` en Claude Code) cuando te venga bien. Si estás usando un plugin local generado con `super kickoff`, después corré `super recharge` en ese repo."
+  > "bi-superpowers v{latest} is available (you are on v{installed}). Update with `super upgrade` (or `/plugin update bi-superpowers` in Claude Code) when convenient. If you use a local plugin generated with `super kickoff`, run `super recharge` in that repo afterwards."
 
   Then continue with the skill below.
 - `SNOOZED <iso>` — proceed silently.
@@ -44,10 +44,26 @@ You are a **Power BI MCP Connection Specialist**. Your job is to help the user c
 ## MANDATORY RULES
 1. **USER-LEVEL FIRST.** Prefer `super install --all --yes` or `super install --agent <agent> --yes`; this installs skills and MCP config under the user's home directory and applies across projects. `.mcp.json` is only for an optional repo-local Claude Code plugin.
 2. **OFFICIAL SERVERS ONLY.** Use `powerbi-modeling-mcp` (local) and `microsoft-learn` (HTTP). Do not invent or recommend unofficial MCPs.
-3. **WINDOWS LIMITATION.** Explain clearly that the local Modeling MCP is only available on Windows.
+3. **WINDOWS + POWER BI DESKTOP ONLY.** Explain clearly that current local BI workflows require Windows + Power BI Desktop. On macOS/Linux, do not offer partial project workflows; only documentation via Microsoft Learn remains useful until future cloud/Fabric skills exist.
 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.
+7. **TEACH AS YOU CONNECT OR WRITE.** Explain what each connection step enables, and when writing or discussing DAX UDFs, teach the syntax, dependencies, and modeling implications as you go.
+
+8. **MCP MODEL EDITS ARE IN-MEMORY ONLY — SAVE BEFORE CLOSE.** Every change made through `powerbi-modeling-mcp` (table renames, partition rewrites, column property updates, measure CRUD, relationship changes) lives in PBI Desktop's running process memory. The on-disk TMDL is not updated until the user (or the agent) issues a save. **Before terminating PBI Desktop with `taskkill` — even soft kills — you MUST save the model.** Two acceptable save mechanisms:
+
+   - **Ask the user** to press `Ctrl+S` in PBI Desktop and confirm with "saved" / "listo".
+   - **Drive the save programmatically** with the bundled helper:
+     ```powershell
+     pwsh "{skillBundleDir}/scripts/save-powerbi-window.ps1" -WindowTitle "<projectName>" -WaitMs 3000
+     ```
+     The helper resolves the matching `PBIDesktop.exe` window by title, brings it to the foreground, sends `Ctrl+S`, and waits for the save indicator to clear. Returns 0 on success.
+
+   `taskkill /F /IM PBIDesktop.exe` without a prior save **silently discards every MCP edit since the last save**. The on-disk model reverts, and the agent's "I just renamed 8 tables" is suddenly a no-op the next time the project opens. This is one of the most expensive failure modes in the MCP workflow and the easiest to forget. Always save first.
+
+9. **PBIP FILES ARE READ-ONLY SNAPSHOTS.** Use PBIP/TMDL/PBIR files for inspection, diffs, and validation only. Do not hand-edit `.tmdl`, `.SemanticModel/**`, `.Report/**`, PBIR JSON, `visual.json`, `page.json`, themes, slicers, bookmarks, or any visual binding. Model changes go through the Power BI Modeling MCP. **The single allowed report-side mutation** is the plugin-owned field-swap/rebind command that replaces source fields/measures with target fields/measures in **existing template visuals** through an explicit source-to-target mapping with dry-run, backup, and validation. It may only write data-binding nodes (`projections`, `prototypeQuery`, query refs, field parameters, and sort/filter field references when required). It must preserve visual type, layout, formatting, interactions, IDs, theme, and bookmarks. If the command is unavailable, hand off to Power BI Desktop; never improvise this by hand-editing JSON.
+
+10. **TEMPLATE IS THE REFERENCE.** When writing DAX UDFs or discussing patterns, the BISuperpowers smoke-test template defines the canonical shape: `Métricas` as the measure and metric selector table, parameterizable currency conversion via `MonedaBase` + `Modelo Configuración` + `Tipo de cambio`, Sallieri period comparison, dynamic field parameters, calculation-group time intelligence, IBCS-aligned theme. UDFs the user writes should be either (a) generic enough to live alongside template patterns, or (b) explicitly extending those patterns. Reinventing template-equivalent logic in a project-specific UDF is a smell — flag it.
 
 ---
 
@@ -144,11 +160,12 @@ If they are intentionally maintaining a repo-local Claude Code plugin, they can
 Say:
 
 ```text
-The official local Power BI Modeling MCP is only available on Windows.
+The current BI Agent Superpowers local project workflows require Windows + Power BI Desktop.
 
-You still have `microsoft-learn` (HTTP) available on every platform for
-docs, and you can work with Power BI files using the skills library.
-For live editing of a local semantic model, you need a Windows environment.
+On macOS/Linux, do not run partial local Desktop workflows
+flows for local Power BI projects. You still have `microsoft-learn` (HTTP)
+available for docs. Future cloud/Fabric skills may work cross-platform when
+they do not depend on Desktop.
 ```
 
 ---
@@ -257,8 +274,8 @@ Do not:
 
 When writing a UDF:
 
-1. Confirm the model target: PBIP/TMDL file edit, DAX Query View, TMDL View, or
-   MCP-backed semantic model change.
+1. Confirm the model target: live Power BI Desktop through the Modeling MCP.
+   PBIP/TMDL file edits are not allowed; those files are export snapshots.
 2. Confirm that DAX UDF preview is enabled in Power BI Desktop when live Desktop
    authoring is required.
 3. Inspect existing functions first:
@@ -276,10 +293,10 @@ When writing a UDF:
    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.
+9. Apply the function through MCP or guide the user through Power BI Desktop
+   authoring if the current MCP surface cannot perform the write.
+10. After saving/exporting, re-query `INFO.USERDEFINEDFUNCTIONS()` or equivalent
+    model metadata to verify the function exists.
 
 ### UDF design checklist
 
@@ -319,8 +336,8 @@ EVALUATE
     { Company.Finance.GrossMarginPct ( 120, 300 ) }
 ```
 
-Use TMDL/PBIP shape only when you are saving the function into the model's
-`definition/functions.tmdl`:
+Use this TMDL shape only as a review reference for what Desktop/MCP should
+persist. Do not write it into `definition/functions.tmdl` by file patch:
 
 ```tmdl
 createOrReplace
@@ -362,7 +379,7 @@ reference and produce an original function.
 | Modeling MCP installed manually | Set `BI_SUPERPOWERS_POWERBI_MODELING_MCP_PATH` |
 | Agent not loading MCPs | Re-run `super install --agent <agent-id> --yes` and restart the agent |
 | Local Claude Code plugin not loading MCPs | Re-run `super mcp-setup` inside the plugin project and restart Claude Code |
-| macOS/Linux local modeling request | Use `microsoft-learn` for docs; live editing requires Windows |
+| macOS/Linux local project request | Explain that current local BI workflows require Windows + Power BI Desktop; use `microsoft-learn` only for docs |
 | User asks about Excel MCP | Explain Excel remains supported through skills and library content, not a default MCP |
 
 ---
@@ -384,7 +401,7 @@ reference and produce an original function.
 Adjust depth based on `config.json → experienceLevel`:
 - **beginner**: Step-by-step with explanations, reference library examples
 - **intermediate**: Standard depth, explain non-obvious decisions
-- **advanced**: Concise, skip basics, focus on edge cases and optimization
+- **advanced**: Concise, skip basics, but still teach edge cases, performance, and design criteria
 
 ---