How do I install the Using Elixir Skills skill?

Run npx skillmds@latest add tomevault-io/using-elixir-skills in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Using Elixir Skills safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Using Elixir Skills?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Using Elixir Skills free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Using Elixir Skills?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Using Elixir Skills by tomevault-io

Name: Using Elixir Skills
Author: tomevault-io

Using Elixir Skills

This skill should be used when the user works on any .ex or .exs file, mentions Elixir/Phoenix/Ecto/OTP, the project has a mix.exs, or asks "which skill should I use", "new to Elixir", "help with Elixir". Routes to the correct thinking skill BEFORE exploring code. Triggers on "implement", "add", "fix", "refactor" in Elixir projects. Use when this capability is needed.

tomevault-io 2cc2773 2 files · 3.1 KB Updated Sep 17, 2026

File contents

THIS IS NOT OPTIONAL. Skills tell you HOW to explore and WHAT to look for. You cannot rationalize your way out of this.

The Rule

Elixir/Phoenix/OTP task → Invoke skill FIRST → Then explore/research → Then write code

Skills come before exploration. The skills tell you what patterns to look for, what questions to ask, and what anti-patterns to avoid. Exploring without the skill means you don't know what you're looking for.

Skill Triggers

Trigger Phrases	Skill to Invoke
code, implement, write, design, architecture, structure, pattern	`elixir-thinking`
LiveView, Plug, PubSub, mount, channel, socket, component	`phoenix-thinking`
context, schema, Ecto, changeset, preload, Repo, migration	`ecto-thinking`
GenServer, supervisor, Task, ETS, bottleneck, Broadway	`otp-thinking`
Oban, workflow, job queue, cascade, graft, background job, async job	`oban-thinking`

Red Flags

These thoughts mean STOP—invoke the skill:

Thought	Reality
"Let me explore the codebase first"	Skills tell you WHAT to look for. Invoke first.
"Let me understand the code first"	Skills guide understanding. Invoke first.
"But first, let me..."	No. Skills come first. Always.
"I'll add a process to organize this"	Processes are for runtime, not organization.
"GenServer is the Elixir way"	GenServer is a bottleneck by design.
"I'll query in mount"	mount is called twice.
"Task.async is simpler"	Use Task.Supervisor in production.
"I know Elixir well enough"	These skills contain paradigm shifts. Invoke them.

Source: georgeguimaraes/claude-code-elixir — distributed by TomeVault.

---name: using-elixir-skillsdescription: This skill should be used when the user works on any .ex or .exs file, mentions Elixir/Phoenix/Ecto/OTP, the project has a mix.exs, or asks "which skill should I use", "new to Elixir", "help with Elixir". Routes to the correct thinking skill BEFORE exploring code. Triggers on "implement", "add", "fix", "refactor" in Elixir projects. Use when this capability is needed.---<EXTREMELY-IMPORTANT>If the task involves Elixir, Phoenix, or OTP code, you MUST invoke the relevant skill BEFORE doing ANYTHING else—including exploring the codebase.THIS IS NOT OPTIONAL. Skills tell you HOW to explore and WHAT to look for. You cannot rationalize your way out of this.</EXTREMELY-IMPORTANT>## The Rule```Elixir/Phoenix/OTP task → Invoke skill FIRST → Then explore/research → Then write code```**Skills come before exploration.** The skills tell you what patterns to look for, what questions to ask, and what anti-patterns to avoid. Exploring without the skill means you don't know what you're looking for.## Skill Triggers| Trigger Phrases | Skill to Invoke ||-----------------|-----------------|| code, implement, write, design, architecture, structure, pattern | `elixir-thinking` || LiveView, Plug, PubSub, mount, channel, socket, component | `phoenix-thinking` || context, schema, Ecto, changeset, preload, Repo, migration | `ecto-thinking` || GenServer, supervisor, Task, ETS, bottleneck, Broadway | `otp-thinking` || Oban, workflow, job queue, cascade, graft, background job, async job | `oban-thinking` |## Red FlagsThese thoughts mean STOP—invoke the skill:| Thought | Reality ||---------|---------|| "Let me explore the codebase first" | Skills tell you WHAT to look for. Invoke first. || "Let me understand the code first" | Skills guide understanding. Invoke first. || "But first, let me..." | No. Skills come first. Always. || "I'll add a process to organize this" | Processes are for runtime, not organization. || "GenServer is the Elixir way" | GenServer is a bottleneck by design. || "I'll query in mount" | mount is called twice. || "Task.async is simpler" | Use Task.Supervisor in production. || "I know Elixir well enough" | These skills contain paradigm shifts. Invoke them. |---> Source: [georgeguimaraes/claude-code-elixir](https://github.com/georgeguimaraes/claude-code-elixir) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions