How do I install the Golem Schedule Agent Scala skill?

Run npx skillmds@latest add golemcloud/golem-schedule-agent-scala in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Golem Schedule Agent Scala safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Golem Schedule Agent Scala?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Golem Schedule Agent Scala free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Golem Schedule Agent Scala?

golemcloud (@golemcloud) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Golem Schedule Agent Scala by golemcloud

Name: Golem Schedule Agent Scala
Author: golemcloud

File contents

Scheduling a Future Agent Invocation

Both golem and golem-cli can be used — all commands below work with either binary.

Usage

golem agent invoke --trigger --schedule-at <DATETIME> <AGENT_ID> <FUNCTION_NAME> [ARGUMENTS...]

The --schedule-at flag schedules the invocation to execute at a specific future time. It requires the --trigger flag because scheduled invocations are always fire-and-forget — the CLI returns immediately after the invocation is enqueued.

DateTime Format

The --schedule-at value must be in ISO 8601 / RFC 3339 format with a timezone:

2026-03-15T10:30:00Z          # UTC
2026-03-15T10:30:00+02:00     # With timezone offset

Examples

Schedule a method to run at a specific time

golem agent invoke --trigger --schedule-at 2026-03-15T10:30:00Z 'MyAgent()' runDailyReport

Schedule with parameters

golem agent invoke --trigger --schedule-at 2026-04-01T00:00:00Z 'BatchProcessor("daily")' generateReport '"Q1-2026"'

Schedule in a specific environment

golem agent invoke --trigger --schedule-at 2026-03-15T08:00:00Z 'production/NotificationAgent()' sendReminders

Schedule with an idempotency key for deduplication

golem agent invoke --trigger --schedule-at 2026-03-15T10:30:00Z -i 'report-2026-03-15' 'ReportAgent()' generateDaily

Available Options

Option	Description
`-t, --trigger`	Required with `--schedule-at`. Fire-and-forget mode
`--schedule-at <DATETIME>`	The time to execute the invocation (ISO 8601 / RFC 3339)
`-i, --idempotency-key <KEY>`	Set a specific idempotency key; use `"-"` for auto-generated
`--no-stream`	Disable live streaming of agent stdout/stderr/log

How It Works

The CLI sends the invocation request with the scheduled time to the Golem server
The server enqueues the invocation to execute at the specified time
The CLI returns immediately with the idempotency key
At the scheduled time, the Golem runtime executes the invocation

Idempotency

Scheduled invocations use idempotency keys just like regular invocations. Providing the same idempotency key for a scheduled invocation ensures it is not executed more than once, even if the CLI command is retried.

Auto-Deploy

If the agent's component has not been deployed yet and the CLI is run from an application directory, the command will automatically build and deploy the component before scheduling.

Value Syntax

The agent ID parameters and method arguments use Scala syntax:

Field names use camelCase with = separator
Options: Some(value) / None
Records: MyRecord(fieldOne = 1, fieldTwo = "hello")
Variants: MyEnum.VariantName(value)
Tuples: (1, "hello")

golem agent invoke --trigger --schedule-at 2026-03-15T10:30:00Z 'MyAgent("user-123")' runTask 'TaskConfig(priority = 1, retry = true)'

---name: golem-schedule-agent-scaladescription: Scheduling a future invocation on a Scala Golem agent. Use when asked to schedule, delay, or plan a future agent method invocation using golem agent invoke --trigger --schedule-at.---# Scheduling a Future Agent InvocationBoth `golem` and `golem-cli` can be used — all commands below work with either binary.## Usage```shellgolem agent invoke --trigger --schedule-at <DATETIME> <AGENT_ID> <FUNCTION_NAME> [ARGUMENTS...]```The `--schedule-at` flag schedules the invocation to execute at a specific future time. It **requires** the `--trigger` flag because scheduled invocations are always fire-and-forget — the CLI returns immediately after the invocation is enqueued.## DateTime FormatThe `--schedule-at` value must be in **ISO 8601 / RFC 3339** format with a timezone:```2026-03-15T10:30:00Z # UTC2026-03-15T10:30:00+02:00 # With timezone offset```## Examples### Schedule a method to run at a specific time```shellgolem agent invoke --trigger --schedule-at 2026-03-15T10:30:00Z 'MyAgent()' runDailyReport```### Schedule with parameters```shellgolem agent invoke --trigger --schedule-at 2026-04-01T00:00:00Z 'BatchProcessor("daily")' generateReport '"Q1-2026"'```### Schedule in a specific environment```shellgolem agent invoke --trigger --schedule-at 2026-03-15T08:00:00Z 'production/NotificationAgent()' sendReminders```### Schedule with an idempotency key for deduplication```shellgolem agent invoke --trigger --schedule-at 2026-03-15T10:30:00Z -i 'report-2026-03-15' 'ReportAgent()' generateDaily```## Available Options| Option | Description ||--------|-------------|| `-t, --trigger` | **Required** with `--schedule-at`. Fire-and-forget mode || `--schedule-at <DATETIME>` | The time to execute the invocation (ISO 8601 / RFC 3339) || `-i, --idempotency-key <KEY>` | Set a specific idempotency key; use `"-"` for auto-generated || `--no-stream` | Disable live streaming of agent stdout/stderr/log |## How It Works1. The CLI sends the invocation request with the scheduled time to the Golem server2. The server enqueues the invocation to execute at the specified time3. The CLI returns immediately with the idempotency key4. At the scheduled time, the Golem runtime executes the invocation## IdempotencyScheduled invocations use idempotency keys just like regular invocations. Providing the same idempotency key for a scheduled invocation ensures it is not executed more than once, even if the CLI command is retried.## Auto-DeployIf the agent's component has not been deployed yet and the CLI is run from an application directory, the command will automatically build and deploy the component before scheduling.## Value SyntaxThe agent ID parameters and method arguments use **Scala syntax**:- Field names use `camelCase` with `=` separator- Options: `Some(value)` / `None`- Records: `MyRecord(fieldOne = 1, fieldTwo = "hello")`- Variants: `MyEnum.VariantName(value)`- Tuples: `(1, "hello")````shellgolem agent invoke --trigger --schedule-at 2026-03-15T10:30:00Z 'MyAgent("user-123")' runTask 'TaskConfig(priority = 1, retry = true)'```

Frequently asked questions

Golem Schedule Agent Scala