golem-call-another-agent-ts

Creates agent-to-agent RPC calls between TypeScript Golem agents using generated clients and awaitable methods.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It enables agent-to-agent RPC in a TypeScript Golem project so one agent can call a different agent and reliably receive the returned value.

Core Features & Use Cases

  • Awaited agent-to-agent calls: Use the generated client (<AgentClass>.get(...)) to invoke remote methods and block until the result is returned.
  • Implicit agent creation and reuse: The first awaited call creates the agent instance implicitly; subsequent calls with the same constructor parameters reuse it.
  • Cross-component RPC support: Inter-component agent calls work by generating bridge SDK code during golem build.
  • Deadlock avoidance guidance: Prevents RPC cycles by using .trigger() for fire-and-forget instead of awaiting each other.

Quick Start

Tell the AI to “In my TypeScript Golem project, show how to call another agent using the generated get() client, await a method result, and avoid deadlocks with fire-and-forget where needed.”

Frequently Asked Questions about golem-call-another-agent-ts

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

FAQPage Schema
How do I call another agent and wait for its result in a TypeScript Golem project?

To call another agent in TypeScript Golem, use the generated @agent client via <AgentClass>.get(...) to invoke a remote method and await the target agent's response. The first awaited call implicitly creates the agent instance, and subsequent calls with the same parameters reuse it.

How does cross-component inter-agent communication work in Golem?

Cross-component inter-agent communication in Golem works by generating bridge SDK code during the golem build process. This allows agents in different components to obtain client handles and execute remote procedure calls against each other synchronously.

Why do my Golem agent RPC calls deadlock when awaiting each other?

Golem agent RPC calls deadlock when agents synchronously await each other in a cycle. To avoid RPC deadlocks, use the .trigger() method for fire-and-forget calls, which breaks the await dependency and allows the calling agent to proceed without blocking.

Does Golem support synchronous agent-to-agent RPC in TypeScript?

Yes, Golem supports synchronous agent-to-agent RPC in TypeScript. By obtaining a client handle with <AgentClass>.get(...), the caller agent can block execution until the remote method returns a value, enabling synchronous inter-agent workflows.

Can I use fire-and-forget to prevent RPC cycles between Golem agents?

Yes, you can use the .trigger() method to execute fire-and-forget calls that prevent RPC cycles between Golem agents. This approach breaks await dependencies, ensuring the caller does not block and avoiding circular deadlocks in inter-agent communication.