@rubytech/create-maxy 1.0.461 → 1.0.462

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/create-maxy",
-  "version": "1.0.461",
+  "version": "1.0.462",
   "description": "Install Maxy — AI for Productive People",
   "bin": {
     "create-maxy": "./dist/index.js"

package/payload/maxy/server.js

@@ -5102,7 +5102,7 @@ function getMcpServers(accountId, enabledPlugins) {
     // the always-on Chromium instance started by vnc.sh on display :99.
     "plugin_playwright_playwright": {
       command: "npx",
-      args: ["-y", "@playwright/mcp@latest", "--cdp-endpoint", "http://127.0.0.1:9222"]
+      args: ["-y", "@playwright/mcp@latest", "--cdp-endpoint", "http://127.0.0.1:9222", "--caps", "pdf"]
     }
   };
   if (process.env.TELEGRAM_PUBLIC_BOT_TOKEN) {

package/payload/platform/plugins/admin/skills/skill-builder/SKILL.md

@@ -46,6 +46,8 @@ Ask what rules the agent should follow when using this skill:
 
 Not every skill needs all of these. Only include what's relevant.
 
+If the skill involves generating PDFs or print-ready documents, load `references/pdf-generation.md` for the constraints on HTML layout and the `browser_pdf_save` rendering path.
+
 ## Step 4: Decide on References
 
 If the skill has detailed procedures, templates, or data formats, those belong in `references/` files — not inline in SKILL.md.

package/payload/platform/plugins/admin/skills/skill-builder/references/pdf-generation.md

@@ -0,0 +1,30 @@
+# PDF Generation in Skills
+
+When a skill needs to produce a PDF, the output is always a two-stage process: the skill authors the HTML, and the browser-specialist renders it to PDF via the `browser_pdf_save` MCP tool.
+
+## The rule
+
+Never instruct the agent to write or execute raw Node.js scripts (e.g. `require('playwright')`, `page.pdf()`, `npx playwright`). Playwright is not in the Node.js module path — these scripts fail with MODULE_NOT_FOUND, waste tool calls searching the filesystem, and produce hardcoded paths that break on reinstall.
+
+Instead, skills that produce PDFs should:
+
+1. **Build the HTML** — the skill's behaviour section describes what the document contains and how it's structured. The agent writes the HTML file using standard file tools.
+2. **Delegate rendering to browser-specialist** — the agent asks the browser-specialist to navigate to the HTML file and call `browser_pdf_save` to produce the PDF. The specialist has Playwright access through governed MCP tools; the admin agent does not.
+
+## Print-ready HTML constraints
+
+HTML intended for PDF output must follow print-ready layout patterns. The most common failures when agents design their own pagination are rigid fixed-height page divs (causing whitespace gaps) and `position: fixed` hacks for headers/footers (causing overlap and duplication).
+
+**Continuous flow layout** — content flows naturally. Use `@page` margin rules for page margins, not wrapper divs with fixed heights. Use `page-break-inside: avoid` on logical units (cards, tables, stat groups) and `page-break-before: always` on major section dividers.
+
+**Page numbers and running footers** — use `@page` margin boxes (`@bottom-center { content: counter(page); }`), not JavaScript or position-fixed elements.
+
+**Dark backgrounds in print** — browsers strip background colours by default. Add `print-color-adjust: exact; -webkit-print-color-adjust: exact;` to dark elements in `@media print`.
+
+**Cover and back pages** — full-bleed pages use `height: 100vh; page-break-after: always;` in `@media print` with zero `@page` margins (via `@page :first` for covers, named pages for back pages).
+
+**Glassmorphism and backdrop-filter** — these do not survive browser print rendering. Any section using glassmorphism needs a pre-rendered PNG fallback image that is hidden on screen and shown only in `@media print`.
+
+## What the skill file should contain
+
+The skill's SKILL.md describes the document's purpose and structure. A `references/` file holds the HTML template or content specification. The skill should state that PDF rendering is delegated to browser-specialist — it should not contain Playwright code, npm commands, or file path assumptions about the Playwright installation.

package/payload/platform/plugins/whatsapp/skills/manage-whatsapp-config/SKILL.md

@@ -17,22 +17,42 @@ Call `whatsapp-status` first — if no WhatsApp account is connected, direct the
 
 ## Presenting settings
 
-Call `whatsapp-config action: schema` to get field definitions with descriptions, types, defaults, and constraints. Use the Description column from the schema output as the `description` field on each form field — do not improvise descriptions.
+Call `whatsapp-config action: schema` to get field definitions with descriptions, and `whatsapp-config action: get-config` to get current values. Use the Description column from the schema output as the `description` field on each form field — do not improvise descriptions.
 
-Group related settings logically when presenting:
+### Admin phones
 
-1. **Messaging policies** — dmPolicy, groupPolicy, allowFrom, groupAllowFrom
-2. **Operational limits** — mediaMaxMb, textChunkLimit, debounceMs
-3. **Behaviour** — sendReadReceipts, ackReaction
-4. **Account settings** — name, enabled, selfChatMode
-5. **Group configuration** — groups (per-group activation)
+Before the form, call `whatsapp-config action: list-admin-phones` and display the result. Admin phones are managed via `add-admin-phone` / `remove-admin-phone` — they are not editable in this form.
 
-Present settings as a `render-component` form with:
-- `description` on every field (from schema output)
-- `defaultValue` showing the current value or the schema default
-- Rich option labels with descriptions for enum fields (e.g. dmPolicy options should explain what "open", "allowlist", and "disabled" each mean)
+### Form fields
 
-Before the user submits, summarise what each default does — the user should understand the implications of keeping defaults, not just see them pre-filled.
+Present settings as a `render-component` form. Each field must have a unique `name` matching the schema field name (used as the state key and the `update-config` field key), a `type`, a `label` (plain English), and a `description` (from schema output). For selects, specify `options`. For all fields, set `defaultValue` from `get-config` (current value) or the schema default.
+
+**Messaging policies:**
+
+- `dmPolicy` (`select`): label "Who can message your agent (DMs)", options:
+  - `open` — "Open — anyone can message"
+  - `allowlist` — "Allowlist — only approved numbers"
+  - `disabled` — "Disabled — no public DMs"
+- `groupPolicy` (`select`): label "Group message handling", options:
+  - `open` — "Always — respond to all group messages"
+  - `allowlist` — "Allowlist — only in approved groups"
+  - `disabled` — "Disabled — ignore all group messages"
+
+**Behaviour:**
+
+- `sendReadReceipts` (`select`): label "Blue ticks (read receipts)", options:
+  - `true` — "On — contacts see read receipts"
+  - `false` — "Off — no read receipts"
+
+**Operational limits:**
+
+- `mediaMaxMb` (`number`): label "Media size limit (MB)"
+- `textChunkLimit` (`number`): label "Message chunk limit (characters)"
+- `debounceMs` (`number`): label "Message batching delay (ms)"
+
+### Submit
+
+The form's `submitMessage` must map the field values back to `update-config` field names: `Save these WhatsApp settings: {{json}}` — where `{{json}}` produces the JSON object with field names as keys (e.g. `{ "dmPolicy": "open", "mediaMaxMb": 50, ... }`).
 
 ## Group configuration
 
@@ -51,9 +71,11 @@ After the user submits, write changes via `whatsapp-config action: "update-confi
 
 ## Language
 
-Use plain English:
-- "Who can message your agent" not "dmPolicy"
-- "Message batching delay" not "debounceMs"
-- "Media size limit" not "mediaMaxMb"
-- "Blue ticks" not "sendReadReceipts"
-- Group names, not JIDs
+Plain English goes in `label` — schema field names go in `name`. The `name` property is the machine key (must match the schema exactly); the `label` is what the user reads. Examples:
+
+- `name: "dmPolicy"`, `label: "Who can message your agent (DMs)"`
+- `name: "debounceMs"`, `label: "Message batching delay (ms)"`
+- `name: "mediaMaxMb"`, `label: "Media size limit (MB)"`
+- `name: "sendReadReceipts"`, `label: "Blue ticks (read receipts)"`
+
+Group names (not JIDs) in all user-facing text.

package/payload/platform/templates/specialists/agents/browser-specialist.md

@@ -3,7 +3,7 @@ name: browser-specialist
 description: "Web browser tasks — visiting websites, filling forms, clicking buttons, and reading page content. Delegate when a task requires controlling the browser."
 summary: "Browses the web on your behalf — visiting websites, filling in forms, and extracting information. For example, when you need to sign up for a service, check a competitor's pricing page, or set up an online account."
 model: claude-sonnet-4-6
-tools: mcp__plugin_playwright_playwright__browser_navigate, mcp__plugin_playwright_playwright__browser_navigate_back, mcp__plugin_playwright_playwright__browser_snapshot, mcp__plugin_playwright_playwright__browser_take_screenshot, mcp__plugin_playwright_playwright__browser_click, mcp__plugin_playwright_playwright__browser_fill, mcp__plugin_playwright_playwright__browser_fill_form, mcp__plugin_playwright_playwright__browser_type, mcp__plugin_playwright_playwright__browser_press_key, mcp__plugin_playwright_playwright__browser_hover, mcp__plugin_playwright_playwright__browser_select_option, mcp__plugin_playwright_playwright__browser_wait_for, mcp__plugin_playwright_playwright__browser_handle_dialog, mcp__plugin_playwright_playwright__browser_evaluate, mcp__plugin_playwright_playwright__browser_console_messages, mcp__plugin_playwright_playwright__browser_resize, mcp__plugin_playwright_playwright__browser_tabs, mcp__plugin_playwright_playwright__browser_close, mcp__admin__api-key-store
+tools: mcp__plugin_playwright_playwright__browser_navigate, mcp__plugin_playwright_playwright__browser_navigate_back, mcp__plugin_playwright_playwright__browser_snapshot, mcp__plugin_playwright_playwright__browser_take_screenshot, mcp__plugin_playwright_playwright__browser_click, mcp__plugin_playwright_playwright__browser_fill, mcp__plugin_playwright_playwright__browser_fill_form, mcp__plugin_playwright_playwright__browser_type, mcp__plugin_playwright_playwright__browser_press_key, mcp__plugin_playwright_playwright__browser_hover, mcp__plugin_playwright_playwright__browser_select_option, mcp__plugin_playwright_playwright__browser_wait_for, mcp__plugin_playwright_playwright__browser_handle_dialog, mcp__plugin_playwright_playwright__browser_evaluate, mcp__plugin_playwright_playwright__browser_console_messages, mcp__plugin_playwright_playwright__browser_resize, mcp__plugin_playwright_playwright__browser_tabs, mcp__plugin_playwright_playwright__browser_close, mcp__plugin_playwright_playwright__browser_pdf_save, mcp__admin__api-key-store
 ---
 
 # Browser Specialist