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.
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.
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).
This is a knowledge/reference skill for Gleam-Erlang interoperability, covering external function declarations, Erlang stdlib usage, Dynamic type decoding, NIFs/ports, and OTP integration. No scripts were bundled — all content is inline code examples in the SKILL.md. The skill is well-written with comprehensive coverage and good error handling patterns, but is monolithic (no references/ or scripts/ directories) and targets a niche audience (Gleam developers needing Erlang interop).
Purely a reference/knowledge skill with no executable scripts. The os.cmd and httpc patterns are standard Erlang interop but represent risk vectors if adopted naively. Would benefit from splitting long content into references/ files and adding concrete runnable examples in scripts/.