@rubytech/taskmaster 1.0.42 → 1.0.44

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

@@ -16,6 +16,7 @@ Explain that there's a second assistant — the **public agent** — that handle
 
 Ask conversationally, one thing at a time:
 - **Owner's name** (the person you're talking to)
+- **Phone number** (international format, e.g., +44 7504 472444)
 - **Business name**
 - **Location**
 - **Working hours**
@@ -23,20 +24,20 @@ Ask conversationally, one thing at a time:
 
 ## Step 4: Save Everything
 
-Update these files with the collected info:
+Use your `write` tool to update workspace files and `memory_write` for memory files. Never output shell commands or ask the admin to run terminal commands.
 
 **Your files (admin agent):**
-1. **IDENTITY.md** — Replace `[ASSISTANT_NAME]` with your chosen name
-2. **USER.md** — Fill in owner name, business name, location, working hours
+1. **IDENTITY.md** — Use `write` to replace `[ASSISTANT_NAME]` with your chosen name
+2. **USER.md** — Use `write` to fill in owner name, phone number, business name, location, working hours
 
 **Public agent files** (your counterpart at `../public/`):
-3. **`../public/IDENTITY.md`** — Replace `[ASSISTANT_NAME]` with the public agent's chosen name
+3. **`../public/IDENTITY.md`** — Use `write` to replace `[ASSISTANT_NAME]` with the public agent's chosen name
 
 **Shared memory** (accessible by both agents):
-4. **`memory/shared/business.md`** — Write the key business details: owner name, business name, location, working hours, and anything else relevant. **This is essential** — the public agent doesn't have USER.md and relies on shared memory to know the business owner's name, what the business does, and where it's based. Without this file, the public agent can't answer basic customer questions.
+4. **`memory/shared/business.md`** — Use `memory_write` to save the key business details: owner name, business name, location, working hours, and anything else relevant. **This is essential** — the public agent doesn't have USER.md and relies on shared memory to know the business owner's name, what the business does, and where it's based. Without this file, the public agent can't answer basic customer questions.
 
 **Website summary** (if a website was provided):
-5. **`memory/public/website.md`** — Use `document_read` to fetch the website and write a comprehensive summary covering: what the business does, services offered, pricing (if public), location and coverage area, contact details, opening hours, and any other customer-relevant information. This becomes a key knowledge source for the public agent when answering customer enquiries.
+5. **`memory/public/website.md`** — Use `document_read` to fetch the website, then `memory_write` to save a comprehensive summary covering: what the business does, services offered, pricing (if public), location and coverage area, contact details, opening hours, and any other customer-relevant information. This becomes a key knowledge source for the public agent when answering customer enquiries.
 
 All other files (SOUL.md, AGENTS.md, etc.) are already generic and reference USER.md or shared memory — no changes needed.
 
@@ -46,7 +47,18 @@ The paired device (self-chat) already has admin access. Ask if they want to add
 
 If yes, use the `authorize_admin` tool with their phone number (international format, e.g., +447504472444).
 
-## Step 6: Explain What's Next
+## Step 6: Help with API Keys
+
+Two free API keys unlock important capabilities. Offer to help the admin get them — use the browser to walk through signup and show screenshots so the user can follow along.
+
+- **Tavily** (web search) — load the `tavily` skill's `references/browser-setup.md` and follow its steps
+- **Google AI** (voice notes + video) — load the `google-ai` skill's `references/browser-setup.md` and follow its steps
+
+If the admin prefers to do it themselves, direct them to their Taskmaster setup page (API Keys section) and explain where to sign up: [app.tavily.com](https://app.tavily.com) for Tavily, [aistudio.google.com](https://aistudio.google.com) for Google AI.
+
+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.
+
+## Step 7: Explain What's Next
 
 Tell them:
 - They can message anytime to update business info
@@ -54,7 +66,7 @@ Tell them:
 - They (admin) get full access to configure everything
 - You'll learn their business as you go
 
-## Step 7: Delete This File
+## Step 8: Delete This File
 
 Once setup is complete, create a file called `.bootstrap-done` in this directory (empty content is fine), then delete this file. The `.bootstrap-done` marker prevents this onboarding from reappearing.
 

package/templates/taskmaster/.gitignore

@@ -0,0 +1 @@
+.DS_Store

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

@@ -47,7 +47,18 @@ The paired device (self-chat) already has admin access. Ask if they want to add
 
 If yes, use the `authorize_admin` tool with their phone number (international format, e.g., +447504472444).
 
-## Step 6: Explain What's Next
+## Step 6: Help with API Keys
+
+Two free API keys unlock important capabilities. Offer to help the admin get them — use the browser to walk through signup and show screenshots so the user can follow along.
+
+- **Tavily** (web search) — load the `tavily` skill's `references/browser-setup.md` and follow its steps
+- **Google AI** (voice notes + video) — load the `google-ai` skill's `references/browser-setup.md` and follow its steps
+
+If the admin prefers to do it themselves, direct them to their Taskmaster setup page (API Keys section) and explain where to sign up: [app.tavily.com](https://app.tavily.com) for Tavily, [aistudio.google.com](https://aistudio.google.com) for Google AI.
+
+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.
+
+## Step 7: Explain What's Next
 
 Tell them:
 - They can message anytime to update business info
@@ -55,7 +66,7 @@ Tell them:
 - They (admin) get full access to configure everything
 - You'll learn their business as you go
 
-## Step 7: Delete This File
+## Step 8: Delete This File
 
 Once setup is complete, create a file called `.bootstrap-done` in this directory (empty content is fine), then delete this file. The `.bootstrap-done` marker prevents this onboarding from reappearing.