Golem Call From External Rust
golemcloud/golem
Calling Golem agents from external Rust applications using generated bridge SDKs.
Calling Golem agents from external MoonBit applications using generated bridge SDKs.
Custom licenceAuto-check passed
Install Golem Call From External Moonbit
$ npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install golemcloud/golem golem-call-from-external-moonbit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/golem-skills/skills/moonbit/golem-call-from-external-moonbit .claude/skills/golem-call-from-external-moonbit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "golem-call-from-external-moonbit" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/moonbit/golem-call-from-external-moonbit into .claude/skills/golem-call-from-external-moonbit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-call-from-external-moonbit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/golemcloud/golem/tree/main/golem-skills/skills/moonbit/golem-call-from-external-moonbitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install golemcloud/golem golem-call-from-external-moonbit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/golem-skills/skills/moonbit/golem-call-from-external-moonbit .agents/skills/golem-call-from-external-moonbit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "golem-call-from-external-moonbit" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/moonbit/golem-call-from-external-moonbit into .agents/skills/golem-call-from-external-moonbit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-call-from-external-moonbit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install golemcloud/golem golem-call-from-external-moonbit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/golem-skills/skills/moonbit/golem-call-from-external-moonbit .cursor/skills/golem-call-from-external-moonbit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "golem-call-from-external-moonbit" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/moonbit/golem-call-from-external-moonbit into .cursor/skills/golem-call-from-external-moonbit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-call-from-external-moonbit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/golemcloud/golem.git --path golem-skills/skills/moonbit/golem-call-from-external-moonbit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install golemcloud/golem golem-call-from-external-moonbit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/golem-skills/skills/moonbit/golem-call-from-external-moonbit .gemini/skills/golem-call-from-external-moonbit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "golem-call-from-external-moonbit" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/moonbit/golem-call-from-external-moonbit into .gemini/skills/golem-call-from-external-moonbit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-call-from-external-moonbit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install golemcloud/golem golem-call-from-external-moonbitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .github/skills && cp -r skills-src/golem-skills/skills/moonbit/golem-call-from-external-moonbit .github/skills/golem-call-from-external-moonbit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "golem-call-from-external-moonbit" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/moonbit/golem-call-from-external-moonbit into .github/skills/golem-call-from-external-moonbit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-call-from-external-moonbit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install golemcloud/golem golem-call-from-external-moonbit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/golem-skills/skills/moonbit/golem-call-from-external-moonbit .opencode/skills/golem-call-from-external-moonbit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "golem-call-from-external-moonbit" agent skill from https://github.com/golemcloud/golem/tree/main/golem-skills/skills/moonbit/golem-call-from-external-moonbit into .opencode/skills/golem-call-from-external-moonbit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "golem-call-from-external-moonbit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
golem-call-from-external-moonbit- GitHub stars
- 1.5k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 811 words
- Files
- 1
- Skills in repo
- 289
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Calling Golem agents from external MoonBit applications using generated bridge SDKs.
- Works in 4 steps: Enable Bridge Generation → Generate the Bridge SDK → Add the Generated Module to a Workspace → …
- The user wants to invoke agents from outside the Golem platform
- SKILL.md covers Overview, Step 1: Enable Bridge Generation, Step 2: Generate the Bridge SDK and Step 3: Add the Generated…, plus 9 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Golem Call From External Moonbit is an agent skill from golemcloud/golem. Calling Golem agents from external MoonBit applications using generated bridge SDKs. Use when the user wants to invoke agents from outside the Golem platform, from a standalone MoonBit CLI or native application.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Golem Cloud is the agent-native platform for building AI agents and distributed applications that never lose state, never duplicate work, and never require you to build…
When your agent uses it
- The user wants to invoke agents from outside the Golem platform
- From a standalone MoonBit CLI
- Native application
Example prompts
- “/golem-call-from-external-moonbit”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Enable Bridge Generation
- Generate the Bridge SDK
- Add the Generated Module to a Workspace
- Use the Generated Client
What it can do on your machine
Read from SKILL.md and the folder at commit c6a3029. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are moonbit, bash and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Golem Call From External Moonbit loads about 2.2k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 811 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 811 words (~2,243 tokens).
“Golem can generate typed MoonBit client libraries (bridge SDKs) for calling agents from any external MoonBit application — a CLI tool, a background job, or any native MoonBit program. The generated client communicates with the Golem server's REST API and…”
- name
- golem-call-from-external-moonbit
Files
Just SKILL.md in golem-skills/skills/moonbit/golem-call-from-external-moonbit of golemcloud/golem.
Open the folder on GitHubat commit c6a3029
Compare with similar skills
Golem Call From External Moonbit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Golem Call From External Moonbit this skillgolemcloud/golem | 1.5k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Golem Call From External Rustgolemcloud/golem | 1.5k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Golem Call From External TSgolemcloud/golem | 1.5k | — | ~1.1k | Automated safety check: Pass | Custom licence | |
| Golem Call From External Effectgolemcloud/golem | 1.5k | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| Golem Call Tool Moonbitgolemcloud/golem | 1.5k | — | ~208 | Automated safety check: Pass | Custom licence | |
| Golem Wait For External Input Moonbitgolemcloud/golem | 1.5k | — | ~923 | Automated safety check: Pass | Custom licence |
Similar skills
Golem Call From External TS
golemcloud/golem
Calling Golem agents from external TypeScript/Node.js applications using generated bridge SDKs.
Golem Call From External Effect
golemcloud/golem
Calling Effect-based Golem agents from external Node.js applications with generated TypeScript bridge clients and Effect v4.
Golem Call Tool Moonbit
golemcloud/golem
Calls a generated typed Golem tool client from MoonBit. An agent skill from golemcloud/golem.
Golem Wait For External Input Moonbit
golemcloud/golem
Waiting for external input using Golem promises in a MoonBit Golem project.
Golem Call From External Scala
golemcloud/golem
Calling Golem agents from external applications when the agent is written in Scala.
More from golemcloud/golem
All 289 skills in this repoMoonbit C Binding
golemcloud/golem
Guide for writing MoonBit bindings to C libraries using native FFI.
Adding Dependencies
golemcloud/golem
Adding or updating crate dependencies in the Golem workspace.
Analysing CI Failures
golemcloud/golem
Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.
Creating New Builtin Plugins
golemcloud/golem
Adds a built-in WASM plugin that is externally released and provisioned by the registry service.
DB Migration Scripts
golemcloud/golem
Writing database migration SQL scripts. An agent skill from golemcloud/golem.
Debugging Hanging Tests
golemcloud/golem
Diagnosing and fixing hanging worker executor or integration tests.
Questions about Golem Call From External Moonbit
What does Golem Call From External Moonbit do?
Calling Golem agents from external MoonBit applications using generated bridge SDKs. Golem Call From External Moonbit is an agent skill from golemcloud/golem. Calling Golem agents from external MoonBit applications using generated bridge SDKs.
When should I use Golem Call From External Moonbit?
Golem Call From External Moonbit fits situations like: the user wants to invoke agents from outside the Golem platform; from a standalone MoonBit CLI; native application.
How do I install Golem Call From External Moonbit in Claude Code?
Run `npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a claude-code`. Or copy the skill folder (golem-skills/skills/moonbit/golem-call-from-external-moonbit in golemcloud/golem) into .claude/skills/golem-call-from-external-moonbit in your project. Claude Code loads it when a task matches its description.
How do I install Golem Call From External Moonbit in Codex?
Run `npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a codex`. Or copy the skill folder (golem-skills/skills/moonbit/golem-call-from-external-moonbit in golemcloud/golem) into .agents/skills/golem-call-from-external-moonbit in your project. Codex loads it when a task matches its description.
Can I use Golem Call From External Moonbit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add golemcloud/golem --skill golem-call-from-external-moonbit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/golem-call-from-external-moonbit, .gemini/skills/golem-call-from-external-moonbit, .github/skills/golem-call-from-external-moonbit and .opencode/skills/golem-call-from-external-moonbit in your project.
What does Golem Call From External Moonbit need to run?
SKILL.md names no scripts, command-line tools or credentials: Golem Call From External Moonbit is instructions for the agent only.
Does Golem Call From External Moonbit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Golem Call From External Moonbit safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Golem Call From External Moonbit use?
Golem Call From External Moonbit has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Golem Call From External Moonbit use?
About 2.2k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Golem Call From External Moonbit?
Skills that share tags, products or a category with Golem Call From External Moonbit: Golem Call From External Rust (golemcloud/golem, 1.5k stars), Golem Call From External TS (golemcloud/golem, 1.5k stars), Golem Call From External Effect (golemcloud/golem, 1.5k stars) and Golem Call Tool Moonbit (golemcloud/golem, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Golem Call From External Moonbit?
golemcloud (a GitHub organization) maintains it in golemcloud/golem, which has 1,507 GitHub stars. The repository holds 289 skills in this directory. The repository was last updated on October 8, 2026.
Source: golemcloud/golem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.