Elixir — OTP and LiveView expert patterns
Expert Elixir development — OTP patterns (GenServer, supervision trees, Task/GenStage/Broadway), Phoenix LiveView server-side rendering, Ecto schemas and queries, testing with mocks and property-based tests, plus a code-review checklist for concurrency and fault tolerance
- What
- Expert Elixir development — OTP patterns (GenServer, supervision trees, Task/GenStage/Broadway), Phoenix LiveView server-side rendering, Ecto schemas and queries, testing with mocks and property-based tests, plus a code-review checklist for concurrency and fault tolerance
- Cost
- Free
- Needs
- an Elixir/Phoenix project the agent can read and work on — the skill is an expert methodology, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @mindrally's expert Elixir skill: write production-quality Elixir using current best practices. Covers OTP patterns (GenServer state machines with `init`/`handle_call`/`handle_cast`/`handle_info`, supervision tree design with `one_for_one`/`rest_for_one`/`one_for_all`, when to use Task vs GenStage vs Broadway), Phoenix LiveView server-rendered interactivity (`mount`/`handle_event`/`handle_info`, real-time updates over PubSub), Ecto (schemas, migrations, changesets, complex joins with `Repo`, transaction safety with `Multi`), testing (ExUnit with mocks, property-based testing with StreamData), and a practical code-review checklist (concurrency safety, fault-tolerance with supervisors, proper error handling, resource cleanup). Honest caveats: guidance only — the agent needs an Elixir/Phoenix project to apply it to; the repo contains nothing but this skill (nothing else to audit in the source). Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: an Elixir/Phoenix project the agent can read and work on — the skill is an expert methodology, not software to install Install "Elixir — OTP and LiveView expert patterns" for me. It gives my agent @mindrally's Elixir playbook: OTP patterns (GenServer state machines, supervision tree design, Task vs GenStage vs Broadway selection), Phoenix LiveView (server-rendered interactivity, mount/handle_event/handle_info, real-time PubSub updates), Ecto (schemas, migrations, changesets, complex Repo joins, Multi transactions), testing (ExUnit with mocks, StreamData property-based tests), and a code-review checklist for concurrency safety and fault tolerance. Apache-2.0-licensed. Repository: https://github.com/mindrally/skills/blob/main/elixir/SKILL.md 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "elixir". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at my Elixir/Phoenix project; nothing else — it's an expert methodology). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.