machinaos 0.0.10 → 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

@@ -0,0 +1,205 @@
+---
+name: subagent-skill
+description: Manage sub-agent delegation, handle task completion events, and coordinate multi-agent workflows.
+metadata:
+  author: machina
+  version: "2.0"
+  category: assistant
+  icon: "🤖"
+  color: "#8B5CF6"
+---
+
+# Sub-Agent Management Skill
+
+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):
+
+### Domain-Specific Agents
+
+| Agent | Icon | Specialty | Best For |
+|-------|------|-----------|----------|
+| **Android Control Agent** | 📱 | Android device automation | Battery checks, WiFi control, app launching, location tracking, sensor data |
+| **Coding Agent** | 💻 | Code execution | Python/JavaScript execution, calculations, data processing |
+| **Web Control Agent** | 🌐 | Browser automation | Web scraping, HTTP requests, form filling |
+| **Social Media Agent** | 📱 | Social messaging | WhatsApp, Telegram, multi-platform messaging |
+| **Travel Agent** | ✈️ | Travel planning | Itineraries, location lookups, travel recommendations |
+
+### Task & Workflow Agents
+
+| Agent | Icon | Specialty | Best For |
+|-------|------|-----------|----------|
+| **Task Management Agent** | 📋 | Task automation | Scheduling, reminders, to-do management |
+| **Tool Agent** | 🔧 | Tool orchestration | Multi-tool workflows, complex task execution |
+| **Productivity Agent** | ⏰ | Productivity | Time management, note-taking, workflow automation |
+
+### Business Agents
+
+| Agent | Icon | Specialty | Best For |
+|-------|------|-----------|----------|
+| **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
+When you delegate a task:
+1. The sub-agent receives the task and starts working immediately
+2. You continue your conversation - delegation is non-blocking
+3. The sub-agent works independently with its own tools and memory
+4. When complete, a `task_completed` event is fired
+
+### What You Receive Back
+- **Task ID**: Unique identifier (e.g., `delegated_abc123_xyz`)
+- **Status**: `completed` or `error`
+- **Agent Name**: Which sub-agent completed the work
+- **Result/Error**: The outcome or error message
+
+## Delegation Best Practices
+
+### When to Delegate
+- 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
+
+### When NOT to Delegate
+- 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:
+```
+Task: [Clear description of what needs to be done]
+Context: [Any relevant background information]
+Expected Output: [What format/information you need back]
+```
+
+## Handling Task Completion
+
+### Successful Completion
+When a delegated task completes successfully:
+
+1. **DO NOT delegate again** - The task is finished
+2. **Extract key information** from the result
+3. **Report to the user** naturally and conversationally
+4. **Suggest next steps** if appropriate
+
+**Example Response:**
+"The Android agent has checked your battery status. Your device is at 78% with approximately 5 hours of usage remaining. Would you like me to enable power-saving mode?"
+
+### Failed Tasks
+When a delegated task fails:
+
+1. **DO NOT retry automatically** - Let the user decide
+2. **Explain what went wrong** clearly
+3. **Suggest alternatives** or troubleshooting steps
+
+**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."
+
+## Multi-Agent Coordination
+
+### Sequential Delegation
+For tasks requiring multiple steps:
+1. Delegate first task to appropriate agent
+2. Wait for completion via task trigger
+3. Use result to delegate next task
+4. Continue until workflow complete
+
+### Parallel Delegation
+For independent tasks:
+- Delegate multiple tasks to different agents
+- Each runs independently
+- Collect results as they complete
+
+## Critical Rules
+
+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 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 |
+
+## Example Workflows
+
+### 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."
+```
+
+### 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."
+```
+
+### No Agent Available
+```
+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."
+```