Get the FREE Ultimate OpenClaw Setup Guide →

Matrix Dreamer

npx machina-cli add skill ojowwalker77/Claude-Matrix/dreamer --openclaw
Files (1)
SKILL.md
2.7 KB

Matrix Dreamer - Scheduled Task Automation

Schedule and manage automated Claude Code tasks using native OS schedulers (launchd on macOS, crontab on Linux).

Parse user arguments from the skill invocation (text after the trigger phrase).

Use the matrix_dreamer tool with the appropriate action parameter.

CRITICAL: One-Time vs Recurring

BEFORE using action: "add", you MUST clarify with the user:

  • "Do you want this to run ONCE or RECURRING (daily/weekly/etc)?"

Natural language like "at 1am" or "tonight at 3pm" is converted to cron expressions, which are always recurring. Users often expect one-time execution but get daily tasks instead.

  • One-time execution: Use action: "run" for immediate execution
  • Recurring tasks: Use action: "add" only after confirming recurring intent

Actions

List tasks (default, or "list"): Use matrix_dreamer with action: "list".

  • Optional: limit to cap results
  • Optional: tag to filter by tag

Add task ("add", "schedule"): Use matrix_dreamer with action: "add" and:

  • name: Task name (required, max 100 chars)
  • schedule: Cron expression or natural language (e.g., "every day at 9am")
  • command: Claude prompt or /command to execute
  • Optional: description, workingDirectory, timeout, timezone, tags, skipPermissions
  • Optional: worktree: { enabled: true } for isolated git worktree execution
  • Optional: env for environment variables

Run immediately ("run <taskId>"): Use matrix_dreamer with action: "run" and taskId.

Remove task ("remove <taskId>", "delete <taskId>"): Use matrix_dreamer with action: "remove" and taskId.

System status ("status"): Use matrix_dreamer with action: "status".

View logs ("logs <taskId>"): Use matrix_dreamer with action: "logs" and taskId.

  • Optional: lines (default: 50)
  • Optional: stream: "stdout", "stderr", or "both"

Execution history ("history"): Use matrix_dreamer with action: "history".

  • Optional: limit to cap results

Examples

  • /matrix:dreamer - list all scheduled tasks
  • /matrix:dreamer add "daily-review" every day at 9am "/matrix:review staged"
  • /matrix:dreamer run task_abc123
  • /matrix:dreamer status
  • /matrix:dreamer logs task_abc123
  • /matrix:dreamer remove task_abc123
  • /matrix:dreamer history

Source

git clone https://github.com/ojowwalker77/Claude-Matrix/blob/main/skills/dreamer/SKILL.mdView on GitHub

Overview

Matrix Dreamer lets you schedule and manage Claude Code tasks with native OS schedulers (launchd on macOS, crontab on Linux). It parses user arguments from the skill invocation and executes via the matrix_dreamer tool with an action parameter. It supports listing, adding, running now, removing, viewing status and logs, and viewing history, with careful handling of one-time vs recurring tasks.

How This Skill Works

The skill parses the user’s trigger phrase, derives the matrix_dreamer action (add, list, run, remove, status, logs, history), and calls the tool to schedule or execute tasks. Natural language like 'every day at 9am' converts to a cron expression and is treated as recurring; for a one-time execution, use action 'run' with a specific taskId, and confirm if recurring is desired before adding.

When to Use It

  • You want to create a new Claude Code task with a cron-like schedule (recurring) or natural-language timing.
  • You need to list all scheduled tasks or filter by tag to review what's next.
  • You want to run a task immediately or check its status for quick validation.
  • You want to remove or delete a scheduled task that is no longer needed.
  • You need to view logs or execution history to troubleshoot a task.

Quick Start

  1. Step 1: Decide if the task should run once or recur; clarify before adding recurring tasks.
  2. Step 2: Use matrix_dreamer with the appropriate action (add/list/run/remove) and provide required fields (name, schedule or taskId, command).
  3. Step 3: Verify results via status, logs, or history and adjust as needed.

Best Practices

  • Clarify whether the task should run once or recur before adding a new task.
  • Use a clear, descriptive task name (max 100 chars) and a precise schedule.
  • Prefer well-formed cron expressions or explicit natural-language timing; note all natural-language schedules are recurring.
  • Utilize optional fields (description, workingDirectory, timeout, timezone, env, tags) and worktree for isolation when needed.
  • Regularly monitor status, logs, and history to audit execution and diagnose issues.

Example Use Cases

  • /matrix:dreamer - list all scheduled tasks
  • /matrix:dreamer add \"daily-review\" every day at 9am \"/matrix:review staged\"
  • /matrix:dreamer run task_abc123
  • /matrix:dreamer status
  • /matrix:dreamer logs task_abc123

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers