funifier-mcp 0.1.0 → 0.2.3

package/dist/mcp/index.js

@@ -8,6 +8,24 @@ const tools_1 = require("./tools");
 const documentation_1 = require("./resources/documentation");
 const templates_1 = require("./prompts/templates");
 async function main() {
+    const subcommand = process.argv[2];
+    if (subcommand === "init") {
+        const { default: runInit } = require("../cli/init");
+        await runInit();
+        return;
+    }
+    if (subcommand === "--version" || subcommand === "-v") {
+        // eslint-disable-next-line @typescript-eslint/no-var-requires
+        const pkg = require("../../package.json");
+        console.log(pkg.version);
+        return;
+    }
+    if (subcommand === "--help" || subcommand === "-h") {
+        console.log("Usage: funifier-mcp            Start the MCP server (stdio)");
+        console.log("       funifier-mcp init       Interactive setup for AI platforms");
+        console.log("       funifier-mcp --version  Print version");
+        return;
+    }
     // Create the API holder (manages connection state)
     const apiHolder = new api_holder_1.ApiHolder();
     // Try to auto-connect from funifier.json or env vars (non-blocking)
@@ -25,7 +43,6 @@ async function main() {
     const transport = new stdio_js_1.StdioServerTransport();
     await server.connect(transport);
     if (!autoConnected) {
-        // Server started without config — tools will ask user to connect via funifier_connect
         console.error("Funifier MCP server started without auto-config. Use funifier_connect tool to connect.");
     }
 }

package/dist/mcp/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/mcp/index.ts"],"names":[],"mappings":";;;AAEA,oEAAoE;AACpE,wEAAiF;AACjF,6CAAyC;AACzC,mCAAwC;AACxC,6DAA8D;AAC9D,mDAAsD;AAEtD,KAAK,UAAU,IAAI;IACjB,mDAAmD;IACnD,MAAM,SAAS,GAAG,IAAI,sBAAS,EAAE,CAAC;IAElC,oEAAoE;IACpE,MAAM,aAAa,GAAG,SAAS,CAAC,cAAc,EAAE,CAAC;IAEjD,wBAAwB;IACxB,MAAM,MAAM,GAAG,IAAI,kBAAS,CAAC;QAC3B,IAAI,EAAE,qBAAqB;QAC3B,OAAO,EAAE,OAAO;KACjB,CAAC,CAAC;IAEH,6CAA6C;IAC7C,IAAA,qBAAa,EAAC,MAAM,EAAE,SAAS,CAAC,CAAC;IACjC,IAAA,iCAAiB,EAAC,MAAM,CAAC,CAAC;IAC1B,IAAA,2BAAe,EAAC,MAAM,CAAC,CAAC;IAExB,6BAA6B;IAC7B,MAAM,SAAS,GAAG,IAAI,+BAAoB,EAAE,CAAC;IAC7C,MAAM,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAEhC,IAAI,CAAC,aAAa,EAAE,CAAC;QACnB,sFAAsF;QACtF,OAAO,CAAC,KAAK,CACX,wFAAwF,CACzF,CAAC;IACJ,CAAC;AACH,CAAC;AAED,IAAI,EAAE,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;IACrB,OAAO,CAAC,KAAK,CAAC,2CAA2C,EAAE,KAAK,CAAC,CAAC;IAClE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/mcp/index.ts"],"names":[],"mappings":";;;AAEA,oEAAoE;AACpE,wEAAiF;AACjF,6CAAyC;AACzC,mCAAwC;AACxC,6DAA8D;AAC9D,mDAAsD;AAEtD,KAAK,UAAU,IAAI;IACjB,MAAM,UAAU,GAAG,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;IACnC,IAAI,UAAU,KAAK,MAAM,EAAE,CAAC;QAC1B,MAAM,EAAE,OAAO,EAAE,OAAO,EAAE,GAAG,OAAO,CAAC,aAAa,CAAC,CAAC;QACpD,MAAM,OAAO,EAAE,CAAC;QAChB,OAAO;IACT,CAAC;IACD,IAAI,UAAU,KAAK,WAAW,IAAI,UAAU,KAAK,IAAI,EAAE,CAAC;QACtD,8DAA8D;QAC9D,MAAM,GAAG,GAAG,OAAO,CAAC,oBAAoB,CAAC,CAAC;QAC1C,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,OAAO,CAAC,CAAC;QACzB,OAAO;IACT,CAAC;IACD,IAAI,UAAU,KAAK,QAAQ,IAAI,UAAU,KAAK,IAAI,EAAE,CAAC;QACnD,OAAO,CAAC,GAAG,CAAC,6DAA6D,CAAC,CAAC;QAC3E,OAAO,CAAC,GAAG,CAAC,mEAAmE,CAAC,CAAC;QACjF,OAAO,CAAC,GAAG,CAAC,8CAA8C,CAAC,CAAC;QAC5D,OAAO;IACT,CAAC;IAED,mDAAmD;IACnD,MAAM,SAAS,GAAG,IAAI,sBAAS,EAAE,CAAC;IAElC,oEAAoE;IACpE,MAAM,aAAa,GAAG,SAAS,CAAC,cAAc,EAAE,CAAC;IAEjD,wBAAwB;IACxB,MAAM,MAAM,GAAG,IAAI,kBAAS,CAAC;QAC3B,IAAI,EAAE,qBAAqB;QAC3B,OAAO,EAAE,OAAO;KACjB,CAAC,CAAC;IAEH,6CAA6C;IAC7C,IAAA,qBAAa,EAAC,MAAM,EAAE,SAAS,CAAC,CAAC;IACjC,IAAA,iCAAiB,EAAC,MAAM,CAAC,CAAC;IAC1B,IAAA,2BAAe,EAAC,MAAM,CAAC,CAAC;IAExB,6BAA6B;IAC7B,MAAM,SAAS,GAAG,IAAI,+BAAoB,EAAE,CAAC;IAC7C,MAAM,MAAM,CAAC,OAAO,CAAC,SAAS,CAAC,CAAC;IAEhC,IAAI,CAAC,aAAa,EAAE,CAAC;QACnB,OAAO,CAAC,KAAK,CACX,wFAAwF,CACzF,CAAC;IACJ,CAAC;AACH,CAAC;AAED,IAAI,EAAE,CAAC,KAAK,CAAC,CAAC,KAAK,EAAE,EAAE;IACrB,OAAO,CAAC,KAAK,CAAC,2CAA2C,EAAE,KAAK,CAAC,CAAC;IAClE,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}

package/package.json

@@ -1,65 +1,70 @@
-{
-  "name": "funifier-mcp",
-  "version": "0.1.0",
-  "description": "Funifier AI toolkit — MCP server, API client, and Claude Code skills for the Funifier gamification platform",
-  "main": "dist/index.js",
-  "types": "dist/index.d.ts",
-  "bin": {
-    "funifier-mcp": "dist/mcp/index.js"
-  },
-  "files": [
-    "dist",
-    "skills",
-    "doc",
-    "README.md",
-    "LICENSE"
-  ],
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/funifierinc/funifier-mcp.git"
-  },
-  "bugs": {
-    "url": "https://github.com/funifierinc/funifier-mcp/issues"
-  },
-  "homepage": "https://github.com/funifierinc/funifier-mcp#readme",
-  "author": "Funifier",
-  "publishConfig": {
-    "access": "public"
-  },
-  "scripts": {
-    "build": "tsc",
-    "bundle": "npm run build && esbuild dist/mcp/index.js --bundle --outfile=dist/mcp/bundle.js --format=cjs --platform=node --minify",
-    "dev": "tsc --watch",
-    "prepublishOnly": "npm run bundle",
-    "test": "vitest run",
-    "test:watch": "vitest watch",
-    "build:skills": "tsx scripts/build-skills.ts",
-    "build:skills:force": "tsx scripts/build-skills.ts --force",
-    "search:docs": "tsx scripts/search-docs.ts"
-  },
-  "keywords": [
-    "funifier",
-    "gamification",
-    "mcp",
-    "model-context-protocol",
-    "claude",
-    "ai",
-    "api-client"
-  ],
-  "license": "MIT",
-  "dependencies": {
-    "@modelcontextprotocol/sdk": "^1.0.0",
-    "axios": "^1.6.0",
-    "zod": "^3.25.76"
-  },
-  "devDependencies": {
-    "@types/node": "^25.5.0",
-    "esbuild": "^0.20.0",
-    "tsx": "^4.21.0",
-    "typescript": "^5.3.0",
-    "vitest": "^1.0.0"
-  },
-  "engines": {
-    "node": ">=18"
-  }
-}
+{
+  "name": "funifier-mcp",
+  "version": "0.2.3",
+  "description": "Funifier AI toolkit — MCP server, API client, and Claude Code skills for the Funifier gamification platform",
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "bin": {
+    "funifier-mcp": "dist/mcp/index.js"
+  },
+  "files": [
+    "dist",
+    "skills",
+    "doc",
+    "datasource-funifier-docs",
+    "AGENTS.md",
+    ".github/copilot-instructions.md",
+    ".cursor/rules/funifier.mdc",
+    "README.md",
+    "LICENSE"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/funifierinc/funifier-mcp.git"
+  },
+  "bugs": {
+    "url": "https://github.com/funifierinc/funifier-mcp/issues"
+  },
+  "homepage": "https://github.com/funifierinc/funifier-mcp#readme",
+  "author": "Funifier",
+  "publishConfig": {
+    "access": "public"
+  },
+  "scripts": {
+    "build": "tsc",
+    "bundle": "npm run build && esbuild dist/mcp/index.js --bundle --outfile=dist/mcp/bundle.js --format=cjs --platform=node --minify",
+    "dev": "tsc --watch",
+    "prepublishOnly": "npm run bundle",
+    "test": "vitest run",
+    "test:watch": "vitest watch",
+    "build:skills": "tsx scripts/build-skills.ts",
+    "build:skills:force": "tsx scripts/build-skills.ts --force",
+    "search:docs": "tsx scripts/search-docs.ts"
+  },
+  "keywords": [
+    "funifier",
+    "gamification",
+    "mcp",
+    "model-context-protocol",
+    "claude",
+    "ai",
+    "api-client"
+  ],
+  "license": "MIT",
+  "dependencies": {
+    "@inquirer/prompts": "^8.4.1",
+    "@modelcontextprotocol/sdk": "^1.0.0",
+    "axios": "^1.6.0",
+    "zod": "^3.25.76"
+  },
+  "devDependencies": {
+    "@types/node": "^25.5.0",
+    "esbuild": "^0.20.0",
+    "tsx": "^4.21.0",
+    "typescript": "^5.3.0",
+    "vitest": "^1.0.0"
+  },
+  "engines": {
+    "node": ">=18"
+  }
+}

package/skills/funifier-create-action/SKILL.md

@@ -1,86 +1,86 @@
----
-name: funifier-create-action
-description: Create a Funifier action — define trackable player behaviors with attributes
----
-
-# funifier-create-action
-
-Create a Funifier action — define trackable player behaviors with attributes
-
-## Persona e Qualidade de Código
-
-A partir de agora, atue como um **desenvolvedor de software sênior altamente experiente**, especializado em **geração de código limpo, legível e de fácil manutenção**. Suas soluções devem seguir rigorosamente as **boas práticas da indústria**, **padrões de projeto** e **arquiteturas modernas**, sempre **evitando overengineering**.
-
-### Ao lidar com qualquer código — seja refatorando ou criando do zero — siga este processo:
-
-1. **Analise cuidadosamente o problema ou o código existente.**
-2. **Raciocine passo a passo** antes de escrever qualquer linha de código.
-3. **Identifique problemas (em caso de refatoração) ou requisitos (em caso de código novo).**
-4. **Defina prioridades e estratégias com base em princípios sólidos de engenharia.**
-5. **Justifique tecnicamente cada decisão**, com base em fundamentos como:
-   - **SOLID**
-   - **DRY (Don't Repeat Yourself)**
-   - **KISS (Keep It Simple, Stupid)**
-   - **YAGNI (You Aren't Gonna Need It)**
-
-Só então prossiga com a implementação.
-
-> **Nota:** Os exemplos de código na documentação Funifier são ilustrativos — podem usar nomes de variáveis genéricos ou scripts monolíticos. Sempre melhore-os: use nomes descritivos, extraia métodos especializados para lógicas complexas e mantenha cada função com responsabilidade única.
-
----
-
-## Before starting — find relevant docs
-
-Run lexical search to load only what you need:
-
-```bash
-npx tsx scripts/search-docs.ts "action track player behavior attributes log event" --skill funifier-create-action
-```
-
-Read only files returned with score > 0.5 (this threshold is printed in the search output).
-
-## Primary docs for this skill
-
-If search returns insufficient results, read directly:
-
-- `datasource-funifier-docs/knowledge/modules/action.md`
-- `datasource-funifier-docs/knowledge/modules/action-log.md`
-
-## Steps
-
-### 1. Understand the requirement
-
-Ask the user what they want to create or accomplish. Gather:
-- The name/title
-- The purpose and behavior
-- Any specific configuration or constraints
-
-### 2. Search for relevant documentation
-
-Run the lexical search (command shown above) and read the returned files.
-
-### 3. Check existing resources (if MCP available)
-
-Use `funifier_list` with the relevant type and a `search` parameter to see
-if a similar resource already exists. Never list all resources without a search term.
-
-### 4. Design and confirm
-
-Based on the docs, outline the configuration to the user and confirm before saving.
-
-### 5. Create or update
-
-Use `funifier_save` with the appropriate type and a JSON payload to create or
-update the resource. If MCP is unavailable, show the complete JSON for manual use.
-
-### 6. Validate
-
-Use `funifier_logs` (for triggers/schedulers) or `funifier_get` to confirm
-the resource was saved correctly and executed without errors.
-
-## MCP
-
-If Funifier MCP tools are available (`funifier_list`, `funifier_save`, `funifier_get`, `funifier_logs`):
-- Use MCP for live server data
-- Use docs for correct patterns and syntax
-- Never learn patterns from existing live resources — docs are authoritative
+---
+name: funifier-create-action
+description: Create a Funifier action — define trackable player behaviors with attributes
+---
+
+# funifier-create-action
+
+Create a Funifier action — define trackable player behaviors with attributes
+
+## Persona e Qualidade de Código
+
+A partir de agora, atue como um **desenvolvedor de software sênior altamente experiente**, especializado em **geração de código limpo, legível e de fácil manutenção**. Suas soluções devem seguir rigorosamente as **boas práticas da indústria**, **padrões de projeto** e **arquiteturas modernas**, sempre **evitando overengineering**.
+
+### Ao lidar com qualquer código — seja refatorando ou criando do zero — siga este processo:
+
+1. **Analise cuidadosamente o problema ou o código existente.**
+2. **Raciocine passo a passo** antes de escrever qualquer linha de código.
+3. **Identifique problemas (em caso de refatoração) ou requisitos (em caso de código novo).**
+4. **Defina prioridades e estratégias com base em princípios sólidos de engenharia.**
+5. **Justifique tecnicamente cada decisão**, com base em fundamentos como:
+   - **SOLID**
+   - **DRY (Don't Repeat Yourself)**
+   - **KISS (Keep It Simple, Stupid)**
+   - **YAGNI (You Aren't Gonna Need It)**
+
+Só então prossiga com a implementação.
+
+> **Nota:** Os exemplos de código na documentação Funifier são ilustrativos — podem usar nomes de variáveis genéricos ou scripts monolíticos. Sempre melhore-os: use nomes descritivos, extraia métodos especializados para lógicas complexas e mantenha cada função com responsabilidade única.
+
+---
+
+## Before starting — find relevant docs
+
+Run lexical search to load only what you need:
+
+```bash
+npx tsx scripts/search-docs.ts "action track player behavior attributes log event" --skill funifier-create-action
+```
+
+Read only files returned with score > 0.5 (this threshold is printed in the search output).
+
+## Primary docs for this skill
+
+If search returns insufficient results, read directly:
+
+- `datasource-funifier-docs/knowledge/modules/action.md`
+- `datasource-funifier-docs/knowledge/modules/action-log.md`
+
+## Steps
+
+### 1. Understand the requirement
+
+Ask the user what they want to create or accomplish. Gather:
+- The name/title
+- The purpose and behavior
+- Any specific configuration or constraints
+
+### 2. Search for relevant documentation
+
+Run the lexical search (command shown above) and read the returned files.
+
+### 3. Check existing resources (if MCP available)
+
+Use `funifier_list` with the relevant type and a `search` parameter to see
+if a similar resource already exists. Never list all resources without a search term.
+
+### 4. Design and confirm
+
+Based on the docs, outline the configuration to the user and confirm before saving.
+
+### 5. Create or update
+
+Use `funifier_save` with the appropriate type and a JSON payload to create or
+update the resource. If MCP is unavailable, show the complete JSON for manual use.
+
+### 6. Validate
+
+Use `funifier_logs` (for triggers/schedulers) or `funifier_get` to confirm
+the resource was saved correctly and executed without errors.
+
+## MCP
+
+If Funifier MCP tools are available (`funifier_list`, `funifier_save`, `funifier_get`, `funifier_logs`):
+- Use MCP for live server data
+- Use docs for correct patterns and syntax
+- Never learn patterns from existing live resources — docs are authoritative

package/skills/funifier-create-aggregate/SKILL.md

@@ -1,87 +1,126 @@
----
-name: funifier-create-aggregate
-description: Create a Funifier prepared aggregate — guided workflow for building MongoDB aggregate pipelines for reports and dashboards
----
-
-# funifier-create-aggregate
-
-Create a Funifier prepared aggregate — guided workflow for building MongoDB aggregate pipelines for reports and dashboards
-
-## Persona e Qualidade de Código
-
-A partir de agora, atue como um **desenvolvedor de software sênior altamente experiente**, especializado em **geração de código limpo, legível e de fácil manutenção**. Suas soluções devem seguir rigorosamente as **boas práticas da indústria**, **padrões de projeto** e **arquiteturas modernas**, sempre **evitando overengineering**.
-
-### Ao lidar com qualquer código — seja refatorando ou criando do zero — siga este processo:
-
-1. **Analise cuidadosamente o problema ou o código existente.**
-2. **Raciocine passo a passo** antes de escrever qualquer linha de código.
-3. **Identifique problemas (em caso de refatoração) ou requisitos (em caso de código novo).**
-4. **Defina prioridades e estratégias com base em princípios sólidos de engenharia.**
-5. **Justifique tecnicamente cada decisão**, com base em fundamentos como:
-   - **SOLID**
-   - **DRY (Don't Repeat Yourself)**
-   - **KISS (Keep It Simple, Stupid)**
-   - **YAGNI (You Aren't Gonna Need It)**
-
-Só então prossiga com a implementação.
-
-> **Nota:** Os exemplos de código na documentação Funifier são ilustrativos — podem usar nomes de variáveis genéricos ou scripts monolíticos. Sempre melhore-os: use nomes descritivos, extraia métodos especializados para lógicas complexas e mantenha cada função com responsabilidade única.
-
----
-
-## Before starting — find relevant docs
-
-Run lexical search to load only what you need:
-
-```bash
-npx tsx scripts/search-docs.ts "aggregate mongodb pipeline report dashboard query prepared" --skill funifier-create-aggregate
-```
-
-Read only files returned with score > 0.5 (this threshold is printed in the search output).
-
-## Primary docs for this skill
-
-If search returns insufficient results, read directly:
-
-- `datasource-funifier-docs/knowledge/guides/aggregates.md`
-- `datasource-funifier-docs/knowledge/guides/database-access.md`
-- `datasource-funifier-docs/knowledge/modules/database.md`
-
-## Steps
-
-### 1. Understand the requirement
-
-Ask the user what they want to create or accomplish. Gather:
-- The name/title
-- The purpose and behavior
-- Any specific configuration or constraints
-
-### 2. Search for relevant documentation
-
-Run the lexical search (command shown above) and read the returned files.
-
-### 3. Check existing resources (if MCP available)
-
-Use `funifier_list` with the relevant type and a `search` parameter to see
-if a similar resource already exists. Never list all resources without a search term.
-
-### 4. Design and confirm
-
-Based on the docs, outline the configuration to the user and confirm before saving.
-
-### 5. Create or update
-
-Use `funifier_save` with the appropriate type and a JSON payload to create or
-update the resource. If MCP is unavailable, show the complete JSON for manual use.
-
-### 6. Validate
-
-Use `funifier_logs` (for triggers/schedulers) or `funifier_get` to confirm
-the resource was saved correctly and executed without errors.
-
-## MCP
-
-If Funifier MCP tools are available (`funifier_list`, `funifier_save`, `funifier_get`, `funifier_logs`):
-- Use MCP for live server data
-- Use docs for correct patterns and syntax
-- Never learn patterns from existing live resources — docs are authoritative
+---
+name: funifier-create-aggregate
+description: Create a Funifier prepared aggregate — guided workflow for building MongoDB aggregate pipelines for reports and dashboards
+---
+
+# funifier-create-aggregate
+
+Create a Funifier prepared aggregate — guided workflow for building MongoDB aggregate pipelines for reports and dashboards
+
+## Persona e Qualidade de Código
+
+A partir de agora, atue como um **desenvolvedor de software sênior altamente experiente**, especializado em **geração de código limpo, legível e de fácil manutenção**. Suas soluções devem seguir rigorosamente as **boas práticas da indústria**, **padrões de projeto** e **arquiteturas modernas**, sempre **evitando overengineering**.
+
+### Ao lidar com qualquer código — seja refatorando ou criando do zero — siga este processo:
+
+1. **Analise cuidadosamente o problema ou o código existente.**
+2. **Raciocine passo a passo** antes de escrever qualquer linha de código.
+3. **Identifique problemas (em caso de refatoração) ou requisitos (em caso de código novo).**
+4. **Defina prioridades e estratégias com base em princípios sólidos de engenharia.**
+5. **Justifique tecnicamente cada decisão**, com base em fundamentos como:
+   - **SOLID**
+   - **DRY (Don't Repeat Yourself)**
+   - **KISS (Keep It Simple, Stupid)**
+   - **YAGNI (You Aren't Gonna Need It)**
+
+Só então prossiga com a implementação.
+
+> **Nota:** Os exemplos de código na documentação Funifier são ilustrativos — podem usar nomes de variáveis genéricos ou scripts monolíticos. Sempre melhore-os: use nomes descritivos, extraia métodos especializados para lógicas complexas e mantenha cada função com responsabilidade única.
+
+---
+
+## Formato do payload (obrigatório)
+
+Funifier armazena código como **strings JSON escapadas**. Ao montar o payload do `funifier_save`:
+
+- **Quebra de linha** → `\n` (nunca newline literal dentro da string)
+- **Aspas duplas** dentro do código → `\"`
+- **Backslash** → `\\` (regex `\b` vira `\\b`; dentro de Groovy com string-building pode exigir `\\\\b`)
+- **Tab** → `\t` (se usar)
+- **Pipelines de aggregate** vão como **string JSON** (não objeto aninhado) — serialize o array inteiro
+
+A regra prática: monte o objeto em JavaScript normalmente e passe por `JSON.stringify` — o MCP faz isso automaticamente quando você entrega o payload como JSON. **Nunca** cole código multilinha cru no meio do JSON.
+
+### Exemplo 1 — custom-page (html + angularjs script)
+
+```json
+{
+  "title": "Ciclos",
+  "slug": "studio/custom/ciclos",
+  "html": "<div class=\"row\">\n  <div class=\"col-md-12\">\n    <h2>Ciclos</h2>\n  </div>\n</div>\n",
+  "script": "$scope.all = [];\n$scope.loading = false;\n\n$scope.list = function () {\n  $scope.loading = true;\n};\n$scope.list();\n"
+}
+```
+
+### Exemplo 2 — aggregate preparado (pipeline JSON + script Groovy)
+
+```json
+{
+  "_id": "extrato",
+  "title": "Extrato de Pontos",
+  "collection": "extrato",
+  "aggregate": "[\n  {\n    \"$match\": { \"player\": \"$param:player\" }\n  },\n  {\n    \"$sort\": { \"time\": -1 }\n  }\n]",
+  "script": "void prepare(aggregations, params) {\n    if (context.get(\"player\") != null) {\n        params.put(\"player\", context.get(\"player\"));\n    } else {\n        params.put(\"player\", \"NAO_EXISTE\");\n    }\n}\n"
+}
+```
+
+Note que `aggregate` é uma **string** contendo JSON serializado (com `\n` e `\"` escapados), **não** um array nativo. Mesma regra vale para `script` em triggers/schedulers/aggregates e `html`/`script` em custom-pages.
+
+---
+
+## Before starting — find relevant docs
+
+Run lexical search to load only what you need:
+
+```bash
+npx tsx scripts/search-docs.ts "aggregate mongodb pipeline report dashboard query prepared" --skill funifier-create-aggregate
+```
+
+Read only files returned with score > 0.5 (this threshold is printed in the search output).
+
+## Primary docs for this skill
+
+If search returns insufficient results, read directly:
+
+- `datasource-funifier-docs/knowledge/guides/aggregates.md`
+- `datasource-funifier-docs/knowledge/guides/database-access.md`
+- `datasource-funifier-docs/knowledge/modules/database.md`
+
+## Steps
+
+### 1. Understand the requirement
+
+Ask the user what they want to create or accomplish. Gather:
+- The name/title
+- The purpose and behavior
+- Any specific configuration or constraints
+
+### 2. Search for relevant documentation
+
+Run the lexical search (command shown above) and read the returned files.
+
+### 3. Check existing resources (if MCP available)
+
+Use `funifier_list` with the relevant type and a `search` parameter to see
+if a similar resource already exists. Never list all resources without a search term.
+
+### 4. Design and confirm
+
+Based on the docs, outline the configuration to the user and confirm before saving.
+
+### 5. Create or update
+
+Use `funifier_save` with the appropriate type and a JSON payload to create or
+update the resource. If MCP is unavailable, show the complete JSON for manual use.
+
+### 6. Validate
+
+Use `funifier_logs` (for triggers/schedulers) or `funifier_get` to confirm
+the resource was saved correctly and executed without errors.
+
+## MCP
+
+If Funifier MCP tools are available (`funifier_list`, `funifier_save`, `funifier_get`, `funifier_logs`):
+- Use MCP for live server data
+- Use docs for correct patterns and syntax
+- Never learn patterns from existing live resources — docs are authoritative