golem-trigger-agent-rust

Triggers fire-and-forget invocations on Rust 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-rust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-trigger-agent-rust
Source: https://github.com/golemcloud/golem/tree/main/golem-skills/skills/rust/golem-trigger-agent-rust
Command: npx skills add https://github.com/golemcloud/golem --skill golem-trigger-agent-rust

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 forces you to wait. This Skill shows how to enqueue asynchronous, fire-and-forget agent method invocations with the golem CLI.

Core Features & Use Cases

  • Fire-and-Forget Invocation: Use golem agent invoke --trigger to enqueue a method call that returns immediately with only the idempotency key.
  • Scheduling and Idempotency: Combine --schedule-at for future execution and -i for explicit idempotency keys that prevent duplicate runs.
  • Rust Value Syntax: Pass agent IDs and arguments using Rust syntax, including records, enums, options, and tuples.
  • Use Case: Trigger a nightly batch job on a BatchProcessor agent with a fixed idempotency key so the report runs once in the background while your CLI session continues.

Quick Start

Ask the AI to trigger a background method on your Golem agent, for example: trigger the run_daily_report method on the BatchProcessor agent without waiting for the result.

Frequently Asked Questions about golem-trigger-agent-rust

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

FAQPage Schema
How do I trigger a Golem agent method without waiting for the result?

Use golem agent invoke --trigger followed by the agent ID, function name, and arguments. The --trigger flag enqueues the invocation and returns immediately with only the idempotency key instead of 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 meant for fire-and-forget background work.

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

Yes, combine --trigger with --schedule-at 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 Golem 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, and passing "-" auto-generates a key.

What syntax do I use for agent arguments in the golem CLI?

Arguments use Rust syntax: snake_case field names, Some(value) or None for options, MyRecord { field: value } for records, MyEnum::Variant(value) for enums, and (1, "hello") for tuples.