Gleam — Erlang Interop

What it does

This skill documents patterns and examples to make Gleam interoperate safely with the Erlang/BEAM ecosystem. It explains declaring external functions, decoding dynamic Erlang types, using Erlang standard libraries (crypto, httpc, ets), NIFs and ports, and integrating with OTP supervisors and gen_server. Concrete code snippets show how to wrap Erlang calls in typed Gleam functions and handle errors at the boundary.

When to use it

Use this skill when you need Gleam code to call existing Erlang libraries or runtime features (timers, ETS, gen_server), when writing NIFs or ports for performance or external processes, or when decoding/validating dynamic Erlang terms received from other BEAM services. It's targeted at Gleam developers building production BEAM apps that need type-safe interop.

What's included

• Scripts: None in this skill (has_scripts=false)
• References: Linked guides and docs referenced in the SKILL.md (has_references=false as packaged)
• Instructions: Detailed examples for external function declarations, dynamic decoders, working with atoms/tuples, ETS usage, HTTP via httpc, NIF/port patterns, OTP integration, and best-practice pitfalls to avoid.

Compatible agents

Likely useful to coding assistants and code-writing agents that support repository browsing and language-aware editing (e.g., Claude Code, Copilot/GitHub Copilot, Codex-style agents).