@rubytech/taskmaster 1.5.1 → 1.5.3

package/taskmaster-docs/USER-GUIDE.md

@@ -768,18 +768,49 @@ You can also create events by asking the assistant in chat ("remind me every Mon
 
 ### Skills
 
-Skills are the specialised abilities your assistant has — like handling customer enquiries, creating quotes, or checking the weather. This tab shows which skills are installed, whether they're active, and if anything is missing (like an API key a skill needs).
+Skills are specialised abilities your assistant has — handling customer enquiries, creating quotes, checking the weather, generating images, and more. The Skills tab shows every skill that is installed, whether it is active, and flags anything that is missing (such as an API key a skill needs).
 
-Skills are labelled as **Preloaded** (built-in, always active) or **User** (created by you). You can:
+Each skill has a label:
 
-- **Tap any skill** to open a detail view showing its full instructions and reference files
-- **Enable/Disable** a user skill using the toggle button
-- **Edit** a user skill — loads its content so you can save an updated version
-- **Delete** a user skill (with confirmation)
+| Label | Meaning |
+|-------|---------|
+| **Preloaded** | Ships with the product. Always active. Cannot be disabled or deleted. |
+| **User** | Created by you (or by your assistant on your behalf). You can enable, disable, edit, or delete these. |
 
-**Creating new skills:** Ask your assistant to help you create a skill — it will walk you through the process step by step and prepare a draft. Once the draft is ready, open the **Drafts** button in the Skills tab to review, install, or delete pending drafts. You don't need to write skill files manually.
+#### Filtering the list
 
-Preloaded skills ship with the product and cannot be disabled or deleted.
+Use the **All / Preloaded / User** chip buttons at the top of the list to show only the type you're interested in.
+
+#### Viewing a skill
+
+Tap any skill to open its detail view. The detail view has tabs — one for the skill's main instructions (SKILL.md) and one for each reference file the skill uses. You can read through everything the skill does without leaving the page.
+
+#### Editing a user skill
+
+From the detail view, tap **Edit** to open the skill editor. The editor has the same tabs as the detail view (SKILL.md and any reference files), so you can edit each part independently. If you are already viewing a reference tab when you tap Edit, the editor opens directly on that reference.
+
+When you save an installed skill, the changes take effect immediately.
+
+#### Enable / Disable
+
+Toggle a user skill on or off with the switch on its card. A disabled skill stays installed but your assistant will not use it until you re-enable it.
+
+#### Delete
+
+Tap the delete icon on a user skill's card. You will be asked to confirm before the skill is removed.
+
+#### Drafts — creating new skills
+
+You do not need to write skill files by hand. Instead:
+
+1. **Ask your assistant** to create a skill — it walks you through the process step by step, asking what you need the skill to do.
+2. The assistant saves a **draft** using its built-in skill-builder.
+3. Open the **Drafts** button in the Skills tab to see all pending drafts.
+4. From the drafts list you can:
+   - **Edit** — review or modify the draft before installing it. The editor has the same tabs (SKILL.md and reference files) so you can fine-tune each part. Clicking **Save** saves your changes back to drafts — it does **not** install the skill.
+   - **Install** — activate the skill so your assistant starts using it.
+   - **Delete** — discard the draft.
+5. Once a draft is installed it moves out of drafts and into the main skills list as a **User** skill.
 
 ### Logs
 
@@ -994,6 +1025,19 @@ If the Pi checks pass but the control panel still doesn't load from another devi
 2. **Check you're on the same network** — mDNS only works between devices on the same WiFi/LAN. It won't work across VLANs or guest networks.
 3. **Contact support** with: what you changed (port/hostname), the output of `hostname`, `grep 127.0.1.1 /etc/hosts`, and `taskmaster daemon status`.
 
+### Static IP Address
+
+You don't need to assign a static IP address — Taskmaster uses a `.local` hostname that resolves automatically via mDNS, even if the IP changes after a reboot or DHCP renewal. You'll always find your control panel at the same `.local` address.
+
+That said, if your IT team prefers to pin devices to static IPs (common on managed business networks), they can do so via DHCP reservation on your router. They'll need the device's MAC address:
+
+1. SSH into the Pi (see "Enabling SSH" below)
+2. Run: `ip link show`
+3. Look for the `link/ether` line under the active interface (`eth0` for wired, `wlan0` for WiFi)
+4. Give that MAC address to your IT team to create a DHCP reservation
+
+This is entirely optional and is a network preference, not a Taskmaster requirement.
+
 ---
 
 ## Troubleshooting
@@ -1061,6 +1105,21 @@ The gateway is the software that runs your assistant. If it's showing red:
 3. Wait 30 seconds for it to come back online
 4. If still not working, try unplugging your Taskmaster device, waiting 10 seconds, and plugging it back in
 
+### Assistant not replying during an AI service outage?
+
+Occasionally, AI providers like Claude experience temporary outages or slowdowns. When this happens, Taskmaster automatically tries to get a reply from a different AI provider instead. Here's how it works:
+
+- **If you have backup providers configured** (e.g., a Google AI key or OpenAI key added on the Setup page), your assistant switches to those automatically. You don't need to do anything — replies keep coming, just from a different AI model behind the scenes.
+- **If you only have one provider** (e.g., Claude with no other API keys), messages sent during the outage won't get a reply. The customer's message is received but the assistant can't respond until the service recovers.
+- **Messages are not queued.** If a message arrives during an outage and all providers are down, it won't be retried automatically. The customer (or you) will need to send the message again once the service is back.
+- **Your conversation history is safe.** An outage doesn't corrupt or lose any previous conversations. Once the service recovers, everything picks up where it left off.
+
+**What you can do to stay protected:**
+
+1. **Add backup API keys** — Go to the **Setup** page, tap **API Keys**, and add keys for Google AI and/or OpenAI alongside your Claude connection. These act as automatic backups.
+2. **Check your logs** — If replies are failing, open **Advanced → Logs → Session Logs** and filter by "errors" to see what's happening.
+3. **Wait it out** — Most AI service outages resolve within minutes to hours. Your assistant will automatically use the primary provider again once it's back.
+
 ### "sudo: unable to resolve host taskmaster" warning?
 
 This harmless warning appears when the Pi's hostname isn't listed in `/etc/hosts`. Every `sudo` command still works — it's just a cosmetic message. To fix it, open a terminal on the Pi and run:

package/templates/customer/agents/admin/BOOTSTRAP.md

@@ -64,7 +64,7 @@ If the admin prefers to do it themselves later, they can manage API keys through
 
 These keys are optional — the assistant works without them. Don't pressure. If the admin wants to skip this and come back later, that's fine.
 
-If they need help with anything at all — setup, API keys, or general questions — suggest they reach out to **Dave at Taskmaster** via WhatsApp: [wa.me/447591215452](https://wa.me/447591215452).
+If they need help with anything at all — setup, API keys, or general questions — suggest they reach out to **Tuesday at Taskmaster** via WhatsApp: [wa.me/447591215452](https://wa.me/447591215452).
 
 ## Step 7: Rename the Account