machinaos 0.0.12 → 0.0.13

package/server/skills/android_agent/screen-control-skill/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: screen-control-skill
+description: Control Android screen - brightness, wake screen, auto-brightness toggle, and screen timeout settings.
+allowed-tools: screen_control_automation
+metadata:
+  author: machina
+  version: "1.0"
+  category: android
+  icon: "💡"
+  color: "#EAB308"
+---
+
+# Screen Control Tool
+
+Control screen settings on Android device.
+
+## How It Works
+
+This skill provides instructions for the **Screen Control Automation** tool node. Connect the **Screen Control Automation** node to Zeenie's `input-tools` handle to enable screen control.
+
+## screen_control Tool
+
+Control screen brightness and display settings.
+
+### Schema Fields
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| action | string | Yes | Action to perform (see below) |
+| parameters | object | No | Additional parameters for set actions |
+
+### Actions
+
+| Action | Description |
+|--------|-------------|
+| `status` | Get current screen settings |
+| `set_brightness` | Set screen brightness level |
+| `wake` | Wake the screen |
+| `auto_brightness_on` | Enable auto-brightness |
+| `auto_brightness_off` | Disable auto-brightness |
+
+### Examples
+
+**Get screen status:**
+```json
+{
+  "action": "status"
+}
+```
+
+**Set brightness to 50%:**
+```json
+{
+  "action": "set_brightness",
+  "parameters": {
+    "level": 50
+  }
+}
+```
+
+**Wake the screen:**
+```json
+{
+  "action": "wake"
+}
+```
+
+**Enable auto-brightness:**
+```json
+{
+  "action": "auto_brightness_on"
+}
+```
+
+**Disable auto-brightness:**
+```json
+{
+  "action": "auto_brightness_off"
+}
+```
+
+### Response Formats
+
+**Status response:**
+```json
+{
+  "success": true,
+  "service": "screen_control",
+  "action": "status",
+  "data": {
+    "brightness": 75,
+    "auto_brightness": true,
+    "screen_on": true,
+    "screen_timeout": 30000
+  }
+}
+```
+
+**Set brightness response:**
+```json
+{
+  "success": true,
+  "service": "screen_control",
+  "action": "set_brightness",
+  "data": {
+    "previous_brightness": 100,
+    "new_brightness": 50
+  }
+}
+```
+
+### Response Fields
+
+| Field | Type | Description |
+|-------|------|-------------|
+| brightness | int | Current brightness (0-100) |
+| auto_brightness | boolean | Auto-brightness enabled |
+| screen_on | boolean | Screen is currently on |
+| screen_timeout | int | Timeout in milliseconds |
+
+## Use Cases
+
+| Use Case | Action | Description |
+|----------|--------|-------------|
+| Check display | status | Get current settings |
+| Lower brightness | set_brightness | Reduce for battery/eyes |
+| Wake device | wake | Turn on screen |
+| Enable adaptive | auto_brightness_on | Let system adjust |
+| Fixed brightness | auto_brightness_off | Manual control |
+
+## Common Workflows
+
+### Battery saving
+
+1. Disable auto-brightness
+2. Set brightness to 30%
+3. Reduce screen timeout
+
+### Night mode
+
+1. Disable auto-brightness
+2. Set brightness to 10-20%
+3. Enable blue light filter (if available)
+
+### Presentation mode
+
+1. Disable auto-brightness
+2. Set brightness to 100%
+3. Increase screen timeout
+
+## Brightness Guidelines
+
+| Level | Use Case |
+|-------|----------|
+| 0-20% | Night/dark room |
+| 20-50% | Indoor use |
+| 50-80% | Normal use |
+| 80-100% | Bright conditions/outdoor |
+
+## Setup Requirements
+
+1. Connect the **Screen Control Automation** node to Zeenie's `input-tools` handle
+2. Android device must be paired
+3. System settings permission may be required

package/server/skills/android_agent/wifi-skill/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: wifi-skill
+description: Control Android WiFi - enable, disable, get status, scan for networks, and get current connection info.
+allowed-tools: wifi_automation
+metadata:
+  author: machina
+  version: "1.0"
+  category: android
+  icon: "📶"
+  color: "#3B82F6"
+---
+
+# WiFi Automation Tool
+
+Control WiFi on Android devices.
+
+## How It Works
+
+This skill provides instructions for the **WiFi Automation** tool node. Connect the **WiFi Automation** node to Zeenie's `input-tools` handle to enable WiFi control.
+
+## wifi_automation Tool
+
+Control WiFi settings and get network information.
+
+### Schema Fields
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| action | string | Yes | Action to perform (see below) |
+| parameters | object | No | Additional parameters for certain actions |
+
+### Actions
+
+| Action | Description | Parameters |
+|--------|-------------|------------|
+| `status` | Get WiFi status and connection info | None |
+| `enable` | Turn WiFi on | None |
+| `disable` | Turn WiFi off | None |
+| `scan` | Scan for available networks | None |
+
+### Examples
+
+**Get WiFi status:**
+```json
+{
+  "action": "status"
+}
+```
+
+**Enable WiFi:**
+```json
+{
+  "action": "enable"
+}
+```
+
+**Disable WiFi:**
+```json
+{
+  "action": "disable"
+}
+```
+
+**Scan for networks:**
+```json
+{
+  "action": "scan"
+}
+```
+
+### Response Formats
+
+**Status response:**
+```json
+{
+  "success": true,
+  "service": "wifi_automation",
+  "action": "status",
+  "data": {
+    "enabled": true,
+    "connected": true,
+    "ssid": "MyHomeNetwork",
+    "bssid": "aa:bb:cc:dd:ee:ff",
+    "ip_address": "192.168.1.100",
+    "link_speed": 72,
+    "rssi": -45,
+    "frequency": 2437
+  }
+}
+```
+
+**Scan response:**
+```json
+{
+  "success": true,
+  "service": "wifi_automation",
+  "action": "scan",
+  "data": {
+    "networks": [
+      {
+        "ssid": "MyHomeNetwork",
+        "bssid": "aa:bb:cc:dd:ee:ff",
+        "rssi": -45,
+        "frequency": 2437,
+        "security": "WPA2"
+      },
+      {
+        "ssid": "Neighbor_WiFi",
+        "bssid": "11:22:33:44:55:66",
+        "rssi": -70,
+        "frequency": 5180,
+        "security": "WPA3"
+      }
+    ]
+  }
+}
+```
+
+**Enable/Disable response:**
+```json
+{
+  "success": true,
+  "service": "wifi_automation",
+  "action": "enable",
+  "data": {
+    "message": "WiFi enabled successfully"
+  }
+}
+```
+
+### Response Fields
+
+| Field | Description |
+|-------|-------------|
+| enabled | WiFi radio is on |
+| connected | Connected to a network |
+| ssid | Network name |
+| bssid | Access point MAC address |
+| ip_address | Device IP on network |
+| link_speed | Connection speed in Mbps |
+| rssi | Signal strength (dBm, closer to 0 is stronger) |
+| frequency | Channel frequency in MHz |
+
+## Use Cases
+
+| Use Case | Action | Description |
+|----------|--------|-------------|
+| Check connection | status | Verify WiFi is connected |
+| Toggle WiFi | enable/disable | Control WiFi radio |
+| Find networks | scan | List available networks |
+| Signal strength | status | Check connection quality |
+
+## Common Workflows
+
+### Auto-connect workflow
+
+1. Check WiFi status
+2. If not enabled, enable it
+3. Scan for networks
+4. Report available options
+
+### Battery saving
+
+1. Check if on mobile data
+2. If not using WiFi, disable it
+3. Re-enable when needed
+
+## Signal Strength Guide
+
+| RSSI (dBm) | Quality |
+|------------|---------|
+| > -50 | Excellent |
+| -50 to -60 | Good |
+| -60 to -70 | Fair |
+| -70 to -80 | Weak |
+| < -80 | Poor |
+
+## Setup Requirements
+
+1. Connect the **WiFi Automation** node to Zeenie's `input-tools` handle
+2. Android device must be paired
+3. Location permission may be required for scanning

package/server/skills/assistant/subagent-skill/SKILL.md

@@ -3,7 +3,7 @@ name: subagent-skill
 description: Manage sub-agent delegation, handle task completion events, and coordinate multi-agent workflows.
 metadata:
   author: machina
-  version: "1.0"
+  version: "2.0"
   category: assistant
   icon: "🤖"
   color: "#8B5CF6"
@@ -13,6 +13,30 @@ metadata:
 
 You are a parent agent that can delegate tasks to specialized sub-agents. This skill helps you understand, delegate to, and handle results from sub-agents effectively.
 
+## CRITICAL: Always Check Sub-Agents First
+
+**NEVER say "I don't have that tool" or "I can't do that" without first checking your connected sub-agents.**
+
+When a user requests something you don't have a direct tool for:
+
+1. **Check your connected sub-agents** - Look at what agents are available in your tools
+2. **Delegate to the appropriate sub-agent** - They have their own tools and capabilities
+3. **Only say you can't** if NO sub-agent can handle it
+
+**Wrong approach:**
+```
+User: "Check my phone battery"
+You: "I don't have access to Android tools, so I can't check your battery."
+```
+
+**Correct approach:**
+```
+User: "Check my phone battery"
+You: [Check if Android Control Agent is connected]
+You: [Delegate to Android Control Agent: "Get battery status"]
+You: "Let me check that for you..." [waits for result]
+```
+
 ## Available Sub-Agent Types
 
 You can delegate tasks to these specialized agents (when connected to your tools):
@@ -42,6 +66,26 @@ You can delegate tasks to these specialized agents (when connected to your tools
 | **Payments Agent** | 💳 | Payment processing | Payment workflows, invoices, financial operations |
 | **Consumer Agent** | 🛒 | Consumer support | Customer service, product recommendations, order management |
 
+## How to Check Sub-Agent Capabilities
+
+Before responding "I can't do that":
+
+1. **List your available tools** - Sub-agents appear as delegation tools
+2. **Match the request to an agent specialty** - Use the table above
+3. **Delegate if a match exists** - The sub-agent has its own tools
+4. **Only decline if truly impossible** - No matching agent connected
+
+### Capability Matching Examples
+
+| User Request | Check For | Delegate To |
+|--------------|-----------|-------------|
+| "Check my battery" | Android Control Agent | `delegate_to_android_agent` |
+| "Send a WhatsApp" | Social Media Agent | `delegate_to_social_agent` |
+| "Calculate this" | Coding Agent | `delegate_to_coding_agent` |
+| "Find restaurants nearby" | Travel Agent | `delegate_to_travel_agent` |
+| "Make an HTTP request" | Web Control Agent | `delegate_to_web_agent` |
+| "Set a reminder" | Task Management Agent | `delegate_to_task_agent` |
+
 ## How Delegation Works
 
 ### Fire-and-Forget Pattern
@@ -60,15 +104,15 @@ When you delegate a task:
 ## Delegation Best Practices
 
 ### When to Delegate
-- Task requires specialized tools you don't have connected
+- User requests something outside your direct tools
+- Task requires specialized capabilities (Android, WhatsApp, code execution, etc.)
 - Task is time-consuming and can run in background
 - Task matches a sub-agent's specialty area
-- User explicitly asks for a specific capability
 
 ### When NOT to Delegate
-- Simple questions you can answer directly
-- Tasks that need immediate response in conversation
-- When you already have the required tools connected
+- Simple questions you can answer directly from knowledge
+- Tasks that need immediate response AND you have the direct tool
+- When the same task is already running (avoid duplicates)
 
 ### Delegation Format
 When delegating, provide clear instructions:
@@ -101,19 +145,6 @@ When a delegated task fails:
 **Example Response:**
 "I wasn't able to send the WhatsApp message because the contact wasn't found. Could you verify the phone number? Alternatively, I can try searching for the contact by name."
 
-## Task Tracking
-
-If you have the Task Manager tool connected, use it to:
-- **List tasks**: See all active and completed delegated tasks
-- **Check status**: Get details on a specific task
-- **Mark done**: Clean up completed task tracking
-
-### Checking Task Status
-Before re-delegating similar work:
-1. Use Task Manager to list recent tasks
-2. Check if the same task is already running
-3. Avoid duplicate delegations
-
 ## Multi-Agent Coordination
 
 ### Sequential Delegation
@@ -131,17 +162,17 @@ For independent tasks:
 
 ## Critical Rules
 
-1. **NEVER re-delegate after receiving a result** - Report it instead
-2. **NEVER retry failed tasks automatically** - Ask user first
-3. **ALWAYS acknowledge task completion** to the user
-4. **ALWAYS match task to agent specialty** for best results
-5. **When in doubt, ask the user** before taking action
+1. **ALWAYS check sub-agents before saying "I can't"** - They extend your capabilities
+2. **NEVER re-delegate after receiving a result** - Report it instead
+3. **NEVER retry failed tasks automatically** - Ask user first
+4. **ALWAYS acknowledge task completion** to the user
+5. **ALWAYS match task to agent specialty** for best results
 
 ## Error Handling
 
 | Error Type | Action |
 |------------|--------|
-| Agent not found | Check if agent is connected to your tools |
+| Agent not connected | Inform user which agent is needed and how to connect it |
 | Task timeout | Report to user, suggest retry |
 | Invalid parameters | Clarify requirements with user |
 | Agent error | Report error details, suggest alternatives |
@@ -151,6 +182,7 @@ For independent tasks:
 ### Battery Check Workflow
 ```
 User: "Check my phone battery"
+You: [See Android Control Agent in tools]
 You: Delegate to Android Control Agent with task "Get battery status"
 Agent: Returns {status: 'completed', result: 'Battery at 78%, charging'}
 You: "Your phone battery is at 78% and currently charging."
@@ -159,15 +191,15 @@ You: "Your phone battery is at 78% and currently charging."
 ### Message Sending Workflow
 ```
 User: "Send a WhatsApp to John saying I'll be late"
+You: [See Social Media Agent in tools]
 You: Delegate to Social Media Agent with message details
 Agent: Returns {status: 'completed', result: 'Message sent to John'}
 You: "Done! I've sent the message to John letting him know you'll be late."
 ```
 
-### Failed Task Workflow
+### No Agent Available
 ```
-User: "Run the Python script at /scripts/analyze.py"
-You: Delegate to Coding Agent
-Agent: Returns {status: 'error', error: 'File not found'}
-You: "I couldn't run that script - the file wasn't found at /scripts/analyze.py. Could you verify the path is correct?"
+User: "Check my phone battery"
+You: [No Android Control Agent in tools]
+You: "I don't have an Android Control Agent connected right now. To check your battery, please connect an Android Control Agent to my tools input, then ask again."
 ```

package/server/skills/coding_agent/javascript-skill/SKILL.md

@@ -0,0 +1,196 @@
+---
+name: javascript-skill
+description: Execute JavaScript code for calculations, data processing, and JSON manipulation. Full ES6+ support with Node.js runtime.
+allowed-tools: javascript_code
+metadata:
+  author: machina
+  version: "1.0"
+  category: code
+  icon: "📜"
+  color: "#F7DF1E"
+---
+
+# JavaScript Code Execution Tool
+
+Execute JavaScript code for calculations, data processing, and JSON manipulation.
+
+## How It Works
+
+This skill provides instructions for the **JavaScript Executor** tool node. Connect the **JavaScript Executor** node to Zeenie's `input-tools` handle to enable JavaScript code execution.
+
+## javascript_code Tool
+
+Execute JavaScript code and return results.
+
+### Schema Fields
+
+| Field | Type | Required | Description |
+|-------|------|----------|-------------|
+| code | string | Yes | JavaScript code to execute |
+
+### Available Features
+
+| Feature | Description |
+|---------|-------------|
+| ES6+ syntax | Arrow functions, destructuring, spread operator |
+| `JSON` | JSON.parse() and JSON.stringify() |
+| `Math` | Mathematical operations |
+| `Date` | Date and time manipulation |
+| `Array` methods | map, filter, reduce, sort, etc. |
+| `Object` methods | keys, values, entries, assign |
+| `String` methods | All standard string methods |
+
+### Built-in Variables
+
+| Variable | Description |
+|----------|-------------|
+| `input_data` | Data from connected workflow nodes (object) |
+| `output` | Set this to return a result |
+
+### Output Methods
+
+1. **Set `output` variable**: Returns structured data to the workflow
+2. **Use `console.log()`**: Captured as console output
+
+### Examples
+
+**Basic calculation:**
+```json
+{
+  "code": "const result = 25 * 4 + 10;\nconsole.log(`Result: ${result}`);\noutput = result;"
+}
+```
+
+**Array processing:**
+```json
+{
+  "code": "const numbers = input_data.numbers || [1, 2, 3, 4, 5];\nconst total = numbers.reduce((a, b) => a + b, 0);\nconst average = total / numbers.length;\nconsole.log(`Total: ${total}, Average: ${average}`);\noutput = { total, average };"
+}
+```
+
+**Filter array:**
+```json
+{
+  "code": "const numbers = input_data.numbers || [1, 2, 3, 4, 5, 6, 7, 8, 9, 10];\nconst evens = numbers.filter(n => n % 2 === 0);\nconsole.log(`Even numbers: ${evens}`);\noutput = evens;"
+}
+```
+
+**Transform data:**
+```json
+{
+  "code": "const users = input_data.users || [{name: 'John', age: 30}, {name: 'Jane', age: 25}];\nconst names = users.map(u => u.name);\nconsole.log(`Names: ${names.join(', ')}`);\noutput = names;"
+}
+```
+
+**JSON manipulation:**
+```json
+{
+  "code": "const data = { name: 'John', age: 30, city: 'NYC' };\nconst json = JSON.stringify(data, null, 2);\nconsole.log(json);\noutput = data;"
+}
+```
+
+**Object operations:**
+```json
+{
+  "code": "const obj = { a: 1, b: 2, c: 3 };\nconst keys = Object.keys(obj);\nconst values = Object.values(obj);\nconst sum = values.reduce((a, b) => a + b, 0);\nconsole.log(`Sum of values: ${sum}`);\noutput = { keys, values, sum };"
+}
+```
+
+**Date operations:**
+```json
+{
+  "code": "const now = new Date();\nconst tomorrow = new Date(now.getTime() + 24 * 60 * 60 * 1000);\nconst formatted = tomorrow.toISOString().split('T')[0];\nconsole.log(`Tomorrow: ${formatted}`);\noutput = formatted;"
+}
+```
+
+**Sort array:**
+```json
+{
+  "code": "const items = input_data.items || ['banana', 'apple', 'cherry'];\nconst sorted = [...items].sort();\nconsole.log(`Sorted: ${sorted}`);\noutput = sorted;"
+}
+```
+
+**String processing:**
+```json
+{
+  "code": "const text = 'Hello World, Hello JavaScript';\nconst words = text.split(' ');\nconst unique = [...new Set(words)];\nconsole.log(`Unique words: ${unique}`);\noutput = unique;"
+}
+```
+
+**Destructuring and spread:**
+```json
+{
+  "code": "const { name, age } = input_data.user || { name: 'John', age: 30 };\nconst profile = { name, age, active: true };\nconst extended = { ...profile, role: 'admin' };\nconsole.log(JSON.stringify(extended));\noutput = extended;"
+}
+```
+
+### Response Format
+
+**Success:**
+```json
+{
+  "success": true,
+  "result": { "total": 15, "average": 3 },
+  "output": "Total: 15, Average: 3"
+}
+```
+
+**Error:**
+```json
+{
+  "error": "ReferenceError: undefinedVar is not defined"
+}
+```
+
+## Use Cases
+
+| Use Case | Approach |
+|----------|----------|
+| Array manipulation | Use map, filter, reduce |
+| JSON processing | Use JSON.parse, JSON.stringify |
+| Object operations | Use Object.keys, values, entries |
+| String processing | Use split, join, replace |
+| Math calculations | Use Math methods |
+| Date operations | Use Date object |
+| Data transformation | Use spread and destructuring |
+
+## Guidelines
+
+1. **Always set `output`**: This returns data to the workflow
+2. **Use `console.log()` for debugging**: Output is captured and returned
+3. **Use ES6+ features**: Arrow functions, destructuring, spread
+4. **Handle undefined**: Use `|| defaultValue` pattern
+5. **Keep code focused**: One task per execution
+6. **No network access**: Use http-skill for web requests
+7. **Timeout**: Default 30 seconds max execution time
+
+## Security Restrictions
+
+- No network/fetch operations
+- No file system access (no require('fs'))
+- No child processes
+- Limited execution time (30 seconds)
+- Sandboxed environment
+
+## Common Patterns
+
+**Default values:**
+```javascript
+const data = input_data.value || 'default';
+```
+
+**Null-safe access:**
+```javascript
+const name = input_data?.user?.name || 'Unknown';
+```
+
+**Array to object:**
+```javascript
+const arr = [{id: 1, name: 'A'}, {id: 2, name: 'B'}];
+const obj = Object.fromEntries(arr.map(x => [x.id, x.name]));
+```
+
+## Setup Requirements
+
+1. Connect the **JavaScript Executor** node to Zeenie's `input-tools` handle
+2. Node.js must be installed on the server