golem-trigger-agent-scala

Triggers fire-and-forget invocations on Scala Golem agents using the golem CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you need to start a long-running or background operation on a Golem agent without blocking on the result, a synchronous invocation is the wrong tool. This Skill shows how to enqueue asynchronous, fire-and-forget invocations on Scala Golem agents using the golem CLI's --trigger flag.

Core Features & Use Cases

  • Fire-and-Forget Invocation: Use golem agent invoke --trigger to enqueue a method call that returns immediately with only an idempotency key.
  • Idempotency and Scheduling: Control duplicate execution with explicit idempotency keys and defer execution with the --schedule-at option.
  • Scala Value Syntax: Pass agent IDs and arguments using Scala syntax, including records, options, variants, and tuples.
  • Use Case: Trigger a daily report job on a BatchProcessor agent with a fixed idempotency key so the job runs in the background and cannot be accidentally executed twice.

Quick Start

Ask the AI to trigger a fire-and-forget invocation of a method on your Scala Golem agent using golem agent invoke --trigger with the appropriate agent ID and arguments.

Frequently Asked Questions about golem-trigger-agent-scala

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

FAQPage Schema
How do I trigger a fire-and-forget invocation on a Golem agent?

Run golem agent invoke --trigger followed by the agent ID, function name, and arguments. The --trigger (or -t) flag enqueues the invocation and returns immediately with only the idempotency key, without waiting for the result.

What is the difference between golem agent invoke and invoke --trigger?

Regular invoke waits for the result, returns the value, and streams agent output. The --trigger variant returns immediately with only the idempotency key, does not stream output, and is intended for background or fire-and-forget work.

Can I schedule a Golem agent invocation for a future time?

Yes, combine --trigger with the --schedule-at option and an ISO 8601 datetime such as 2026-03-15T10:30:00Z. The invocation is enqueued and executed by the Golem runtime at the specified time.

How do idempotency keys work with triggered invocations?

Triggered invocations accept an idempotency key via -i or --idempotency-key. If the same key is reused, the invocation will not be executed again; passing "-" auto-generates a key.

What argument syntax does the Scala Golem agent invoke command use?

Arguments use Scala syntax: camelCase field names with = separators, Some(value)/None for options, MyRecord(field = value) for records, MyEnum.VariantName(value) for variants, and (1, "hello") for tuples.