golem-schedule-agent-scala

Schedules future invocations of Scala Golem agent methods via the golem CLI.

1.5k|212|Updated Nov 24, 2023
One-click install
npx skills add https://github.com/golemcloud/golem --skill golem-schedule-agent-scala
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-schedule-agent-scala
Source: https://github.com/golemcloud/golem/tree/main/golem-skills/skills/scala/golem-schedule-agent-scala
Command: npx skills add https://github.com/golemcloud/golem --skill golem-schedule-agent-scala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running a Golem agent method at a specific future time requires knowing the exact CLI flags, datetime format, and fire-and-forget semantics. This Skill provides the correct command structure for scheduling delayed agent invocations on Scala-based Golem agents without trial and error.

Core Features & Use Cases

  • Scheduled Invocation: Uses golem agent invoke --trigger --schedule-at to enqueue an agent method call for a future ISO 8601 / RFC 3339 datetime.
  • Idempotency Support: Accepts an idempotency key so scheduled invocations are not executed more than once even if the command is retried.
  • Scala Value Syntax: Passes agent IDs and arguments using Scala syntax such as Some(value), records, variants, and tuples.
  • Use Case: Schedule a ReportAgent to run generateDaily at 10:30 UTC tomorrow with a deduplication key, directly from the command line.

Quick Start

Ask the AI to schedule a Scala Golem agent method invocation at a specific future time using golem agent invoke with the --trigger and --schedule-at flags.

Frequently Asked Questions about golem-schedule-agent-scala

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I schedule a Golem agent invocation for a future time?

Use golem agent invoke with the --trigger and --schedule-at flags followed by the agent ID, function name, and arguments. The --schedule-at value must be an ISO 8601 / RFC 3339 datetime with a timezone, such as 2026-03-15T10:30:00Z.

Why does golem agent invoke --schedule-at require the --trigger flag?

Scheduled invocations are always fire-and-forget, so --schedule-at requires --trigger. The CLI enqueues the invocation and returns immediately with the idempotency key instead of waiting for the result.

Can I prevent a scheduled Golem invocation from running twice?

Yes, provide an idempotency key with the -i or --idempotency-key option. Using the same key for a scheduled invocation ensures it is not executed more than once, even if the CLI command is retried.

What datetime format does --schedule-at accept?

The --schedule-at flag accepts ISO 8601 / RFC 3339 datetimes with a timezone, such as 2026-03-15T10:30:00Z for UTC or 2026-03-15T10:30:00+02:00 with an offset. Values without a timezone are not valid.

How do I pass Scala arguments to a scheduled Golem agent method?

Arguments use Scala syntax: records like TaskConfig(priority = 1, retry = true), options as Some(value) or None, variants like MyEnum.VariantName(value), and tuples like (1, "hello"). Field names use camelCase with an equals separator.