@bradtech/sales-skills 1.0.0

package/.env.dist

@@ -0,0 +1,18 @@
+# Rename this file to '.env' at the root of the repository
+
+# Odoo ERP Configuration
+ODOO_URL="https://your-instance.odoo.com"
+ODOO_DB="your_database_name"
+ODOO_USER="your_email@company.com"
+ODOO_PASSWORD="your_password_or_api_key"
+
+# Brevo API Configuration - Retrieve your v3 API key from your Brevo account
+BREVO_API_KEY="your_brevo_v3_api_key"
+
+# Path to the Google Service Account key file (optional if placed at root as 'service_account.json')
+GOOGLE_APPLICATION_CREDENTIALS="path/to/your/service_account.json"
+
+# Local LM Studio Configuration (optional)
+LM_STUDIO_URL="http://localhost:1234/v1"
+LM_STUDIO_MODEL="qwen2.5-coder-7b-instruct"
+

package/AGENT.md

@@ -0,0 +1,58 @@
+# LLM Agent Instructions: Sales Skills Guidelines
+
+This repository follows the core guidelines and styling conventions of the crapougnax ecosystem.
+
+---
+
+## 🧭 Base Guidelines & Personal Rules
+
+For base development principles, coding standards, and project rules, all agent actions must comply with the rules defined in:
+👉 **[Gist: Personal Gemini Rules & Instructions](https://gist.github.com/crapougnax/47971b85aa73dd702f4372a89858111c)**
+
+---
+
+## 🛠 How to Add a New Vendor Skill
+
+Vendor skills represent atomic wrappers around third-party APIs. To add a new vendor integration:
+
+1. **Create the Vendor Directory**:
+   - Location: `skills/vendor/<vendor_name>/`
+2. **Implement Client and CLI Runner**:
+   - Create scripts inside the vendor directory (e.g., `client.ts` for logic, `cli.ts` for Commander-based runner).
+   - Use standard `@quatrain` core libraries for logging, HTTP clients, and prompt helpers:
+     - `@quatrain/log` for output reporting.
+     - `@quatrain/cli` for interactive prompts.
+     - `@quatrain/api-client` (REST) or `@quatrain/api-xmlrpc` (XML-RPC).
+3. **Prevent Subcommand Collision**:
+   - Ensure the command parsing in the main CLI entrypoint (`cli.ts`) is conditionally executed:
+     ```typescript
+     if (import.meta.main) {
+       main().catch(...)
+     }
+     ```
+4. **Create the Skill Definition**:
+   - Add `skills/vendor/<vendor_name>/SKILL.md` containing YAML frontmatter (`name` and `description`) and detailed instruction triggers.
+5. **Activate the Skill**:
+   - Link the directory into the agent customization workspace folder:
+     ```bash
+     ln -s ../../skills/vendor/<vendor_name> .agents/skills/<vendor_name>
+     ```
+
+---
+
+## 🚀 How to Add a New Composite Action
+
+Composite actions orchestrate workflows across multiple vendors. To add a new composite action:
+
+1. **Create the Action Directory**:
+   - Location: `skills/actions/<action_name>/`
+2. **Implement the Action Orchestrator**:
+   - Create scripts inside a `scripts/` subdirectory, e.g., `skills/actions/<action_name>/scripts/<action_name>_cli.ts`.
+   - Import vendor client instances from `../../../vendor/` relative paths.
+3. **Create the Skill Definition**:
+   - Add `skills/actions/<action_name>/SKILL.md` containing YAML frontmatter (`name` and `description`) and instructions defining the workflow steps.
+4. **Activate the Action**:
+   - Link the directory into the agent customization workspace folder:
+     ```bash
+     ln -s ../../skills/actions/<action_name> .agents/skills/<action_name>
+     ```

package/HOWTO.md

@@ -0,0 +1,72 @@
+# How-To Guide: Running Sales Skills Commands
+
+This document contains standard recipes and commands for testing, verifying, and running the sales-skills suite. Make sure you have run `bun install` and loaded your `.env` before executing these commands.
+
+---
+
+## 1. Odoo ERP Integration
+
+### Search Partners
+Search Odoo contacts by query string (checks names and emails):
+```bash
+bun run skills/vendor/odoo/cli.ts search-partners --query "infotel" --limit 5 --output ".log/partners.json"
+```
+
+### Create Contact
+Create a new partner inside Odoo:
+```bash
+bun run skills/vendor/odoo/cli.ts create-contact --name "John Doe" --email "john.doe@example.com" --output ".log/new_contact.json"
+```
+
+### Create Meeting
+Schedule a calendar meeting inside Odoo (attendees list expects Odoo partner IDs):
+```bash
+bun run skills/vendor/odoo/cli.ts create-meeting --name "Introduction Call" --start "2026-06-25 14:00:00" --duration 1.5 --attendees 365940,365941 --output ".log/new_meeting.json"
+```
+
+---
+
+## 2. Brevo Email Marketing
+
+### List Contacts
+Retrieve contacts from your Brevo mailing list:
+```bash
+bun run skills/vendor/brevo/cli.ts list-contacts --limit 10 --output ".log/brevo_list.json"
+```
+
+---
+
+## 3. Google Calendar
+
+### List Events
+List upcoming calendar events for a specific user:
+```bash
+bun run skills/vendor/google/cli.ts list-events --calendar-id "olivier@brad.ag" --limit 5 --output ".log/google_events.json"
+```
+
+### Create Event
+Schedule an event in Google Calendar:
+```bash
+bun run skills/vendor/google/cli.ts create-event --summary "Sync with Partner" --start "2026-06-25 15:30:00" --duration 1.0 --description "Introductory talk" --calendar-id "olivier@brad.ag" --output ".log/event_created.json"
+```
+
+### Delete Event
+Delete an event by its unique Google Calendar ID:
+```bash
+bun run skills/vendor/google/cli.ts delete-event --event-id "_example_id" --calendar-id "olivier@brad.ag" --output ".log/event_deleted.json"
+```
+
+---
+
+## 4. Google Calendar to Odoo CRM Sync (Composite Action)
+
+Sync Google Calendar events for a specific date to OdooCRM, prompting for missing contact creation:
+```bash
+bun run skills/actions/sync-meetings-to-odoo/scripts/sync_meetings_cli.ts --calendar-id "olivier@brad.ag" --date "2026-06-25" --output ".log/sync_run.json"
+```
+During execution, the CLI will:
+1. Load calendar events.
+2. Present list of proposals.
+3. Wait for `(Y/n)` keyboard confirmations to create contacts, update contacts, and insert meetings.
+4. Execute confirmed operations.
+5. Log a final summary of all successful creations to `.log/sync_run.json`.

package/LICENSE

@@ -0,0 +1,8 @@
+# LICENSE
+
+This project is licensed under the **GNU Affero General Public License v3.0 (AGPL v3)**.
+
+Copyright © 2026 Brad Technology SAS. All Rights Reserved.
+
+For full license details, please refer to the official GNU AGPL v3 text at:
+https://www.gnu.org/licenses/agpl-3.0.txt

package/LLM.md

@@ -0,0 +1,37 @@
+# LLM Agent Skill Activation
+
+Activate and update all integration skills for your local or global LLM agents with a single command:
+
+```bash
+bun run setup-skills
+```
+
+---
+
+## What the Script Sets Up
+
+### 1. Gemini Coding Assistant (Customization Roots)
+- Links all workspace integrations under `skills/` to the local customization directory `.agents/skills/`.
+- Registers rule definitions (`AGENT.md`) to `.agents/AGENTS.md`.
+- Automatically links skills globally to `~/.gemini/config/skills/` if the global config directory exists.
+
+### 2. Claude-based Assistants (Cline, Roo Code, etc.)
+- Exposes workspace guidelines by linking `AGENT.md` directly to `.clinerules` and `.roomodes` at the root.
+- The assistant automatically parses these files at startup to understand available commands.
+
+### 3. Local Models via LM Studio (Agent Runner)
+You can run this skill set with local models (e.g. Qwen-2.5-Coder, Llama-3) hosted via LM Studio:
+1. Turn on the local server in LM Studio (defaults to `http://localhost:1234/v1`).
+2. Run the agent using `local-agent`:
+   ```bash
+   bun run local-agent "Search Odoo for partners at infotel"
+   ```
+- Environment variables `LM_STUDIO_URL` and `LM_STUDIO_MODEL` can be defined in your `.env` to override the defaults.
+
+### 4. Other Assistants (OpenAI / Custom GPTs)
+- Register the TS CLI runner commands under your Custom Actions / Functions.
+- Example execute command:
+  ```bash
+  bun run skills/actions/sync-meetings-to-odoo/scripts/sync_meetings_cli.ts --calendar-id <email> --date <date> --output <output_path>
+  ```
+

package/README.md

@@ -0,0 +1,100 @@
+# Brad Sales Skills
+
+A suite of TypeScript/Bun integration tools designed to connect Odoo ERP, Brevo, and Google Calendar into a cohesive automated sales assistant. 
+
+This repository leverages the `@quatrain` ecosystem for unified logging, API clients (both REST and XML-RPC), and interactive prompt helper utilities.
+
+---
+
+## Features
+
+### 1. Atomic Vendor Clients (`skills/vendor/`)
+- **Odoo CRM (`odoo-integration`)**: Search partners, update contacts, create new contacts, and manage calendar events in Odoo using a fast XML-RPC connector (`@quatrain/api-xmlrpc`).
+- **Brevo Email Marketing (`brevo-integration`)**: Query, insert, and update newsletter and CRM contacts via the Brevo REST API client.
+- **Google Calendar (`google-calendar`)**: Access Google Calendars using service account credentials. Supports listing, creating, and deleting events.
+
+### 2. Composite Sync Actions (`skills/actions/`)
+- **Google Calendar to Odoo Meetings Sync (`sync-meetings-to-odoo`)**: An interactive command-line orchestrator that:
+  1. Pulls events from Google Calendar for a target date.
+  2. Resolves attendees' emails against Odoo partners.
+  3. Prompts the user interactively (using inquirer-based helpers) to create missing contacts, update incomplete names, and create Odoo calendar meetings linked to those partners.
+
+---
+
+## Directory Structure
+
+```
+├── .env.dist                   # Template for environment configuration
+├── package.json                # Project dependencies (linked local @quatrain workspaces)
+├── tsconfig.json               # Path mappings for direct Bun execution
+├── service_account.json        # (Optional) Google Service Account key file
+├── skills/                     # Skill Definitions & Implementations
+│   ├── actions/                # Composite orchestrators
+│   │   └── sync-meetings-to-odoo/
+│   │       ├── SKILL.md        # LLM integration triggers for composite sync
+│   │       └── scripts/
+│   │           └── sync_meetings_cli.ts
+│   └── vendor/                 # CLI entry points and definitions for atomic vendors
+│       ├── google/
+│       │   ├── SKILL.md        # LLM integration triggers for Google Calendar
+│       │   ├── calendar.ts     # Google calendar client
+│       │   └── cli.ts          # CLI runner
+│       ├── odoo/
+│       │   ├── SKILL.md        # LLM integration triggers for Odoo
+│       │   └── cli.ts          # Odoo client & CLI runner
+│       └── brevo/
+│           ├── SKILL.md        # LLM integration triggers for Brevo
+│           └── cli.ts          # Brevo client & CLI runner
+
+```
+
+---
+
+## Configuration
+
+Duplicate `.env.dist` as `.env` and fill in the credentials:
+
+```ini
+# Odoo ERP Configuration
+ODOO_URL="https://your-instance.odoo.com"
+ODOO_DB="your_database_name"
+ODOO_USER="your_email@company.com"
+ODOO_PASSWORD="your_password_or_api_key"
+
+# Brevo API Configuration
+BREVO_API_KEY="your_brevo_v3_api_key"
+
+# Path to the Google Service Account key file (optional if placed at root as 'service_account.json')
+GOOGLE_APPLICATION_CREDENTIALS="service_account.json"
+```
+
+### Google Service Account
+Download your Google Cloud Service Account key file and:
+1. Place it at the root of the repository as `service_account.json`, OR
+2. Place it anywhere and set its absolute path in the `GOOGLE_APPLICATION_CREDENTIALS` environment variable inside `.env`.
+
+---
+
+## LLM Activation
+
+This repository is structured as a **Gemini/Custom Agent Skill Set**. To activate these skills and allow your LLM coding assistant to automatically discover, read, and run these commands, configure customization roots:
+
+### 1. Workspace-Specific Activation (Recommended)
+Create a directory named `.agents` at the root of your workspace, and create/link the skill definitions:
+```bash
+mkdir -p .agents/skills
+ln -s ../../skills/vendor/google .agents/skills/google-calendar
+ln -s ../../skills/vendor/odoo .agents/skills/odoo-integration
+ln -s ../../skills/vendor/brevo .agents/skills/brevo-integration
+ln -s ../../skills/actions/sync-meetings-to-odoo .agents/skills/sync-meetings-to-odoo
+```
+
+### 2. Global Activation
+Alternatively, copy or link these directories into your global configuration directory (usually located at `~/.gemini/config/skills/`):
+```bash
+cp -r skills/vendor/* ~/.gemini/config/skills/
+cp -r skills/actions/* ~/.gemini/config/skills/
+```
+
+Once linked/copied, the LLM agent will detect the frontmatter name and description in each `SKILL.md` (e.g. `google-calendar`, `odoo-integration`), matching user requests to the respective CLI tools and executing actions autonomously.
+

package/bin/activate_skills.sh

@@ -0,0 +1,54 @@
+#!/usr/bin/env bash
+
+# Exit immediately if a command exits with a non-zero status
+set -e
+
+WORKSPACE_ROOT="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
+cd "$WORKSPACE_ROOT"
+
+echo "=== Sales Skills LLM Activation & Update Script ==="
+
+# 1. Local Workspace-Specific Customizations (.agents)
+echo "Setting up local Gemini agent workspace customizations..."
+mkdir -p .agents/skills
+
+# Helper to link if target doesn't exist, or update/force symlink
+link_skill() {
+  local src="$1"
+  local dest=".agents/skills/$2"
+  echo "Linking skill '$2' -> '$src'..."
+  ln -sfh "../../$src" "$dest"
+}
+
+link_skill "skills/vendor/google" "google-calendar"
+link_skill "skills/vendor/odoo" "odoo-integration"
+link_skill "skills/vendor/brevo" "brevo-integration"
+link_skill "skills/actions/sync-meetings-to-odoo" "sync-meetings-to-odoo"
+
+# Link AGENT.md as workspace customizations rule AGENTS.md
+echo "Linking AGENT.md -> .agents/AGENTS.md..."
+ln -sf "../AGENT.md" .agents/AGENTS.md
+
+# 2. Cline & Roo Code Rule Files
+echo "Setting up rules for Cline and Roo Code assistants..."
+ln -sf "AGENT.md" .clinerules
+ln -sf "AGENT.md" .roomodes
+
+# 3. Global Gemini Assistant Skills (Optional)
+GLOBAL_GEMINI_SKILLS_DIR="$HOME/.gemini/config/skills"
+if [ -d "$HOME/.gemini/config" ]; then
+  echo "Global Gemini config found. Setting up global skills..."
+  mkdir -p "$GLOBAL_GEMINI_SKILLS_DIR"
+  
+  # Link/update skills globally
+  ln -sfh "$WORKSPACE_ROOT/skills/vendor/google" "$GLOBAL_GEMINI_SKILLS_DIR/google-calendar"
+  ln -sfh "$WORKSPACE_ROOT/skills/vendor/odoo" "$GLOBAL_GEMINI_SKILLS_DIR/odoo-integration"
+  ln -sfh "$WORKSPACE_ROOT/skills/vendor/brevo" "$GLOBAL_GEMINI_SKILLS_DIR/brevo-integration"
+  ln -sfh "$WORKSPACE_ROOT/skills/actions/sync-meetings-to-odoo" "$GLOBAL_GEMINI_SKILLS_DIR/sync-meetings-to-odoo"
+  
+  echo "Global skills successfully symlinked to $GLOBAL_GEMINI_SKILLS_DIR"
+else
+  echo "Global Gemini config path not found. Skipping global registration."
+fi
+
+echo "Success! Skills are linked, activated, and updated."

package/bin/lm_studio_agent.ts

@@ -0,0 +1,172 @@
+import { $ } from "bun";
+import { existsSync, readFileSync } from "node:fs";
+import { join } from "node:path";
+
+const LM_STUDIO_URL = process.env.LM_STUDIO_URL || "http://localhost:1234/v1";
+const MODEL_NAME = process.env.LM_STUDIO_MODEL || "qwen2.5-coder-7b-instruct"; // Default fallback model name
+
+console.log(`=== LM Studio Local Agent Runner ===`);
+console.log(`Connecting to LM Studio at: ${LM_STUDIO_URL}`);
+console.log(`Using model: ${MODEL_NAME}`);
+
+// Define tools according to OpenAI / LM Studio specification
+const TOOLS = [
+  {
+    type: "function",
+    function: {
+      name: "search_odoo_partners",
+      description: "Search for contacts or companies in Odoo ERP matching a query string.",
+      parameters: {
+        type: "object",
+        properties: {
+          query: { type: "string", description: "Search query (email, name, or domain)" },
+          limit: { type: "integer", description: "Maximum number of partners to return", default: 5 }
+        },
+        required: ["query"]
+      }
+    }
+  },
+  {
+    type: "function",
+    function: {
+      name: "list_google_events",
+      description: "List upcoming calendar events from Google Calendar.",
+      parameters: {
+        type: "object",
+        properties: {
+          calendarId: { type: "string", description: "Email address of the calendar owner", default: "primary" },
+          limit: { type: "integer", description: "Maximum number of events to fetch", default: 10 }
+        },
+        required: ["calendarId"]
+      }
+    }
+  },
+  {
+    type: "function",
+    function: {
+      name: "sync_meetings_to_odoo",
+      description: "Sync meetings from Google Calendar to Odoo CRM interactively, confirming contacts and meetings creation.",
+      parameters: {
+        type: "object",
+        properties: {
+          calendarId: { type: "string", description: "Google Calendar owner email (defaults to Odoo login)" },
+          date: { type: "string", description: "Target date to sync in YYYY-MM-DD format (defaults to today)" }
+        },
+        required: ["calendarId"]
+      }
+    }
+  }
+];
+
+// Helper to execute local CLI scripts and return the JSON output
+async function executeTool(name: string, args: any): Promise<any> {
+  const logDir = join(process.cwd(), ".log");
+  await $`mkdir -p ${logDir}`;
+  const outputPath = join(logDir, `lm_studio_${name}_result.json`);
+
+  console.log(`\n[Executing Tool: ${name} with arguments:`, args, "]");
+
+  try {
+    if (name === "search_odoo_partners") {
+      const limit = args.limit || 5;
+      await $`bun run skills/vendor/odoo/cli.ts search-partners --query ${args.query} --limit ${limit} --output ${outputPath}`;
+    } else if (name === "list_google_events") {
+      const limit = args.limit || 10;
+      await $`bun run skills/vendor/google/cli.ts list-events --calendar-id ${args.calendarId} --limit ${limit} --output ${outputPath}`;
+    } else if (name === "sync_meetings_to_odoo") {
+      const dateOption = args.date ? ["--date", args.date] : [];
+      // Note: This script is interactive and uses stdin. We spawn it inheriting parent terminal I/O.
+      await $`bun run skills/actions/sync-meetings-to-odoo/scripts/sync_meetings_cli.ts --calendar-id ${args.calendarId} ${dateOption} --output ${outputPath}`.inherit();
+    } else {
+      throw new Error(`Unknown tool name: ${name}`);
+    }
+
+    if (existsSync(outputPath)) {
+      const content = readFileSync(outputPath, "utf8");
+      return JSON.parse(content);
+    }
+    return { status: "success", info: "Command ran successfully, but no output JSON was produced." };
+  } catch (err: any) {
+    console.error(`Tool execution failed: ${err.message}`);
+    return { error: err.message };
+  }
+}
+
+// Simple agent loop
+async function runAgent(prompt: string) {
+  const messages: any[] = [
+    {
+      role: "system",
+      content: "You are a helpful sales assistant with access to Odoo CRM, Google Calendar, and Brevo tools. Run actions whenever requested."
+    },
+    { role: "user", content: prompt }
+  ];
+
+  let loop = true;
+  while (loop) {
+    try {
+      const response = await fetch(`${LM_STUDIO_URL}/chat/completions`, {
+        method: "POST",
+        headers: { "Content-Type": "application/json" },
+        body: JSON.stringify({
+          model: MODEL_NAME,
+          messages,
+          tools: TOOLS,
+          tool_choice: "auto"
+        })
+      });
+
+      if (!response.ok) {
+        throw new Error(`HTTP error ${response.status}: ${await response.text()}`);
+      }
+
+      const result = await response.json();
+      const choice = result.choices?.[0];
+      const message = choice?.message;
+
+      if (!message) {
+        console.log("No response message received.");
+        break;
+      }
+
+      // Add assistant response to history
+      messages.push(message);
+
+      if (message.tool_calls && message.tool_calls.length > 0) {
+        for (const toolCall of message.tool_calls) {
+          const functionName = toolCall.function.name;
+          const functionArgs = JSON.parse(toolCall.function.arguments);
+
+          const resultPayload = await executeTool(functionName, functionArgs);
+
+          // Add tool result to history
+          messages.push({
+            role: "tool",
+            tool_call_id: toolCall.id,
+            name: functionName,
+            content: JSON.stringify(resultPayload)
+          });
+        }
+      } else {
+        // Model returned final text answer
+        console.log(`\n[Assistant Response]:\n${message.content}`);
+        loop = false;
+      }
+    } catch (err: any) {
+      console.error(`Agent loop error: ${err.message}`);
+      break;
+    }
+  }
+}
+
+// Run using prompt argument or exit
+const userPrompt = process.argv.slice(2).join(" ");
+if (!userPrompt) {
+  console.log("Usage: bun run bin/lm_studio_agent.ts <your prompt here>");
+  console.log("Example: bun run bin/lm_studio_agent.ts 'Search Odoo for contacts at infotel'");
+  process.exit(1);
+}
+
+runAgent(userPrompt).catch((err) => {
+  console.error("Agent execution failed:", err);
+});

package/bin/publish-prepare.cjs

@@ -0,0 +1,69 @@
+const fs = require('node:fs');
+const path = require('node:path');
+const { execSync } = require('node:child_process');
+
+const pkgPath = './package.json';
+const pkg = JSON.parse(fs.readFileSync(pkgPath, 'utf8'));
+
+console.log('[PREPARE] Resolving workspace dependencies for CI install...');
+
+// Remove workspaces since they don't exist in CI
+delete pkg.workspaces;
+
+let changed = false;
+for (const depType of ['dependencies', 'devDependencies', 'peerDependencies']) {
+  if (pkg[depType]) {
+    for (const [name, val] of Object.entries(pkg[depType])) {
+      if (typeof val === 'string' && (val === 'workspace:*' || val.startsWith('workspace:'))) {
+        try {
+          // Query the version from the registry
+          console.log(`[PREPARE] Querying registry version for ${name}...`);
+          const latestVersion = execSync(`npm view ${name} version`, { encoding: 'utf8' }).trim();
+          pkg[depType][name] = `^${latestVersion}`;
+          console.log(`[PREPARE] Resolved ${name} dependency to ^${latestVersion}`);
+          changed = true;
+        } catch (err) {
+          console.warn(`[WARNING] Failed to resolve version for ${name} from registry: ${err.message}`);
+          
+          // Try local workspace fallback if present
+          let resolvedLocal = false;
+          const corePkgsDir = path.resolve(process.cwd(), '../../QUATRAIN/Core/packages');
+          if (fs.existsSync(corePkgsDir)) {
+            try {
+              const dirs = fs.readdirSync(corePkgsDir);
+              for (const dir of dirs) {
+                const localPkgJsonPath = path.join(corePkgsDir, dir, 'package.json');
+                if (fs.existsSync(localPkgJsonPath)) {
+                  const localPkgJson = JSON.parse(fs.readFileSync(localPkgJsonPath, 'utf8'));
+                  if (localPkgJson.name === name) {
+                    pkg[depType][name] = `^${localPkgJson.version}`;
+                    console.log(`[PREPARE] Resolved ${name} from local workspace to ^${localPkgJson.version}`);
+                    changed = true;
+                    resolvedLocal = true;
+                    break;
+                  }
+                }
+              }
+            } catch (e) {
+              // ignore
+            }
+          }
+          
+          if (!resolvedLocal) {
+            // Fallback to '*' if it is not published yet and local workspace not found
+            pkg[depType][name] = '*';
+            console.log(`[PREPARE] Fallback resolved ${name} dependency to *`);
+            changed = true;
+          }
+        }
+      }
+    }
+  }
+}
+
+if (changed || pkg.hasOwnProperty('workspaces')) {
+  fs.writeFileSync(pkgPath, JSON.stringify(pkg, null, 2) + '\n', 'utf8');
+  console.log('[PREPARE] package.json updated successfully.');
+} else {
+  console.log('[PREPARE] No changes made to package.json.');
+}