machinaos 0.0.12 → 0.0.13

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

@@ -1,176 +0,0 @@
----
-name: code-skill
-description: Execute Python or JavaScript code for calculations, data processing, and automation. Use when user needs to run code, do calculations, or process data.
-allowed-tools: python_code javascript_code
-metadata:
-  author: machina
-  version: "3.0"
-  category: code
-  icon: "💻"
-  color: "#F59E0B"
----
-
-# Code Execution
-
-This skill enables you to execute Python and JavaScript code for various tasks using the `python_code` and `javascript_code` tools.
-
-## Tool: python_code
-
-Execute Python code for calculations, data processing, and automation.
-
-### Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `code` | string | Yes | Python code to execute. Set `output` variable with result. Use `print()` for console output. |
-
-### Available Libraries
-- Standard library: `math`, `json`, `datetime`, `timedelta`, `re`, `random`
-- Collections: `Counter`, `defaultdict`
-- All built-in functions
-
-### Variables Available
-- `input_data` - Data from connected workflow nodes (dict)
-- `output` - Set this variable to return a result
-
-### Returns
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `success` | boolean | Whether execution succeeded |
-| `result` | any | Value of `output` variable if set |
-| `output` | string | Captured print() statements |
-| `error` | string | Error message if execution failed |
-
-### Example Usage
-```python
-# Calculate with data
-data = input_data.get("numbers", [1, 2, 3])
-total = sum(data)
-average = total / len(data)
-print(f"Total: {total}, Average: {average}")
-output = {"total": total, "average": average}
-```
-
----
-
-## Tool: javascript_code
-
-Execute JavaScript code for calculations, data processing, and JSON manipulation.
-
-### Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `code` | string | Yes | JavaScript code to execute. Set `output` variable with result. Use `console.log()` for output. |
-
-### Variables Available
-- `input_data` - Data from connected workflow nodes (object)
-- `output` - Set this variable to return a result
-
-### Returns
-
-| Field | Type | Description |
-|-------|------|-------------|
-| `success` | boolean | Whether execution succeeded |
-| `result` | any | Value of `output` variable if set |
-| `output` | string | Captured console.log() statements |
-| `error` | string | Error message if execution failed |
-
-### Example Usage
-```javascript
-// Process JSON data
-const data = input_data.numbers || [1, 2, 3];
-const total = data.reduce((a, b) => a + b, 0);
-const average = total / data.length;
-console.log(`Total: ${total}, Average: ${average}`);
-output = { total, average };
-```
-
----
-
-## Examples
-
-### Calculate a tip (Python)
-**User**: "Calculate 15% tip on $85.50"
-
-**Tool Call** (python_code):
-```json
-{
-  "code": "bill = 85.50\ntip_percent = 15\ntip = bill * (tip_percent / 100)\ntotal = bill + tip\nprint(f\"Tip: ${tip:.2f}\")\nprint(f\"Total: ${total:.2f}\")\noutput = {\"tip\": tip, \"total\": total}"
-}
-```
-
-### Generate random numbers (Python)
-**User**: "Generate 5 random numbers between 1 and 100"
-
-**Tool Call** (python_code):
-```json
-{
-  "code": "import random\nnumbers = [random.randint(1, 100) for _ in range(5)]\nprint(f\"Random numbers: {numbers}\")\noutput = numbers"
-}
-```
-
-### Process JSON data (JavaScript)
-**User**: "Sum all the values in this object"
-
-**Tool Call** (javascript_code):
-```json
-{
-  "code": "const values = Object.values(input_data);\nconst sum = values.reduce((a, b) => a + b, 0);\nconsole.log(`Sum: ${sum}`);\noutput = sum;"
-}
-```
-
-### Date calculations (Python)
-**User**: "What date is 30 days from now?"
-
-**Tool Call** (python_code):
-```json
-{
-  "code": "from datetime import datetime, timedelta\ntoday = datetime.now()\nfuture = today + timedelta(days=30)\nresult = future.strftime('%Y-%m-%d')\nprint(f\"30 days from now: {result}\")\noutput = result"
-}
-```
-
-### Array manipulation (JavaScript)
-**User**: "Filter this array to only even numbers"
-
-**Tool Call** (javascript_code):
-```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;"
-}
-```
-
----
-
-## When to Use Each Tool
-
-| Use Case | Recommended Tool |
-|----------|------------------|
-| Math calculations | `python_code` |
-| Date/time operations | `python_code` |
-| Data analysis | `python_code` |
-| Random number generation | `python_code` |
-| JSON manipulation | `javascript_code` |
-| Array operations | Either |
-| String processing | Either |
-
----
-
-## Security Guidelines
-
-1. **No file system access** outside designated directories
-2. **No network requests** from code (use http-skill instead)
-3. **No system commands** or shell access
-4. **Limited execution time** (timeout configurable, default 30 seconds)
-5. **No sensitive data** in code outputs
-
-## Best Practices
-
-1. Keep code simple and focused on one task
-2. Use descriptive variable names
-3. Always set the `output` variable with your result
-4. Use `print()` / `console.log()` for debugging
-5. Handle potential errors gracefully
-6. Prefer Python for math, dates, and data processing
-7. Prefer JavaScript for JSON manipulation

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

@@ -1,163 +0,0 @@
----
-name: http-skill
-description: Make HTTP requests to external APIs and web services. Use when user needs to fetch data from URLs, call APIs, or interact with web services.
-allowed-tools: http-request
-metadata:
-  author: machina
-  version: "2.0"
-  category: integration
-  icon: "🌐"
-  color: "#EF4444"
----
-
-# HTTP Requests
-
-This skill enables you to make HTTP requests to external APIs and web services.
-
-## Capabilities
-
-- Make GET, POST, PUT, DELETE, PATCH requests
-- Send JSON payloads in request body
-- Set custom headers (authentication, content-type, etc.)
-- Handle API responses (JSON and text)
-
-## Tool Reference
-
-### http-request
-
-Make an HTTP request to a URL.
-
-**Parameters:**
-| Parameter | Type | Required | Default | Description |
-|-----------|------|----------|---------|-------------|
-| `url` | string | Yes | - | Full URL to request (e.g., `https://api.example.com/data`) |
-| `method` | string | No | `GET` | HTTP method: `GET`, `POST`, `PUT`, `DELETE`, `PATCH` |
-| `body` | object | No | null | Request body as JSON object (for POST/PUT/PATCH) |
-| `headers` | object | No | null | Custom headers as key-value pairs |
-
-**Returns:**
-| Field | Type | Description |
-|-------|------|-------------|
-| `status` | number | HTTP status code (200, 404, 500, etc.) |
-| `data` | any | Response body (parsed JSON or text) |
-| `headers` | object | Response headers |
-| `url` | string | Final URL (may differ if redirected) |
-| `method` | string | HTTP method used |
-
-## Common Use Cases
-
-### Fetching Data (GET)
-```json
-{
-  "url": "https://api.example.com/users/123",
-  "method": "GET"
-}
-```
-
-### Creating Resources (POST)
-```json
-{
-  "url": "https://api.example.com/users",
-  "method": "POST",
-  "body": {"name": "John", "email": "john@example.com"},
-  "headers": {"Content-Type": "application/json"}
-}
-```
-
-### Updating Resources (PUT/PATCH)
-```json
-{
-  "url": "https://api.example.com/users/123",
-  "method": "PUT",
-  "body": {"name": "John Updated"}
-}
-```
-
-### Deleting Resources (DELETE)
-```json
-{
-  "url": "https://api.example.com/users/123",
-  "method": "DELETE"
-}
-```
-
-### With Authentication
-```json
-{
-  "url": "https://api.example.com/protected",
-  "method": "GET",
-  "headers": {
-    "Authorization": "Bearer your-api-token",
-    "X-API-Key": "your-api-key"
-  }
-}
-```
-
-## Examples
-
-**User**: "Get the current Bitcoin price"
-**Action**: Use http-request with:
-```json
-{
-  "url": "https://api.coindesk.com/v1/bpi/currentprice.json",
-  "method": "GET"
-}
-```
-
-**User**: "Post this data to my webhook"
-**Action**: Use http-request with:
-```json
-{
-  "url": "https://webhook.example.com/endpoint",
-  "method": "POST",
-  "body": {"event": "user_action", "data": "..."},
-  "headers": {"Content-Type": "application/json"}
-}
-```
-
-**User**: "Check if example.com is up"
-**Action**: Use http-request with:
-```json
-{
-  "url": "https://example.com",
-  "method": "GET"
-}
-```
-Then check if status is 200.
-
-**User**: "Get weather for New York"
-**Action**: Use http-request with:
-```json
-{
-  "url": "https://api.openweathermap.org/data/2.5/weather?q=New York&appid=YOUR_KEY",
-  "method": "GET"
-}
-```
-
-## Security Guidelines
-
-1. **Never expose API keys** in responses to the user
-2. **Validate URLs** - only request from trusted domains
-3. **Don't make requests** to internal/private networks (localhost, 192.168.x.x, 10.x.x.x)
-4. **Respect rate limits** of external services
-5. **Handle errors gracefully** and inform the user clearly
-6. **Don't store sensitive data** from API responses
-
-## Error Handling
-
-Common HTTP status codes and what they mean:
-
-| Status | Meaning | Action |
-|--------|---------|--------|
-| 200-299 | Success | Process the response data |
-| 400 | Bad Request | Check request parameters |
-| 401 | Unauthorized | Check API key/authentication |
-| 403 | Forbidden | Access denied, may need different permissions |
-| 404 | Not Found | Check URL path |
-| 429 | Too Many Requests | Rate limited, wait before retrying |
-| 500-599 | Server Error | External service issue, try again later |
-
-When an error occurs, inform the user about:
-- What was attempted
-- What went wrong (status code and message)
-- Suggested next steps

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

@@ -1,172 +0,0 @@
----
-name: maps-skill
-description: Location services including geocoding, nearby places, and maps. Use when user asks about addresses, locations, places nearby, or wants to see a map.
-metadata:
-  author: machina
-  version: "3.0"
-  category: location
-  icon: "🗺️"
-  color: "#4285F4"
----
-
-# Location Services
-
-This skill provides context for location-based capabilities using Google Maps services.
-
-## How It Works
-
-This skill provides instructions and context. To execute location actions, connect the appropriate **tool nodes** to the Zeenie's `input-tools` handle:
-
-- **Add Locations** node - Geocode addresses to coordinates or reverse geocode
-- **Show Nearby Places** node - Search for nearby places
-
-## add_locations Tool (Geocoding)
-
-Convert addresses to coordinates or coordinates to addresses.
-
-### Schema Fields
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| service_type | string | Yes | "geocode" (address to coordinates) or "reverse_geocode" (coordinates to address) |
-| address | string | If geocode | Address to geocode (e.g., "1600 Amphitheatre Parkway, Mountain View, CA") |
-| lat | float | If reverse_geocode | Latitude coordinate |
-| lng | float | If reverse_geocode | Longitude coordinate |
-
-### Examples
-
-**Geocode address:**
-```json
-{
-  "service_type": "geocode",
-  "address": "Eiffel Tower, Paris"
-}
-```
-
-**Reverse geocode:**
-```json
-{
-  "service_type": "reverse_geocode",
-  "lat": 48.8584,
-  "lng": 2.2945
-}
-```
-
-### Response Format
-
-```json
-{
-  "success": true,
-  "service_type": "geocoding",
-  "input": {"address": "Eiffel Tower, Paris"},
-  "results": [
-    {
-      "formatted_address": "Champ de Mars, 5 Av. Anatole France, 75007 Paris, France",
-      "geometry": {
-        "location": {"lat": 48.8583701, "lng": 2.2944813}
-      },
-      "address_components": [...]
-    }
-  ],
-  "status": "OK"
-}
-```
-
-## show_nearby_places Tool
-
-Search for places near a location.
-
-### Schema Fields
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| lat | float | Yes | Center latitude for search |
-| lng | float | Yes | Center longitude for search |
-| radius | int | No | Search radius in meters (default: 500, max: 50000) |
-| type | string | No | Place type (default: "restaurant") |
-| keyword | string | No | Optional keyword to filter results |
-
-### Examples
-
-**Find nearby restaurants:**
-```json
-{
-  "lat": 40.7484,
-  "lng": -73.9857,
-  "radius": 500,
-  "type": "restaurant"
-}
-```
-
-**Find coffee shops near a location:**
-```json
-{
-  "lat": 37.7749,
-  "lng": -122.4194,
-  "type": "cafe",
-  "keyword": "starbucks"
-}
-```
-
-### Response Format
-
-```json
-{
-  "success": true,
-  "type": "restaurant",
-  "search_parameters": {
-    "location": {"lat": 40.7484, "lng": -73.9857},
-    "radius": 500,
-    "type": "restaurant"
-  },
-  "results": [
-    {
-      "name": "Example Restaurant",
-      "vicinity": "123 Main St",
-      "rating": 4.5,
-      "user_ratings_total": 150,
-      "price_level": 2,
-      "geometry": {
-        "location": {"lat": 40.7485, "lng": -73.9860}
-      },
-      "types": ["restaurant", "food"],
-      "opening_hours": {"open_now": true}
-    }
-  ],
-  "total_results": 10,
-  "status": "OK"
-}
-```
-
-## Place Types
-
-Common place types for nearby search:
-- Food: restaurant, cafe, bakery, bar, meal_takeaway
-- Shopping: store, supermarket, shopping_mall, clothing_store
-- Services: bank, atm, gas_station, pharmacy, post_office
-- Health: hospital, doctor, dentist, pharmacy
-- Transport: bus_station, train_station, airport, taxi_stand
-- Entertainment: movie_theater, gym, park, museum, zoo
-
-## Common Workflows
-
-### Find nearby places by address
-1. Use `add_locations` with service_type="geocode" to get coordinates
-2. Use `show_nearby_places` with the returned lat/lng
-
-### Get address from coordinates
-1. Use `add_locations` with service_type="reverse_geocode"
-
-## Response Guidelines
-
-When presenting location results:
-1. List the top results with name, rating, and address
-2. Include distance if available
-3. Mention if places are currently open
-4. Offer to search for different types or expand radius
-
-## Setup Requirements
-
-1. Connect this skill to Zeenie's `input-skill` handle
-2. Connect location tool nodes to Zeenie's `input-tools` handle
-3. Ensure Google Maps API key is configured in credentials

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

@@ -1,86 +0,0 @@
----
-name: scheduler-skill
-description: Schedule tasks and set timers. Use when user wants to schedule something, set a reminder, create a recurring task, or use cron expressions.
-metadata:
-  author: machina
-  version: "2.0"
-  category: automation
-  icon: "⏰"
-  color: "#10B981"
----
-
-# Task Scheduling
-
-This skill provides context for scheduling tasks, setting timers, and creating recurring jobs.
-
-## How It Works
-
-This skill provides instructions and context. Scheduling is handled through workflow deployment:
-
-- **Cron Scheduler** trigger node - Recurring schedules using cron expressions
-- **Timer** trigger node - One-time delayed execution
-- **Workflow Trigger** node - Manual workflow execution
-
-## Capabilities
-
-When used with workflow triggers:
-- Create one-time timers
-- Set up recurring schedules with cron expressions
-- Deploy workflows that run on schedule
-
-## Cron Expression Format
-
-```
-* * * * *
-| | | | |
-| | | | +-- Day of week (0-7, Sun=0 or 7)
-| | | +---- Month (1-12)
-| | +------ Day of month (1-31)
-| +-------- Hour (0-23)
-+---------- Minute (0-59)
-```
-
-### Common Patterns
-
-| Pattern | Description |
-|---------|-------------|
-| `0 9 * * *` | Every day at 9:00 AM |
-| `0 9 * * 1-5` | Weekdays at 9:00 AM |
-| `*/15 * * * *` | Every 15 minutes |
-| `0 0 1 * *` | First day of each month |
-| `0 8,12,18 * * *` | At 8am, noon, and 6pm |
-
-## Example Interactions
-
-**User**: "Remind me in 30 minutes"
-- This requires setting up a Timer trigger workflow
-- Inform user: "I can help you create a scheduled workflow. Set up a Timer trigger node with 30 minute delay."
-
-**User**: "Send a daily report at 9am"
-- This requires a Cron Scheduler workflow
-- Inform user: "Create a workflow with Cron Scheduler trigger using expression '0 9 * * *'"
-
-**User**: "Check for updates every hour"
-- This requires a Cron Scheduler workflow
-- Inform user: "Create a workflow with Cron Scheduler trigger using expression '0 * * * *'"
-
-## Workflow-Based Scheduling
-
-In this system, scheduling is achieved through:
-
-1. **Trigger Nodes**: Cron Scheduler or Timer nodes start workflows
-2. **Workflow Deployment**: Deploy the workflow to activate the schedule
-3. **Cancel**: Undeploy the workflow to cancel the schedule
-
-## Best Practices
-
-1. Explain that schedules require workflow deployment
-2. Provide the cron expression for the user's request
-3. Confirm timezone considerations for time-sensitive tasks
-4. Help users understand workflow-based scheduling model
-
-## Limitations
-
-- This skill provides guidance only
-- Actual scheduling requires workflow creation and deployment
-- Cannot directly create/cancel schedules via chat commands