@rubytech/taskmaster 1.0.3 → 1.0.5

package/README.md

@@ -14,7 +14,7 @@ taskmaster provision
 Or one command on a fresh device:
 
 ```bash
-curl -fsSL https://taskmaster.bot/install.sh | bash
+curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 ```
 
 After install, open the setup wizard in your browser:

package/dist/agents/system-prompt.js

@@ -122,7 +122,7 @@ export function buildAgentSystemPrompt(params) {
         browser: "Control web browser",
         canvas: "Present/eval/snapshot the Canvas",
         nodes: "List/describe/notify/camera/screen on paired nodes",
-        cron: "Manage cron jobs and wake events (use for reminders; when scheduling a reminder, write the systemEvent text as something that will read like a reminder when it fires, and mention that it is a reminder depending on the time gap between setting and firing; include recent context in reminder text if appropriate)",
+        cron: "Manage scheduled events and wake events (use for reminders; when scheduling a reminder, write the systemEvent text as something that will read like a reminder when it fires, and mention that it is a reminder depending on the time gap between setting and firing; include recent context in reminder text if appropriate)",
         message: "Send messages and channel actions",
         gateway: "Restart, apply config, or run updates on the running Taskmaster process",
         agents_list: "List agent ids allowed for sessions_spawn",
@@ -263,7 +263,7 @@ export function buildAgentSystemPrompt(params) {
                 "- browser: control Taskmaster's dedicated browser",
                 "- canvas: present/eval/snapshot the Canvas",
                 "- nodes: list/describe/notify/camera/screen on paired nodes",
-                "- cron: manage cron jobs and wake events (use for reminders; when scheduling a reminder, write the systemEvent text as something that will read like a reminder when it fires, and mention that it is a reminder depending on the time gap between setting and firing; include recent context in reminder text if appropriate)",
+                "- cron: manage scheduled events and wake events (use for reminders; when scheduling a reminder, write the systemEvent text as something that will read like a reminder when it fires, and mention that it is a reminder depending on the time gap between setting and firing; include recent context in reminder text if appropriate)",
                 "- sessions_list: list sessions",
                 "- sessions_history: fetch session history",
                 "- sessions_send: send to another session",

package/dist/agents/tool-display.json

@@ -145,7 +145,7 @@
         },
         "cron": {
             "emoji": "⏰",
-            "title": "Cron",
+            "title": "Events",
             "actions": {
                 "status": { "label": "status" },
                 "list": { "label": "list" },

package/dist/agents/tools/cron-tool.js

@@ -113,21 +113,21 @@ async function buildReminderContextLines(params) {
 }
 export function createCronTool(opts) {
     return {
-        label: "Cron",
+        label: "Events",
         name: "cron",
-        description: `Manage Gateway cron jobs (status/list/add/update/remove/run/runs) and send wake events.
+        description: `Manage scheduled events (status/list/add/update/remove/run/runs) and send wake events.
 
 ACTIONS:
-- status: Check cron scheduler status
-- list: List jobs (use includeDisabled:true to include disabled)
-- add: Create job (requires job object, see schema below)
-- update: Modify job (requires jobId + patch object)
-- remove: Delete job (requires jobId)
-- run: Trigger job immediately (requires jobId)
-- runs: Get job run history (requires jobId)
+- status: Check event scheduler status
+- list: List events (use includeDisabled:true to include disabled). Returns all events for your account.
+- add: Create event (requires job object, see schema below)
+- update: Modify event (requires jobId + patch object)
+- remove: Delete event (requires jobId)
+- run: Trigger event immediately (requires jobId)
+- runs: Get event run history (requires jobId)
 - wake: Send wake event (requires text, optional mode)
 
-JOB SCHEMA (for add action):
+EVENT SCHEMA (for add action):
 {
   "name": "string (optional)",
   "schedule": { ... },      // Required: when to run
@@ -158,7 +158,7 @@ WAKE MODES (for wake action):
 - "next-heartbeat" (default): Wake on next heartbeat
 - "now": Wake immediately
 
-Use jobId as the canonical identifier; id is accepted for compatibility. Use contextMessages (0-10) to add previous messages as context to the job text.`,
+Use jobId as the canonical identifier; id is accepted for compatibility. Use contextMessages (0-10) to add previous messages as context to the event text.`,
         parameters: CronToolSchema,
         execute: async (_toolCallId, args) => {
             const params = args;
@@ -171,10 +171,15 @@ Use jobId as the canonical identifier; id is accepted for compatibility. Use con
             switch (action) {
                 case "status":
                     return jsonResult(await callGatewayTool("cron.status", gatewayOpts, {}));
-                case "list":
-                    return jsonResult(await callGatewayTool("cron.list", gatewayOpts, {
+                case "list": {
+                    const listParams = {
                         includeDisabled: Boolean(params.includeDisabled),
-                    }));
+                    };
+                    const accountId = opts?.agentAccountId;
+                    if (accountId)
+                        listParams.accountId = accountId;
+                    return jsonResult(await callGatewayTool("cron.list", gatewayOpts, listParams));
+                }
                 case "add": {
                     if (!params.job || typeof params.job !== "object") {
                         throw new Error("job required");

package/dist/build-info.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.0.3",
-  "commit": "f5ee9266aae9d8aa35a658d4cc7d946a75ddf524",
-  "builtAt": "2026-02-14T19:48:12.948Z"
+  "version": "1.0.5",
+  "commit": "0d0cd3f87e0115e7ae887f96fefa33d8fdedbddb",
+  "builtAt": "2026-02-15T07:57:32.812Z"
 }

package/dist/cli/provision-seed.js

@@ -87,7 +87,11 @@ export function buildDefaultAgentList(workspaceRoot) {
                     ],
                 },
                 write: {
-                    include: ["memory/users/{peer}/**", "memory/groups/{peer}/**"],
+                    include: [
+                        "memory/users/{peer}/**",
+                        "memory/groups/{peer}/**",
+                        "memory/shared/events/**",
+                    ],
                 },
             },
         },

package/dist/config/version.js

@@ -13,11 +13,21 @@ export function parseTaskmasterVersion(raw) {
         revision: revision ? Number.parseInt(revision, 10) : 0,
     };
 }
+/**
+ * Date-based versions (e.g. 2026.1.25) have major >= 2000.
+ * Semver versions (e.g. 1.0.4) have major < 100.
+ * Comparing across formats is meaningless — return null.
+ */
+function isDateVersion(v) {
+    return v.major >= 2000;
+}
 export function compareTaskmasterVersions(a, b) {
     const parsedA = parseTaskmasterVersion(a);
     const parsedB = parseTaskmasterVersion(b);
     if (!parsedA || !parsedB)
         return null;
+    if (isDateVersion(parsedA) !== isDateVersion(parsedB))
+        return null;
     if (parsedA.major !== parsedB.major)
         return parsedA.major < parsedB.major ? -1 : 1;
     if (parsedA.minor !== parsedB.minor)

package/dist/gateway/protocol/schema/cron.js

@@ -66,6 +66,7 @@ export const CronJobStateSchema = Type.Object({
 export const CronJobSchema = Type.Object({
     id: NonEmptyString,
     agentId: Type.Optional(NonEmptyString),
+    accountId: Type.Optional(NonEmptyString),
     name: NonEmptyString,
     description: Type.Optional(Type.String()),
     enabled: Type.Boolean(),
@@ -82,11 +83,13 @@ export const CronJobSchema = Type.Object({
 export const CronListParamsSchema = Type.Object({
     includeDisabled: Type.Optional(Type.Boolean()),
     agentIds: Type.Optional(Type.Array(Type.String())),
+    accountId: Type.Optional(Type.String()),
 }, { additionalProperties: false });
 export const CronStatusParamsSchema = Type.Object({}, { additionalProperties: false });
 export const CronAddParamsSchema = Type.Object({
     name: NonEmptyString,
     agentId: Type.Optional(Type.Union([NonEmptyString, Type.Null()])),
+    accountId: Type.Optional(Type.Union([NonEmptyString, Type.Null()])),
     description: Type.Optional(Type.String()),
     enabled: Type.Optional(Type.Boolean()),
     deleteAfterRun: Type.Optional(Type.Boolean()),
@@ -99,6 +102,7 @@ export const CronAddParamsSchema = Type.Object({
 export const CronJobPatchSchema = Type.Object({
     name: Type.Optional(NonEmptyString),
     agentId: Type.Optional(Type.Union([NonEmptyString, Type.Null()])),
+    accountId: Type.Optional(Type.Union([NonEmptyString, Type.Null()])),
     description: Type.Optional(Type.String()),
     enabled: Type.Optional(Type.Boolean()),
     deleteAfterRun: Type.Optional(Type.Boolean()),

package/dist/gateway/server-methods/cron.js

@@ -28,6 +28,10 @@ export const cronHandlers = {
                 return jobAgent !== undefined && normalized.includes(jobAgent);
             });
         }
+        if (typeof p.accountId === "string" && p.accountId.trim()) {
+            const target = p.accountId.trim();
+            jobs = jobs.filter((job) => job.accountId === target);
+        }
         respond(true, { jobs }, undefined);
     },
     "cron.status": async ({ params, respond, context }) => {

package/dist/gateway/server.impl.js

@@ -5,6 +5,7 @@ import { listChannelPlugins } from "../channels/plugins/index.js";
 import { createDefaultDeps } from "../cli/deps.js";
 import { formatCliCommand } from "../cli/command-format.js";
 import { CONFIG_PATH_TASKMASTER, isNixMode, loadConfig, migrateLegacyConfig, readConfigFileSnapshot, writeConfigFile, } from "../config/config.js";
+import { VERSION } from "../version.js";
 import { isDiagnosticsEnabled } from "../infra/diagnostic-events.js";
 import { logAcceptedEnvOption } from "../infra/env.js";
 import { applyPluginAutoEnable } from "../config/plugin-auto-enable.js";
@@ -116,6 +117,17 @@ export async function startGatewayServer(port = 18789, opts = {}) {
             log.warn(`gateway: failed to persist plugin auto-enable changes: ${String(err)}`);
         }
     }
+    // Stamp config with running version on startup so upgrades keep the stamp current.
+    const storedVersion = configSnapshot.config.meta?.lastTouchedVersion;
+    if (configSnapshot.exists && storedVersion !== VERSION) {
+        try {
+            await writeConfigFile(configSnapshot.config);
+            log.info(`gateway: updated config version stamp from ${storedVersion ?? "(none)"} to ${VERSION}`);
+        }
+        catch (err) {
+            log.warn(`gateway: failed to update config version stamp: ${String(err)}`);
+        }
+    }
     const cfgAtStart = loadConfig();
     // License check — gateway always starts (so setup UI is reachable),
     // but pages other than /setup will redirect until a license is activated.

package/dist/infra/update-check.js

@@ -214,7 +214,7 @@ export async function fetchNpmTagVersion(params) {
     const timeoutMs = params?.timeoutMs ?? 3500;
     const tag = params.tag;
     try {
-        const res = await fetchWithTimeout(`https://registry.npmjs.org/taskmaster/${encodeURIComponent(tag)}`, timeoutMs);
+        const res = await fetchWithTimeout(`https://registry.npmjs.org/@rubytech%2Ftaskmaster/${encodeURIComponent(tag)}`, timeoutMs);
         if (!res.ok) {
             return { tag, version: null, error: `HTTP ${res.status}` };
         }

package/dist/logging/logger.js

@@ -26,20 +26,32 @@ function attachExternalTransport(logger, transport) {
         }
     });
 }
+let resolvingSettings = false;
 function resolveSettings() {
-    let cfg = loggingState.overrideSettings ?? readLoggingConfig();
-    if (!cfg) {
-        try {
-            const loaded = requireConfig("../config/config.js");
-            cfg = loaded.loadConfig?.().logging;
-        }
-        catch {
-            cfg = undefined;
+    // Guard against recursion: loadConfig() may trigger logging during
+    // validation, which calls getLogger() → resolveSettings() again.
+    if (resolvingSettings) {
+        return { level: "info", file: defaultRollingPathForToday() };
+    }
+    resolvingSettings = true;
+    try {
+        let cfg = loggingState.overrideSettings ?? readLoggingConfig();
+        if (!cfg) {
+            try {
+                const loaded = requireConfig("../config/config.js");
+                cfg = loaded.loadConfig?.().logging;
+            }
+            catch {
+                cfg = undefined;
+            }
         }
+        const level = normalizeLogLevel(cfg?.level, "info");
+        const file = cfg?.file ?? defaultRollingPathForToday();
+        return { level, file };
+    }
+    finally {
+        resolvingSettings = false;
     }
-    const level = normalizeLogLevel(cfg?.level, "info");
-    const file = cfg?.file ?? defaultRollingPathForToday();
-    return { level, file };
 }
 function settingsChanged(a, b) {
     if (!a)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rubytech/taskmaster",
-  "version": "1.0.3",
+  "version": "1.0.5",
   "description": "AI-powered business assistant for small businesses",
   "publishConfig": {
     "access": "public"

package/scripts/install.sh

@@ -4,10 +4,10 @@ set -euo pipefail
 # Taskmaster — one-command install for fresh devices (Pi or Mac).
 #
 # Usage:
-#   curl -fsSL https://taskmaster.bot/install.sh | bash
+#   curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 #
 # With custom port:
-#   curl -fsSL https://taskmaster.bot/install.sh | bash -s -- --port 19000
+#   curl -fsSL https://taskmaster.bot/install.sh | sudo bash -s -- --port 19000
 
 PORT=""
 for arg in "$@"; do

package/scripts/postinstall.js

@@ -2,7 +2,13 @@ import fs from "node:fs";
 import path from "node:path";
 import { spawnSync } from "node:child_process";
 import { fileURLToPath } from "node:url";
-import { setupGitHooks } from "./setup-git-hooks.js";
+let setupGitHooks = () => {};
+try {
+  const mod = await import("./setup-git-hooks.js");
+  setupGitHooks = mod.setupGitHooks;
+} catch {
+  // setup-git-hooks.js is not shipped in the npm package — skip in production
+}
 
 function detectPackageManager(ua = process.env.npm_config_user_agent ?? "") {
   // Examples:

package/skills/business-assistant/SKILL.md

@@ -214,7 +214,7 @@ Always ask the business owner before reshuffling. Never move a job without appro
 **Real-time location (GPS):**
 If the business owner's phone is paired as a node, you can query their GPS location on demand using `location.get`. Use this for:
 - **Customer asks "where is he?"** → Check GPS, compare to next appointment location, give an ETA: "[name] left his last job about 15 minutes ago. He should be with you in about 20 minutes."
-- **Late detection** → If you have a cron check 10 minutes before each appointment, query GPS. If the business owner is still far away, proactively message the customer: "Hi! [name]'s running about 15 minutes late — he's on his way. Sorry for the wait!" This turns a complaint into a professional courtesy.
+- **Late detection** → If you have a scheduled event check 10 minutes before each appointment, query GPS. If the business owner is still far away, proactively message the customer: "Hi! [name]'s running about 15 minutes late — he's on his way. Sorry for the wait!" This turns a complaint into a professional courtesy.
 - **Business owner or their partner asks "where is [name]?"** → Report current location and next job ETA.
 - **End-of-day** → If the business owner is near their home postcode, stop offering same-day appointments.
 - Do NOT track location continuously. Only query when you have a specific reason.
@@ -339,7 +339,7 @@ Customers can always request to speak to the business owner directly. The agent
 
 ## Morning Briefing
 
-If a cron job is set up for morning briefings, send a daily summary. **Group jobs by area, not just time.** Include postcodes, estimated travel, and total driving time. See Schedule Optimisation section for full format.
+If a scheduled event is set up for morning briefings, send a daily summary. **Group jobs by area, not just time.** Include postcodes, estimated travel, and total driving time. See Schedule Optimisation section for full format.
 
 > **Morning [name]! Here's your Tuesday:**
 >

package/skills/event-management/SKILL.md

@@ -0,0 +1,15 @@
+# Event Management
+
+Applies when handling anything time-bound: appointments, meetings, reminders, follow-ups, callbacks, deadlines — any commitment or scheduled action between one or more parties.
+
+## When to activate
+
+- Customer requests or confirms an appointment
+- Business owner asks to schedule, reschedule, or cancel something
+- A reminder, follow-up, or callback needs to be recorded
+- Someone asks "what's on [day/week]?" or "show me the schedule"
+- A deadline or time-sensitive commitment is mentioned
+
+## References
+
+Load `references/events.md` for the standard event template, file naming, dual-write pattern, and calendar query instructions.

package/skills/event-management/references/events.md

@@ -0,0 +1,120 @@
+# Events
+
+Events are any time-bound information: appointments, meetings, reminders, follow-ups, callbacks, deadlines. Anything that represents a commitment, agreement, or scheduled action between one or more parties.
+
+---
+
+## Standard Event Format
+
+Every event file follows this structure. All fields above the `## Notes` section are required unless marked optional.
+
+```markdown
+# Event: [Short descriptive title]
+
+- **Date:** YYYY-MM-DD
+- **Time:** HH:MM (24h, local timezone)
+- **Duration:** [number] min
+- **Customer:** [Name] ([phone])
+- **Service:** [what is being done]
+- **Location:** [address or "Remote" / "Phone"]
+- **Status:** confirmed | tentative | cancelled | completed
+- **Created by:** [agent id — e.g. public, admin]
+- **Created:** YYYY-MM-DDTHH:MM:SSZ
+
+## Notes
+[Free text — special instructions, context, history of changes]
+```
+
+### Field guidance
+
+- **Date/Time** — always local timezone. If the business owner's timezone is known, use it consistently.
+- **Duration** — estimated in minutes. If unknown, use a reasonable default for the service type and note the assumption.
+- **Customer** — full name and phone in international format. For internal events (admin meetings, personal reminders) use the owner's name and number.
+- **Status** — `confirmed` when both parties have agreed. `tentative` when proposed but not confirmed. `cancelled` when called off. `completed` after the event has passed and the work is done.
+- **Service** — brief description of the work or purpose. Not a category — use plain language ("boiler service", "quote for kitchen extension", "team meeting").
+
+---
+
+## File Naming
+
+Files are named for sort order and human readability:
+
+```
+YYYY-MM-DD-slug.md
+```
+
+Examples:
+- `2026-02-20-boiler-service-john-smith.md`
+- `2026-02-21-quote-mrs-jenkins.md`
+- `2026-03-01-team-meeting.md`
+
+The slug should be lowercase, hyphenated, and include enough context to identify the event without opening the file.
+
+---
+
+## Where to Write
+
+Every event must be written to **two** locations:
+
+1. **Per-customer record:** `memory/users/{phone}/events/YYYY-MM-DD-slug.md`
+   - Scoped to the customer. Visible when reviewing that customer's history.
+2. **Shared calendar:** `memory/shared/events/YYYY-MM-DD-slug.md`
+   - Visible to all agents in the account. The admin agent uses this for calendar queries.
+
+Both files have identical content. Write to both in the same operation.
+
+For events that have no external customer (internal meetings, personal reminders), write only to `memory/shared/events/`.
+
+---
+
+## Updating Events
+
+When an event changes (rescheduled, cancelled, details updated):
+
+1. Update **both** copies — the per-customer file and the shared calendar file.
+2. Change the **Status** field appropriately.
+3. Add a note in the `## Notes` section explaining the change and when it happened.
+4. If the date changes, rename both files to reflect the new date. Delete the old files.
+
+---
+
+## Querying the Calendar
+
+To answer "what's on [day/week]?" or "show me the schedule":
+
+1. List files in `memory/shared/events/` — filenames are date-prefixed, so lexicographic order is chronological order.
+2. Filter by date prefix (e.g., `2026-02-20` for a specific day, `2026-02-` for a month).
+3. Read the matching files for details.
+
+This is a directory listing + read operation, not a search. It is fast and complete.
+
+---
+
+## Linking Events to Scheduled Reminders
+
+Events (calendar data) and scheduled reminders (the `cron` tool) serve different purposes:
+
+- **Event file** — the record of what is happening, when, and with whom. Source of truth for the calendar.
+- **Scheduled reminder** (`cron` tool) — an automated trigger that fires at a specific time to notify or act. Optional.
+
+When you create an event that also needs a reminder (e.g., "remind me 30 minutes before"), create both:
+1. The event file (in both locations, as above)
+2. A scheduled reminder via the `cron` tool, referencing the event
+
+The reminder's payload text should reference the event clearly so the recipient has full context when it fires.
+
+---
+
+## Event Types
+
+This format covers all time-bound data. Examples:
+
+| Type | Customer field | Location | Notes |
+|------|---------------|----------|-------|
+| Customer appointment | Customer name + phone | Job site address | Service details, access instructions |
+| Quote visit | Customer name + phone | Site address | What to quote, measurements needed |
+| Callback | Customer name + phone | "Phone" | Why they're expecting a call, promised window |
+| Follow-up | Customer name + phone | n/a | What to follow up on, last interaction context |
+| Internal meeting | Owner name + phone | Meeting link or office | Agenda, attendees |
+| Personal reminder | Owner name + phone | n/a | What to remember, deadline context |
+| Deadline | Owner or customer | n/a | What's due, consequences of missing it |

package/taskmaster-docs/USER-GUIDE.md

@@ -39,7 +39,7 @@ You'll need a monitor, keyboard, and mouse connected to the Pi.
 2. Run:
 
 ```
-curl -fsSL https://taskmaster.bot/install.sh | bash
+curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 ```
 
 3. Wait for it to finish (a few minutes — it installs Node.js if needed)
@@ -54,7 +54,7 @@ You can also access the setup page from any other device on the same network at
 Open **Terminal** (search for "Terminal" in Spotlight) and run:
 
 ```
-curl -fsSL https://taskmaster.bot/install.sh | bash
+curl -fsSL https://taskmaster.bot/install.sh | sudo bash
 ```
 
 This installs Node.js (if needed), Taskmaster, and sets up the background service. Once finished, open your browser and go to: **http://localhost:18789/setup**
@@ -62,7 +62,7 @@ This installs Node.js (if needed), Taskmaster, and sets up the background servic
 **Custom port:** If you're running multiple Taskmaster instances (e.g., one on a Pi and one on a Mac), give each a different port:
 
 ```
-curl -fsSL https://taskmaster.bot/install.sh | bash -s -- --port 19000
+curl -fsSL https://taskmaster.bot/install.sh | sudo bash -s -- --port 19000
 ```
 
 ### Option D: Install from a package file

package/templates/taskmaster/agents/admin/AGENTS.md

@@ -142,11 +142,11 @@ Keep it brief. Bullet points. Only what matters.
 
 ---
 
-## Reminders (Cron Tool)
+## Reminders (Events Tool)
 
-When [OWNER_NAME] asks you to remind them about something, use the `cron` tool correctly.
+When [OWNER_NAME] asks you to remind them about something, use the `cron` tool (named "Events" in the UI) correctly.
 
-### CRITICAL: Two Types of Cron Jobs
+### CRITICAL: Two Types of Scheduled Events
 
 | Type | When to Use | What Happens |
 |------|-------------|--------------|
@@ -197,11 +197,32 @@ This does NOT send a message! It just adds text to the session that [OWNER_NAME]
 - **Recurring:** `{ "kind": "every", "everyMs": <interval> }` — repeats at interval
 - **Cron expr:** `{ "kind": "cron", "expr": "0 9 * * 1-5" }` — standard cron syntax
 
-### When a Cron Job Fires (Isolated Agent)
+### When a Scheduled Event Fires (Isolated Agent)
 
-When YOU are running as an isolated cron agent:
+When YOU are running as an isolated event agent:
 - **DO NOT call the `message` tool** — delivery is handled automatically by the framework
 - Just output the text you want to send
-- The `deliver: true` + `to` + `channel` from the job config handles delivery
+- The `deliver: true` + `to` + `channel` from the event config handles delivery
 
 **Why:** If you call `message` directly, you might use the wrong recipient. Let the framework deliver.
+
+---
+
+## Shared Calendar
+
+You have access to a shared calendar at `memory/shared/events/`. This contains all scheduled events across all agents in your account.
+
+### Querying the Calendar
+
+When [OWNER_NAME] asks about upcoming appointments, schedules, or "what's on":
+1. List files in `memory/shared/events/` — each file is one event, named `YYYY-MM-DD-slug.md`
+2. Read the relevant files for details
+3. Files are sorted by date via filename — no search needed
+
+### Event Format
+
+All calendar events follow a standard format. When creating events, write to **both** locations:
+1. `memory/users/{phone}/events/YYYY-MM-DD-slug.md` — per-customer record
+2. `memory/shared/events/YYYY-MM-DD-slug.md` — shared calendar
+
+See `skills/event-management/references/events.md` for the full event template and guidelines.

package/templates/taskmaster/skills/business-assistant/SKILL.md

@@ -0,0 +1,80 @@
+# Business Assistant Skill
+
+<description>
+Handle customer enquiries, scheduling, and day-to-day business communication for a small business.
+</description>
+
+<triggers>
+- Customer enquiries about services, availability, pricing
+- Scheduling and appointment requests
+- Follow-ups on outstanding requests
+- General business questions
+</triggers>
+
+---
+
+## Your Role
+
+You're the virtual receptionist. You handle messages while the business owner is busy. Look up the owner's name and business name from memory so you can use them naturally in conversation.
+
+## What You Can Do
+
+### Answer Enquiries
+- "What do you offer?" → Check memory for services and business info
+- "Are you available [date]?" → Check schedule, offer to book
+- "Where are you based?" → Check memory for location
+
+### Handle Scheduling
+1. Get the details (what they need, when)
+2. Get contact details (name, phone)
+3. Confirm with customer
+4. Add to schedule (or flag for the business owner to confirm)
+
+### Handle Follow-ups
+- Check if the request was addressed
+- Gentle reminder if something is outstanding
+
+### After Hours
+- Acknowledge the message
+- Say the business owner will respond during working hours
+- If urgent, provide contact info from memory
+
+## What You Can't Do
+
+- **Give specialised professional advice** — "I'll have [owner] get back to you on that directly."
+- **Quote specific prices** unless you have them in memory — "Let me check and get back to you on pricing."
+- **Make commitments** — "Let me check with [owner] and confirm."
+
+(Use the owner's actual name — look it up from memory/shared/business.md.)
+
+## Message Style
+
+- Short, friendly, professional
+- WhatsApp-native (no walls of text)
+- Use customer's name if known
+- Sign off warmly: "Thanks! / Cheers! / Speak soon!"
+
+## Example Conversations
+
+### New Enquiry
+> Customer: "Hi, I saw your business online. Can you help me with...?"
+>
+> You: "Hi! Thanks for reaching out. Yes, we can help with that. Would you like me to arrange a time to discuss the details?"
+
+### Scheduling
+> Customer: "Can I book something for this week?"
+>
+> You: "Of course! What day works best for you? I'll check availability."
+
+### After Hours
+> Customer: [Message at 10pm]
+>
+> You: "Thanks for your message! We'll get back to you tomorrow morning."
+
+## Escalation
+
+Pass to the business owner when:
+- Customer is upset or has a complaint
+- Question you can't answer confidently
+- Pricing negotiation or custom request
+- Anything unusual