golem-trigger-agent-ts

Trigger TypeScript Golem agents asynchronously with golem agent invoke --trigger.

Updated May 17, 2026
One-click install
npx skills add https://github.com/Rust-soham/golem-claw --skill golem-trigger-agent-ts-rust-soham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golem-trigger-agent-ts
Source: https://github.com/Rust-soham/golem-claw/tree/main/packages/golem/.agents/skills/golem-trigger-agent-ts
Command: npx skills add https://github.com/Rust-soham/golem-claw --skill golem-trigger-agent-ts-rust-soham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the need to start an agent method asynchronously without blocking for a result, especially when you only care that the work gets enqueued and eventually executed.

Core Features & Use Cases

  • Fire-and-forget triggering: Send an invocation request and return immediately, using the idempotency key as the only returned value.
  • Background and scheduled work: Enqueue long-running operations now or schedule them for later with a specific execution time.
  • Idempotent enqueuing: Prevent duplicate execution by reusing the same idempotency key.

Quick Start

Trigger your agent method in a non-blocking way by running: golem agent invoke --trigger <AGENT_ID> <FUNCTION_NAME> <ARGUMENTS...>.

Frequently Asked Questions about golem-trigger-agent-ts

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

FAQPage Schema
How do I trigger a Golem agent invocation in TypeScript without waiting for the result?

This approach enqueues the background task immediately and returns only the idempotency key, allowing your TypeScript application to continue executing without blocking for the agent's return value.

Can I schedule a deferred Golem agent execution for a specific time?

Yes, you can schedule deferred Golem agent execution by configuring the trigger command with a specific execution time, enqueueing the background work to run later across staging or production environments.

How do I prevent duplicate executions when enqueuing background TypeScript agent tasks?

You prevent duplicate background task executions by reusing the same idempotency key across repeated fire-and-forget Golem agent invocations, ensuring the operation is only processed once.

What CLI flags are required for non-blocking Golem agent invocation?

Non-blocking Golem agent invocation requires the --trigger and --no-stream flags, along with correct TypeScript value syntax for agent IDs and arguments when executing the golem agent invoke command.

When should I use fire-and-forget triggering instead of waiting for a Golem agent response?

Use fire-and-forget triggering for long-running background operations when your application only needs confirmation that work is enqueued and eventually executed, without requiring the agent's return value to proceed.