erlang

Erlang concurrent programming with OTP. Use for .erl files.

7 stars

byG1Joshi

View on GitHub Installation ↓

Best use case

erlang is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Erlang concurrent programming with OTP. Use for .erl files.

Teams using erlang should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/erlang/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/languages/erlang/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/erlang/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How erlang Compares

Feature / Agent	erlang	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Erlang concurrent programming with OTP. Use for .erl files.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Erlang

Erlang powered WhatsApp and the telecom backbone. OTP 27 (2024) adds a **JSON module** and triple-quoted strings. It is the foundation of Elixir.

## When to Use

- **99.9999999% Reliability**: Hot code reloading, supervision trees.
- **Massive Concurrency**: Lightweight processes (millions per node).
- **Distributed Systems**: Distributed Erlang nodes connect natively.

## Core Concepts

### OTP

Open Telecom Platform. Behaviors like `gen_server` (Generic Server).

### Let it Crash

Don't catch exceptions. Let the supervisor restart the process.

### Message Passing

`Pid ! Message`. No shared memory.

## Best Practices (2025)

**Do**:

- **Use `rebar3`**: The standard build tool.
- **Use `maybe`**: The new monadic-like flow control (enabled by default in 27).
- **Use `json`**: The new stdlib JSON parser (faster/safer).

**Don't**:

- **Don't optimize pre-maturely**: Profile first. Messages are copied.

## References

- [Erlang.org](https://www.erlang.org/)