machinaos 0.0.1

package/server/skills/assistant-personality/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: assistant-personality
+description: General AI assistant with helpful, harmless, and honest responses. Use as the default personality for conversations.
+metadata:
+  author: machina
+  version: "1.0"
+  category: assistant
+---
+
+# Assistant Personality
+
+You are a helpful, harmless, and honest AI assistant. Your goal is to assist users with their requests while being truthful and avoiding harmful content.
+
+## Core Principles
+
+1. **Helpfulness**: Provide clear, accurate, and useful information
+2. **Honesty**: Be truthful about your capabilities and limitations
+3. **Safety**: Avoid generating harmful, illegal, or unethical content
+
+## Communication Style
+
+- Be concise but thorough
+- Use clear, simple language
+- Break down complex topics into understandable parts
+- Ask clarifying questions when needed
+- Admit when you don't know something
+
+## Response Guidelines
+
+When responding to users:
+1. Understand the intent behind their question
+2. Provide the most helpful response possible
+3. Include relevant context or caveats
+4. Suggest follow-up questions if appropriate
+
+## Examples
+
+User: "What's the weather like?"
+Response: I don't have access to real-time weather data. However, I can help you find weather information if you tell me your location, or you can use a weather service like weather.com.
+
+User: "Help me write an email"
+Response: I'd be happy to help you write an email. Could you tell me:
+- Who is the recipient?
+- What is the purpose of the email?
+- What tone would you like (formal, casual, etc.)?

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

@@ -0,0 +1,140 @@
+---
+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: code-python code-javascript
+metadata:
+  author: machina
+  version: "1.0"
+  category: code
+---
+
+# Code Execution
+
+This skill enables you to execute Python and JavaScript code for various tasks.
+
+## Capabilities
+
+- Run Python code with full standard library
+- Execute JavaScript code
+- Perform complex calculations
+- Process and transform data
+- Generate outputs and visualizations
+
+## Tool Reference
+
+### code-python
+Execute Python code.
+
+Parameters:
+- `code` (required): Python code to execute
+- `input_data` (optional): Data to pass to the script (available as `input_data` variable)
+
+Returns:
+- output: Script output (print statements)
+- result: Return value if any
+- error: Error message if execution failed
+
+### code-javascript
+Execute JavaScript code.
+
+Parameters:
+- `code` (required): JavaScript code to execute
+- `input_data` (optional): Data to pass to the script
+
+Returns:
+- output: Console output
+- result: Return value
+- error: Error message if execution failed
+
+## Python Guidelines
+
+### Available Libraries
+- Standard library (math, json, datetime, re, etc.)
+- Data processing (collections, itertools)
+- String manipulation
+
+### Input Data Access
+```python
+# Access input data from previous nodes
+data = input_data  # Available as global variable
+print(f"Received: {data}")
+```
+
+### Output
+```python
+# Print for output display
+print("Hello, World!")
+
+# Return value for downstream nodes
+result = {"status": "success", "value": 42}
+```
+
+## JavaScript Guidelines
+
+### Input Data Access
+```javascript
+// Access input data from previous nodes
+const data = input_data;
+console.log(`Received: ${JSON.stringify(data)}`);
+```
+
+### Output
+```javascript
+// Console for output display
+console.log("Hello, World!");
+
+// Return value for downstream nodes
+return { status: "success", value: 42 };
+```
+
+## Examples
+
+**User**: "Calculate 15% tip on $85.50"
+**Action**: Use code-python with:
+```python
+bill = 85.50
+tip_percent = 15
+tip = bill * (tip_percent / 100)
+total = bill + tip
+print(f"Tip: ${tip:.2f}")
+print(f"Total: ${total:.2f}")
+```
+
+**User**: "Convert this JSON to CSV"
+**Action**: Use code-python with:
+```python
+import json
+import csv
+import io
+
+data = input_data  # JSON from previous node
+output = io.StringIO()
+writer = csv.DictWriter(output, fieldnames=data[0].keys())
+writer.writeheader()
+writer.writerows(data)
+print(output.getvalue())
+```
+
+**User**: "Generate 5 random numbers between 1 and 100"
+**Action**: Use code-python with:
+```python
+import random
+numbers = [random.randint(1, 100) for _ in range(5)]
+print(f"Random numbers: {numbers}")
+```
+
+## 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 after 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. Add comments for complex logic
+4. Validate input data before processing
+5. Handle potential errors gracefully

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

@@ -0,0 +1,161 @@
+---
+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
+---
+
+# 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/maps-skill/SKILL.md

@@ -0,0 +1,170 @@
+---
+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
+---
+
+# 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 Chat Agent'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 Chat Agent's `input-skill` handle
+2. Connect location tool nodes to Chat Agent's `input-tools` handle
+3. Ensure Google Maps API key is configured in credentials

package/server/skills/memory-skill/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: memory-skill
+description: Manage conversation memory. Use when user asks to remember something, recall information, view/edit conversation history, or manage short/long-term memory.
+allowed-tools: memory-save memory-get memory-clear memory-view memory-search
+metadata:
+  author: machina
+  version: "2.0"
+  category: memory
+---
+
+# Memory Management Skill
+
+This skill enables you to manage conversation memory using the SimpleMemory node's markdown-based storage system.
+
+## Memory Architecture
+
+### Short-Term Memory (Markdown)
+- Visible and editable in the SimpleMemory node's UI
+- Stored as markdown with timestamped entries
+- Window-based: keeps last N message pairs (configurable)
+- Format: `### **Human** (timestamp)` and `### **Assistant** (timestamp)`
+
+### Long-Term Memory (Vector DB)
+- Automatically archives messages that exceed the window
+- Semantic search for relevant past conversations
+- Enabled via `longTermEnabled` in SimpleMemory node
+
+## Capabilities
+
+1. **View History**: See recent conversation in markdown format
+2. **Save Notes**: Add explicit notes/memories to the conversation
+3. **Search Memory**: Find relevant past conversations semantically
+4. **Clear Memory**: Reset conversation history
+
+## When to Use
+
+**Save information when:**
+- User says "remember this" or "don't forget"
+- Important context is shared for future use
+- User wants to note something specific
+
+**Recall information when:**
+- User asks "do you remember..."
+- Context from earlier is needed
+- User references previous discussions
+
+**View history when:**
+- User wants to see conversation log
+- Debugging or reviewing past exchanges
+
+## Tool Reference
+
+### memory-save
+Add a note or memory entry to the conversation history.
+
+Parameters:
+- `content` (required): Information to remember
+- `role` (optional): "note" (default) or "context"
+
+Example:
+```json
+{
+  "content": "User's favorite color is blue",
+  "role": "note"
+}
+```
+
+### memory-get
+Get recent conversation history or search for specific content.
+
+Parameters:
+- `count` (optional): Number of recent messages (default: 10)
+- `search` (optional): Search term to find specific memories
+
+Example - Recent history:
+```json
+{
+  "count": 5
+}
+```
+
+Example - Search:
+```json
+{
+  "search": "favorite color"
+}
+```
+
+### memory-clear
+Clear conversation history.
+
+Parameters:
+- `confirm` (required): Must be true to clear
+
+Example:
+```json
+{
+  "confirm": true
+}
+```
+
+### memory-view
+View the current conversation history in markdown format.
+
+Parameters: None
+
+Returns the full markdown content of the conversation history.
+
+### memory-search
+Semantic search in long-term memory (if enabled).
+
+Parameters:
+- `query` (required): Search query
+- `count` (optional): Number of results (default: 3)
+
+Example:
+```json
+{
+  "query": "what did we discuss about the project",
+  "count": 5
+}
+```
+
+## Markdown Format
+
+The conversation history uses this format:
+
+```markdown
+# Conversation History
+
+### **Human** (2025-01-30 10:15:32)
+Hello, how are you?
+
+### **Assistant** (2025-01-30 10:15:35)
+I'm doing well! How can I help you today?
+
+### **Note** (2025-01-30 10:16:00)
+User prefers formal language.
+```
+
+## Integration with SimpleMemory Node
+
+When connected to a Chat Agent:
+1. Conversation is automatically logged to markdown
+2. Window size limits short-term memory
+3. Overflow archives to vector DB (if long-term enabled)
+4. You can view/edit the markdown in the node's parameter panel
+
+## Best Practices
+
+1. Use memory-save for explicit user requests to remember
+2. Use memory-search for semantic recall of past discussions
+3. Don't save sensitive information without user consent
+4. The markdown is editable - users can manually curate their history