@johpaz/hive-agents 0.0.35 → 0.0.36

package/packages/skills/src/bundled/canvas/canvas_dashboard/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: canvas_dashboard
+description: "Real-time visual dashboard for monitoring task status, progress, and system state"
+version: 1.0.0
+author: Hive Team
+icon: "📈"
+category: canvas
+permissions:
+  - canvas_write
+dependencies: []
+tools: [canvas_render, canvas_show_progress, canvas_clear]
+
+# Structured skill fields
+triggers:
+  - "mostrá el dashboard"
+  - "show dashboard"
+  - "estado en tiempo real"
+  - "real-time status"
+  - "monitoreo visual"
+  - "visual monitoring"
+  - "panel de control"
+  - "control panel"
+  - "limpiá el canvas"
+  - "clear canvas"
+  - "actualizá el dashboard"
+  - "update dashboard"
+
+preferred_agents: []
+
+steps:
+  - step: 1
+    action: canvas_clear
+    instruction: "Clear existing canvas content before rendering new dashboard"
+    output: canvas_cleared
+
+  - step: 2
+    action: canvas_render
+    instruction: "Render dashboard layout with components (progress, status, metrics)"
+    params:
+      component: "dashboard"
+      sections: "Array of dashboard sections"
+    output: dashboard_rendered
+
+  - step: 3
+    action: canvas_show_progress
+    instruction: "Update progress bars for ongoing tasks"
+    params:
+      bars: "Array of {label, value, status}"
+    output: progress_updated
+
+  - step: 4
+    action: canvas_render (updates)
+    instruction: "Update dashboard with real-time changes"
+    params:
+      updates: "Changed components"
+    output: dashboard_updated
+
+rules:
+  - "Clear canvas before rendering new dashboard to avoid clutter"
+  - "Use consistent layout: header, progress section, status section, metrics"
+  - "Update progress bars in real-time as tasks advance"
+  - "Use color coding: green=complete, blue=in_progress, red=error"
+  - "Keep dashboard concise — show only critical information"
+  - "Clear dashboard when session context changes significantly"
+  - "Use span: 'full' in canvas_render or canvas_show_* for components that need full canvas width (tables, charts, long markdown)"
+
+output_format:
+  structure: canvas_dashboard
+  sections:
+    - "header"
+    - "progress_section"
+    - "status_section"
+    - "metrics"
+  max_length: "Concise real-time overview"
+
+examples:
+  - user_input: "mostrá el dashboard del proyecto"
+    expected_behavior: "canvas_clear → canvas_render({ sections: [progress, tasks, metrics] }) → update in real-time"
+
+  - user_input: "actualizá el estado en el dashboard"
+    expected_behavior: "canvas_show_progress({ bars: [{label: 'Research', value: 100, status: 'complete'}, ...] })"
+
+  - user_input: "limpiá el canvas"
+    expected_behavior: "canvas_clear({}) → empty canvas"
+---
+
+# Canvas Dashboard Skill
+
+## Cuándo se Activa
+
+Para mostrar dashboards visuales de monitoreo en tiempo real de tareas, proyectos, o estado del sistema.
+
+## Herramientas Disponibles
+
+| Tool | Qué hace | Cuándo usarla |
+|------|----------|---------------|
+| `canvas_render` | Renderiza componentes | Layout del dashboard |
+| `canvas_show_progress` | Barras de progreso | Estado de tasks |
+| `canvas_clear` | Limpia canvas | Antes de nuevo dashboard |
+
+## Workflow
+
+1. **Clear** → `canvas_clear()` — limpiar previo
+2. **Render layout** → `canvas_render({ sections })`
+3. **Update progress** → `canvas_show_progress()` en tiempo real
+4. **Refresh** → `canvas_render({ updates })` para cambios
+
+## Estructura de Dashboard
+
+```javascript
+canvas_render({
+  component: {
+    id: "dashboard-main",
+    type: "markdown",
+    props: { content: "## Dashboard\n..." },
+    span: "full"   // ← ancho completo del canvas
+  }
+})
+
+// O con tarjetas individuales:
+canvas_show_card({ title: "Métricas", span: "full", items: [...] })
+canvas_show_progress({ tasks: [...], span: "full" })
+```
+
+## Color Coding
+
+| Color | Estado |
+|-------|--------|
+| 🟢 Verde | Complete |
+| 🔵 Azul | In Progress |
+| 🔴 Rojo | Error/Blocked |
+| 🟡 Amarillo | Pending |
+
+## Mejores Prácticas
+
+- Clear antes de renderizar nuevo dashboard
+- Layout consistente (header, progress, status, metrics)
+- Update en tiempo real con progreso
+- Solo información crítica (no sobrecargar)
+
+## Errores a Evitar
+
+- ❌ No clear entre dashboards (clutter)
+- ❌ Demasiada información (sobrecarga visual)
+- ❌ No actualizar en tiempo real
+- ❌ Sin color coding para estados

package/packages/skills/src/bundled/canvas/canvas_interact/SKILL.md

@@ -0,0 +1,148 @@
+---
+name: canvas_interact
+description: "Collect user input and confirmations through interactive forms and dialogs"
+version: 1.0.0
+author: Hive Team
+icon: "💬"
+category: canvas
+permissions:
+  - canvas_write
+dependencies: []
+tools: [canvas_ask, canvas_confirm]
+
+# Structured skill fields
+triggers:
+  - "preguntame"
+  - "ask me"
+  - "formulario"
+  - "form"
+  - "confirmame"
+  - "confirm"
+  - "necesito ingresar datos"
+  - "need to enter data"
+  - "dialogo"
+  - "dialog"
+  - "input del usuario"
+  - "user input"
+  - "seleccionar opcion"
+  - "select option"
+
+preferred_agents: []
+
+steps:
+  - step: 1
+    action: determine_interaction_type
+    instruction: "Determine if simple confirmation (yes/no) or complex form input needed"
+    output: interaction_type
+
+  - step: 2
+    action: canvas_confirm or canvas_ask
+    instruction: "Show appropriate interactive component"
+    params:
+      confirm: "message, confirm/cancel labels"
+      ask: "title, fields array with type/label/options"
+    output: user_response
+
+  - step: 3
+    action: process_response
+    instruction: "Handle user response: proceed if confirmed, collect form data"
+    output: processed_data
+
+rules:
+  - "Use canvas_confirm for simple yes/no decisions"
+  - "Use canvas_ask for multi-field data collection"
+  - "Always provide clear labels and placeholders for form fields"
+  - "Mark required fields explicitly"
+  - "Validate input types (email, number) when applicable"
+  - "Handle cancel/dismiss gracefully"
+
+output_format:
+  structure: canvas_component
+  sections:
+    - "component_type"
+    - "title"
+    - "fields_or_message"
+    - "user_response"
+  max_length: "Interactive form or confirmation"
+
+examples:
+  - user_input: "necesito ingresar mis datos de usuario"
+    expected_behavior: "canvas_ask({ title: 'User Data', fields: [{name: 'email', label: 'Email', type: 'email'}, {name: 'role', label: 'Role', type: 'select', options: [...]}] })"
+
+  - user_input: "confirmame antes de eliminar"
+    expected_behavior: "canvas_confirm({ message: '¿Eliminar archivo?', confirmLabel: 'Sí', cancelLabel: 'Cancelar' })"
+
+  - user_input: "preguntame las preferencias"
+    expected_behavior: "canvas_ask({ title: 'Preferences', fields: [{name: 'theme', label: 'Theme', type: 'select', options: [{label: 'Dark', value: 'dark'}, {label: 'Light', value: 'light'}]}] })"
+---
+
+# Canvas Interact Skill
+
+## Cuándo se Activa
+
+Para recoger input del usuario mediante formularios interactivos o confirmaciones.
+
+## Herramientas Disponibles
+
+| Tool | Qué hace | Cuándo usarla |
+|------|----------|---------------|
+| `canvas_ask` | Muestra formulario | Input multi-campo |
+| `canvas_confirm` | Diálogo confirmación | Yes/No decisions |
+
+## Workflow
+
+### Confirmación Simple
+```javascript
+canvas_confirm({
+  message: "¿Eliminar archivo?",
+  confirmLabel: "Sí, eliminar",
+  cancelLabel: "Cancelar"
+})
+```
+
+### Formulario Complejo
+```javascript
+canvas_ask({
+  title: "User Registration",
+  fields: [
+    { name: "email", label: "Email", type: "email", required: true },
+    { name: "password", label: "Password", type: "password", required: true },
+    { 
+      name: "role", 
+      label: "Role", 
+      type: "select", 
+      options: [
+        { label: "Admin", value: "admin" },
+        { label: "User", value: "user" }
+      ]
+    }
+  ]
+})
+```
+
+## Tipos de Campo
+
+| Type | Uso |
+|------|-----|
+| `text` | Texto libre |
+| `email` | Email con validación |
+| `password` | Contraseña (oculto) |
+| `number` | Números |
+| `select` | Dropdown con opciones |
+| `checkbox` | Booleano |
+| `textarea` | Texto multilínea |
+
+## Mejores Prácticas
+
+- Labels claros y descriptivos
+- Placeholders con ejemplos
+- Marcar required explícitamente
+- Validar tipos (email, number)
+- Manejar cancel gracefully
+
+## Errores a Evitar
+
+- ❌ Labels vagos sin contexto
+- ❌ No marcar required fields
+- ❌ Sin validación de tipo
+- ❌ No manejar cancel

package/packages/skills/src/bundled/canvas/canvas_report/SKILL.md

@@ -0,0 +1,146 @@
+---
+name: canvas_report
+description: "Display structured results to users using cards, lists, and progress indicators"
+version: 1.0.0
+author: Hive Team
+icon: "📊"
+category: canvas
+permissions:
+  - canvas_write
+dependencies: []
+tools: [canvas_show_card, canvas_show_list, canvas_show_progress]
+
+# Structured skill fields
+triggers:
+  - "mostrame en el canvas"
+  - "show on canvas"
+  - "mostrá los resultados"
+  - "show results"
+  - "tarjeta informativa"
+  - "info card"
+  - "lista los resultados"
+  - "list results"
+  - "barra de progreso"
+  - "progress bar"
+  - "dashboard"
+  - "estado visual"
+  - "visual status"
+
+preferred_agents: []
+
+steps:
+  - step: 1
+    action: determine_display_type
+    instruction: "Determine best display format: card for structured info, list for key-value, progress for status"
+    output: display_type
+
+  - step: 2
+    action: canvas_show_card or canvas_show_list
+    instruction: "Render content in appropriate format"
+    params:
+      card: "title, items with labels"
+      list: "key-value pairs"
+    output: rendered
+
+  - step: 3
+    action: canvas_show_progress (if applicable)
+    instruction: "Show progress bars for ongoing tasks"
+    params:
+      bars: "Array of {label, value: 0-100}"
+    output: progress_displayed
+
+rules:
+  - "Use canvas_show_card for structured information with labeled items"
+  - "Use canvas_show_list for simple key-value pairs"
+  - "Use canvas_show_progress for multi-task progress visualization"
+  - "Keep card items concise (max 5-7 items for readability)"
+  - "Use clear labels that indicate what each value represents"
+  - "Clear canvas when switching contexts significantly"
+
+output_format:
+  structure: canvas_component
+  sections:
+    - "component_type"
+    - "title"
+    - "content"
+  max_length: "Concise visual display"
+
+examples:
+  - user_input: "mostrame los resultados en el canvas"
+    expected_behavior: "canvas_show_card({ title: 'Results', items: [{label: 'Found', value: '7 trends'}, {label: 'Sources', value: '5 URLs'}] })"
+
+  - user_input: "lista las configuraciones actuales"
+    expected_behavior: "canvas_show_list({ items: { 'Language': 'Spanish', 'Timezone': 'UTC-3', 'Channel': 'Telegram' } })"
+
+  - user_input: "mostrá el progreso del proyecto"
+    expected_behavior: "canvas_show_progress({ bars: [{label: 'Research', value: 100}, {label: 'Content', value: 60}, {label: 'Email', value: 0}] })"
+---
+
+# Canvas Report Skill
+
+## Cuándo se Activa
+
+Para mostrar resultados estructurados visualmente en el canvas del usuario.
+
+## Herramientas Disponibles
+
+| Tool | Qué hace | Cuándo usarla |
+|------|----------|---------------|
+| `canvas_show_card` | Muestra información estructurada | Resultados con items etiquetados |
+| `canvas_show_list` | Lista clave-valor | Configuraciones, datos simples |
+| `canvas_show_progress` | Barras de progreso | Estado de tasks múltiples |
+
+## Workflow
+
+1. **Determinar formato** → Card vs List vs Progress
+2. **Renderizar** → `canvas_show_*` apropiado
+3. **Clear** → Si cambio de contexto significativo
+
+## Formatos
+
+### Card
+```javascript
+canvas_show_card({
+  title: "Research Results",
+  items: [
+    { label: "Trends Found", value: "7" },
+    { label: "Sources", value: "5 URLs" },
+    { label: "Time", value: "2.5 min" }
+  ]
+})
+
+// Full-width card (ocupa todo el ancho del canvas):
+canvas_show_card({
+  title: "Full Report",
+  span: "full",
+  items: [...]
+})
+```
+
+### List
+```javascript
+canvas_show_list({
+  items: {
+    "Language": "Spanish",
+    "Timezone": "UTC-3",
+    "Channel": "Telegram"
+  }
+})
+```
+
+### Progress
+```javascript
+canvas_show_progress({
+  bars: [
+    { label: "Research", value: 100 },
+    { label: "Content", value: 60 },
+    { label: "Email", value: 0 }
+  ]
+})
+```
+
+## Errores a Evitar
+
+- ❌ Cards con demasiados items (>7)
+- ❌ Labels vagos sin contexto
+- ❌ No clear entre contextos diferentes

package/packages/skills/src/bundled/cli/cli_pipeline/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: cli_pipeline
+description: "Execute shell commands and pipe output to files for logging and further processing"
+version: 1.0.0
+author: Hive Team
+icon: "🔗"
+category: cli
+permissions:
+  - shell_exec
+  - filesystem_write
+dependencies: []
+tools: [exec, terminal, project_write]
+
+# Structured skill fields
+triggers:
+  - "guardá el output"
+  - "save output"
+  - "pipeline"
+  - "pipe to file"
+  - "redireccioná el output"
+  - "redirect output"
+  - "log del comando"
+  - "command log"
+  - "ejecutá y guardá"
+  - "run and save"
+  - "resultado en archivo"
+  - "result to file"
+
+preferred_agents: []
+
+steps:
+  - step: 1
+    action: validate_command
+    instruction: "Validate command is safe and appropriate for pipeline execution"
+    output: validated_command
+
+  - step: 2
+    action: exec or terminal
+    instruction: "Execute command and capture full output (stdout + stderr)"
+    params:
+      command: "validated command"
+      timeout: "appropriate timeout"
+    output: command_output
+
+  - step: 3
+    action: format_output
+    instruction: "Format output for file storage: add timestamp, command, execution time"
+    output: formatted_output
+
+  - step: 4
+    action: project_write
+    instruction: "Write output to specified file path"
+    params:
+      path: "logs/command_YYYY-MM-DD_HH-MM-SS.log"
+      content: "formatted output"
+    output: file_written
+
+rules:
+  - "Capture both stdout and stderr for complete logging"
+  - "Add metadata: timestamp, command, execution time, exitCode"
+  - "Use descriptive filenames with timestamps for logs"
+  - "For large outputs, write incrementally or split files"
+  - "Confirm file path before writing"
+
+output_format:
+  structure: markdown
+  sections:
+    - "command"
+    - "timestamp"
+    - "exit_code"
+    - "execution_time"
+    - "output_file"
+  max_length: "Full logged output"
+
+examples:
+  - user_input: "ejecutá npm install y guardá el output en logs/install.log"
+    expected_behavior: "exec({ command: 'npm install' }) → format with metadata → project_write({ path: 'logs/install.log' })"
+
+  - user_input: "corré los tests y guardá el resultado"
+    expected_behavior: "terminal({ command: 'npm test' }) → capture full output → write to timestamped log file"
+
+  - user_input: "hacé un pipeline de git log a archivo"
+    expected_behavior: "exec({ command: 'git log --oneline' }) → write to 'logs/git_log_YYYY-MM-DD.md'"
+---
+
+# CLI Pipeline Skill
+
+## Cuándo se Activa
+
+Para ejecutar comandos y guardar el output en archivos para logging o procesamiento posterior.
+
+## Herramientas Disponibles
+
+| Tool | Qué hace | Cuándo usarla |
+|------|----------|---------------|
+| `exec` | Ejecuta comando | Comandos simples |
+| `terminal` | Ejecuta con entorno | Comandos complejos |
+| `project_write` | Escribe archivo | Guardar output |
+
+## Workflow
+
+1. **Validar comando** → Seguro para ejecución
+2. **Ejecutar** → Capturar stdout + stderr
+3. **Formatear** → Agregar timestamp, comando, metadata
+4. **Escribir** → `project_write({ path, content })`
+
+## Formato de Log
+
+```markdown
+# Command Log
+
+**Command**: npm install
+**Timestamp**: 2025-03-09 14:30:00
+**Exit Code**: 0
+**Execution Time**: 45.2s
+
+---
+
+## Output
+
+[stdout content...]
+[stderr if any...]
+```
+
+## Mejores Prácticas
+
+- Filenames con timestamp para tracking
+- Incluir metadata completa (exitCode, tiempo)
+- Capturar stdout y stderr
+- Para outputs grandes, escribir incrementalmente
+
+## Errores a Evitar
+
+- ❌ No incluir metadata en log
+- ❌ Filenames genéricos sin timestamp
+- ❌ No capturar stderr

package/packages/skills/src/bundled/cli/cli_safe_exec/SKILL.md

@@ -0,0 +1,125 @@
+---
+name: cli_safe_exec
+description: "Execute shell commands safely with error handling, timeouts, and output validation"
+version: 1.0.0
+author: Hive Team
+icon: "💻"
+category: cli
+permissions:
+  - shell_exec
+dependencies: []
+tools: [exec, terminal]
+
+# Structured skill fields
+triggers:
+  - "ejecutá este comando"
+  - "run this command"
+  - "corré el comando"
+  - "execute command"
+  - "terminal"
+  - "bash"
+  - "shell"
+  - "npm"
+  - "yarn"
+  - "bun"
+  - "git"
+  - "docker"
+  - "comando de sistema"
+  - "system command"
+
+preferred_agents: []
+
+steps:
+  - step: 1
+    action: validate_command
+    instruction: "Validate command is safe. Check for destructive operations (rm, DROP, DELETE)"
+    output: validated_command
+
+  - step: 2
+    action: exec or terminal
+    instruction: "Execute with appropriate timeout. Use exec for simple, terminal for complex"
+    params:
+      command: "validated command"
+      timeout: 30-300 seconds
+    output: command_result
+
+  - step: 3
+    action: parse_result
+    instruction: "Parse stdout and stderr. Check exitCode (0=success)"
+    output: parsed_output
+
+  - step: 4
+    action: handle_error
+    instruction: "If failed, analyze error and suggest fixes or retry options"
+    output: error_handling
+
+rules:
+  - "NEVER use for scheduled tasks — use cron.create instead"
+  - "Prefer read-only commands when possible"
+  - "Confirm before destructive operations (rm, DROP, DELETE, --force)"
+  - "Set appropriate timeout: 30s simple, 120s builds, 300s heavy"
+  - "Always check exitCode — non-zero means failure"
+  - "Use absolute paths for reliability"
+
+output_format:
+  structure: markdown
+  sections:
+    - "command"
+    - "exit_code"
+    - "stdout"
+    - "stderr"
+    - "execution_time"
+  max_length: "Full output with analysis"
+
+examples:
+  - user_input: "ejecutá npm install"
+    expected_behavior: "exec({ command: 'npm install', timeout: 120 }) → check exitCode → return installation summary"
+
+  - user_input: "corré los tests"
+    expected_behavior: "exec({ command: 'npm test', timeout: 180 }) → parse results → report pass/fail count"
+
+  - user_input: "hacé git status"
+    expected_behavior: "exec({ command: 'git status' }) → return current branch and changes"
+---
+
+# CLI Safe Exec Skill
+
+## Cuándo se Activa
+
+Para ejecutar comandos de shell de forma segura con manejo de errores y timeouts.
+
+## Herramientas Disponibles
+
+| Tool | Qué hace | Cuándo usarla |
+|------|----------|---------------|
+| `exec` | Ejecuta con validación y timeout | Comandos simples (<30s) |
+| `terminal` | Ejecuta con entorno completo | Comandos complejos, Git, npm |
+
+## ⚠️ ADVERTENCIA CRÍTICA
+
+**NUNCA usar para tareas programadas** — usar `cron.create` en su lugar.
+
+## Workflow
+
+1. **Validar** → Comando es seguro, no destructivo
+2. **Ejecutar** → `exec` o `terminal` con timeout apropiado
+3. **Parsear** → Check exitCode, stdout, stderr
+4. **Manejar error** → Si falló, analizar y sugerir fixes
+
+## Timeouts Apropiados
+
+| Tipo | Timeout |
+|------|---------|
+| Listar archivos | 10s |
+| Git operations | 30s |
+| npm install | 120s |
+| npm run build | 120s |
+| npm test | 180s |
+| Docker builds | 300s |
+
+## Errores a Evitar
+
+- ❌ Usar para cron (usar cron.create)
+- ❌ Sin timeout apropiado
+- ❌ Ignorar exitCode
+- ❌ Comandos destructivos sin confirmar