Skip to content
Back to search

elixir-agent-tools

MarketplaceWorks with Claude CodeGitHub

Elixir development skills with optional Mix checks and Expert language server integration

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/georgeguimaraes--elixir-agent-tools/badge.svg)](/listings/georgeguimaraes--elixir-agent-tools)

HTML

<a href="/listings/georgeguimaraes--elixir-agent-tools"><img src="/api/listings/georgeguimaraes--elixir-agent-tools/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Install all five skills with the [Skills CLI](https://github.com/vercel-labs/skills) and choose your agent when prompted. Works with Codex, Claude Code, OpenCode, and other supported agents:

npx skills add georgeguimaraes/elixir-agent-tools --skill '*'

Add `-g` to make the skills available across projects. Start a new session after installation. Mix checks and code navigation are [optional tools](#optional-tools) you can add later.

<details> <summary>Alternative: native Claude Code or Codex plugin</summary>

Install the same five skills as a plugin. Choose this or `npx skills` to avoid duplicate skills.

Claude Code

claude plugin marketplace add georgeguimaraes/elixir-agent-tools
claude plugin install elixir-dev@elixir-agent-tools

Codex

codex plugin marketplace add georgeguimaraes/elixir-agent-tools
codex plugin add elixir-dev@elixir-agent-tools

</details>

<details> <summary>Manual installation</summary>

For agents that discover skills under `~/.agents/skills`, clone this repository into a persistent location and link each skill:

git clone https://github.com/georgeguimaraes/elixir-agent-tools.git "$HOME/.local/share/elixir-agent-tools"
mkdir -p "$HOME/.agents/skills"
for skill in elixir phoenix ecto otp oban; do
  ln -s "$HOME/.local/share/elixir-agent-tools/plugins/elixir-dev/skills/$skill" "$HOME/.agents/skills/$skill"
done

If a destination already exists, inspect it before replacing it. Start a new session after installation. Updating the clone updates the linked skills.

For other agents with [Agent Skills support](https://agentskills.io), install the individual folders from `plugins/elixir-dev/skills/` in that agent's skill directory.

</details>

<details> <summary>Try a local checkout in Codex</summary>

Register the local directory instead of the GitHub repository:

codex plugin marketplace add /path/to/elixir-agent-tools
codex plugin add elixir-dev@elixir-agent-tools

Start a new session after installation.

</details>

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 80 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "elixir-agent-tools",
  3. "owner": {
  4. "name": "George Guimaraes"
  5. },
  6. "metadata": {
  7. "description": "Elixir development skills with optional Mix checks and Expert language server integration",
  8. "pluginRoot": "./plugins",
  9. "version": "4.0.0"
  10. },
  11. "plugins": [
  12. {
  13. "name": "elixir-lsp",
  14. "source": "./plugins/elixir-lsp",
  15. "description": "Elixir Language Server integration for go-to-definition, references, and hover docs",
  16. "category": "lsp",
  17. "keywords": [
  18. "elixir",
  19. "lsp",
  20. "language-server",
  21. "intellisense",
  22. "autocomplete"
  23. ]
  24. },
  25. {
  26. "name": "elixir-dev",
  27. "source": "./plugins/elixir-dev",
  28. "description": "Development guidance for Elixir, Phoenix, Ecto, OTP, and Oban",
  29. "category": "skills",
  30. "keywords": [
  31. "elixir",
  32. "phoenix",
  33. "ecto",
  34. "otp",
  35. "oban",
  36. "liveview",
  37. "genserver"
  38. ]
  39. },
  40. {
  41. "name": "mix-compile",
  42. "source": "./plugins/mix-compile",
  43. "description": "Auto-compile Elixir files with warnings-as-errors after edits",
  44. "category": "hooks",
  45. "keywords": [
  46. "elixir",
  47. "mix",
  48. "compile",
  49. "warnings",
  50. "errors"
  51. ]
  52. },
  53. {
  54. "name": "mix-format",
  55. "source": "./plugins/mix-format",
  56. "description": "Auto-format Elixir files with mix format after edits",
  57. "category": "hooks",
  58. "keywords": [
  59. "elixir",
  60. "mix",
  61. "format",
  62. "formatting",
  63. "code-style"
  64. ]
  65. },
  66. {
  67. "name": "mix-credo",
  68. "source": "./plugins/mix-credo",
  69. "description": "Run Credo static analysis after editing Elixir files",
  70. "category": "hooks",
  71. "keywords": [
  72. "elixir",
  73. "mix",
  74. "credo",
  75. "linting",
  76. "code-quality"
  77. ]
  78. }
  79. ]
  80. }
README.md · README · 207 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Elixir Agent Tools
  2. Elixir development guidance for coding agents, with optional Mix checks and Expert language server integration.
  3. Five skills covering language idioms, Phoenix interfaces, Ecto persistence, OTP processes, and Oban jobs. Install them with `npx skills`, then add optional plugins when you want automatic checks or code navigation.
  4. **These skills are small on purpose. Every instruction must change the agent's behavior.** Modern coding agents already know the basics. Their context should go toward your code and your problem. We keep only guidance that changes a decision or prevents a demonstrated mistake. If the agent would do the same thing without an instruction, that instruction doesn't belong here.
  5. ## Installation
  6. Install all five skills with the [Skills CLI](https://github.com/vercel-labs/skills) and choose your agent when prompted. Works with Codex, Claude Code, OpenCode, and other supported agents:
  7. ```bash
  8. npx skills add georgeguimaraes/elixir-agent-tools --skill '*'
  9. ```
  10. Add `-g` to make the skills available across projects. Start a new session after installation. Mix checks and code navigation are [optional tools](#optional-tools) you can add later.
  11. <details>
  12. <summary>Alternative: native Claude Code or Codex plugin</summary>
  13. Install the same five skills as a plugin. Choose this or `npx skills` to avoid duplicate skills.
  14. ### Claude Code
  15. ```bash
  16. claude plugin marketplace add georgeguimaraes/elixir-agent-tools
  17. claude plugin install elixir-dev@elixir-agent-tools
  18. ```
  19. ### Codex
  20. ```bash
  21. codex plugin marketplace add georgeguimaraes/elixir-agent-tools
  22. codex plugin add elixir-dev@elixir-agent-tools
  23. ```
  24. </details>
  25. <details>
  26. <summary>Manual installation</summary>
  27. For agents that discover skills under `~/.agents/skills`, clone this repository into a persistent location and link each skill:
  28. ```bash
  29. git clone https://github.com/georgeguimaraes/elixir-agent-tools.git "$HOME/.local/share/elixir-agent-tools"
  30. mkdir -p "$HOME/.agents/skills"
  31. for skill in elixir phoenix ecto otp oban; do
  32. ln -s "$HOME/.local/share/elixir-agent-tools/plugins/elixir-dev/skills/$skill" "$HOME/.agents/skills/$skill"
  33. done
  34. ```
  35. If a destination already exists, inspect it before replacing it. Start a new session after installation. Updating the clone updates the linked skills.
  36. For other agents with [Agent Skills support](https://agentskills.io), install the individual folders from `plugins/elixir-dev/skills/` in that agent's skill directory.
  37. </details>
  38. <details>
  39. <summary>Try a local checkout in Codex</summary>
  40. Register the local directory instead of the GitHub repository:
  41. ```bash
  42. codex plugin marketplace add /path/to/elixir-agent-tools
  43. codex plugin add elixir-dev@elixir-agent-tools
  44. ```
  45. Start a new session after installation.
  46. </details>
  47. ## Elixir skills
  48. Each skill has its own discovery description. The agent can load several skills for a task that crosses domains, such as a LiveView form backed by an Ecto changeset. There is no startup hook or mandatory routing skill.
  49. | Skill | Scope | Example request |
  50. |-------|-------|-----------------|
  51. | [elixir](plugins/elixir-dev/skills/elixir/SKILL.md) | Functions, modules, data structures, pattern matching, error handling | "Refactor this nested case expression" |
  52. | [phoenix](plugins/elixir-dev/skills/phoenix/SKILL.md) | LiveView, components, HTTP endpoints, Plug, channels, PubSub | "Keep this LiveView filter in sync with the URL" |
  53. | [ecto](plugins/elixir-dev/skills/ecto/SKILL.md) | Schemas, changesets, queries, transactions, migrations, data access | "Fix the N+1 queries on this page" |
  54. | [otp](plugins/elixir-dev/skills/otp/SKILL.md) | Processes, supervision, runtime concurrency, ETS, Broadway | "Find the bottleneck in this GenServer" |
  55. | [oban](plugins/elixir-dev/skills/oban/SKILL.md) | Durable jobs, retries, scheduling, uniqueness, Oban Pro workflows | "Send these emails in a job that retries failures" |
  56. OTP covers work and state managed by running processes. Oban covers jobs that need persistence, retry policies, or scheduling. Phoenix owns interface behavior, while Ecto owns the persistence behind it.
  57. ### Upgrading to elixir-dev 3.0
  58. Skill names now use their domain directly: `elixir`, `phoenix`, `ecto`, `otp`, and `oban`. Remove the `-thinking` suffix from explicit skill references in your prompts and agent instructions. The `using-elixir-skills` router and its startup hook have been removed.
  59. The plugin is now named `elixir-dev` and the marketplace is `elixir-agent-tools`. If you installed from the old Claude Code marketplace, uninstall the plugins you used from `claude-code-elixir`, remove that marketplace, and add `georgeguimaraes/elixir-agent-tools`. Reinstall your chosen plugins with the new marketplace ID using the installation commands above. The old `elixir` plugin is replaced by `elixir-dev`.
  60. Update any explicit plugin-qualified skill references to use the new bundle name.
  61. If you installed skills manually, replace your old skill links or copies with the renamed folders under `plugins/elixir-dev/skills/`.
  62. ### Sources
  63. The skills draw on Elixir and Erlang documentation, framework guides, and talks about application design:
  64. - [José Valim - Gang of None](https://www.youtube.com/watch?v=4yAaHV9wQE4)
  65. - [Saša Jurić - The Soul of Erlang and Elixir](https://www.youtube.com/watch?v=JvBT4XBdoUE)
  66. - [Saša Jurić - Clarity](https://www.youtube.com/watch?v=6sNmJtoKDCo)
  67. - [Designing Elixir Systems with OTP](https://pragprog.com/titles/jgotp/designing-elixir-systems-with-otp/)
  68. - [Official Elixir Guides](https://elixir-lang.org/getting-started/)
  69. - [Phoenix 1.8 Scopes](https://hexdocs.pm/phoenix/scopes.html)
  70. - [Phoenix LiveView Docs](https://hexdocs.pm/phoenix_live_view)
  71. - [Stephen Bussey - Real-Time Phoenix](https://pragprog.com/titles/sbsockets/real-time-phoenix/)
  72. - [Phoenix Contexts Guide](https://hexdocs.pm/phoenix/contexts.html)
  73. - [German Velasco - DDD for Phoenix Contexts](https://www.youtube.com/watch?v=mSgZ2LJXfew) (ElixirConf 2024)
  74. - [Ecto Multi-Tenancy Guide](https://hexdocs.pm/ecto/multi-tenancy-with-query-prefixes.html)
  75. - [Erlang OTP Design Principles](https://www.erlang.org/doc/system/design_principles.html)
  76. - [Elixir GenServer Docs](https://hexdocs.pm/elixir/GenServer.html)
  77. - [Elixir School - OTP Concurrency](https://elixirschool.com/en/lessons/advanced/otp_concurrency)
  78. - [Saša Jurić - Elixir in Action](https://www.manning.com/books/elixir-in-action-third-edition)
  79. ## Optional tools
  80. These tools use native plugins. Add the marketplace for your agent below, then install any tools you want. The skills work without them.
  81. | Plugin | What you get | Requirements |
  82. |--------|--------------|--------------|
  83. | [mix-format](#mix-format) | Run `mix format` after edits to `.ex` and `.exs` files | Claude Code or Codex, Bash, Elixir/Mix, a Mix project |
  84. | [mix-compile](#mix-compile) | Compile with `--warnings-as-errors` after edits to `.ex` files | Claude Code or Codex, Bash, Elixir/Mix, a Mix project |
  85. | [mix-credo](#mix-credo) | Run Credo after edits to `.ex` and `.exs` files | Claude Code or Codex, Bash, Elixir/Mix, Credo in the project |
  86. | [elixir-lsp](#elixir-lsp) | Code navigation and diagnostics through Expert | Claude Code, Expert, Python 3 |
  87. <details>
  88. <summary>Install tools in Claude Code</summary>
  89. Add the marketplace once:
  90. ```bash
  91. claude plugin marketplace add georgeguimaraes/elixir-agent-tools
  92. ```
  93. Run only the commands for the tools you want:
  94. ```bash
  95. claude plugin install mix-format@elixir-agent-tools
  96. claude plugin install mix-compile@elixir-agent-tools
  97. claude plugin install mix-credo@elixir-agent-tools
  98. claude plugin install elixir-lsp@elixir-agent-tools
  99. ```
  100. </details>
  101. <details>
  102. <summary>Install tools in Codex</summary>
  103. Add the marketplace once:
  104. ```bash
  105. codex plugin marketplace add georgeguimaraes/elixir-agent-tools
  106. ```
  107. Run only the commands for the checks you want:
  108. ```bash
  109. codex plugin add mix-format@elixir-agent-tools
  110. codex plugin add mix-compile@elixir-agent-tools
  111. codex plugin add mix-credo@elixir-agent-tools
  112. ```
  113. Use `/hooks` in Codex to review and trust the installed hook commands. Codex requires hook trust separately from plugin installation. See the [Codex hooks documentation](https://learn.chatgpt.com/docs/hooks). The Expert LSP plugin remains Claude Code only.
  114. </details>
  115. The Mix hooks support macOS and Linux, including WSL on Windows. They use Bash 3.2+, standard Unix tools, and the OS file-lock utility: `lockf` on macOS or `flock` on Linux/WSL. JSON parsing is bundled, so the Mix hooks need no jq, Python, uv, or newer Elixir version.
  116. The three Mix plugins share a Bash runner and a bundled [JSON.sh](https://github.com/dominictarr/JSON.sh) parser. They handle Claude Code's `Edit`, `MultiEdit`, and `Write` events and Codex's `apply_patch` events, including patches spanning multiple files or projects. Shell commands that write files do not trigger these edit hooks.
  117. Checks run synchronously and return failures as context to the agent. The plugins serialize their Mix commands per project, but hook execution order is not guaranteed. Formatting is not guaranteed to finish before compilation or Credo starts. Hooks have bounded waits and report timeouts. Mix plugins 2.0 replace the old single-file scripts and asynchronous Credo hook.
  118. ### mix-format
  119. Runs `mix format` on surviving edited `.ex` and `.exs` files, using the nearest parent `mix.exs` to locate each project. Reports formatting failures.
  120. ### mix-compile
  121. Runs `mix compile --warnings-as-errors` once per affected Mix project after editing an `.ex` file. Deletions and both sides of a move also trigger compilation. Reports compiler warnings and errors. Edits to `.exs` scripts and tests don't trigger compilation.
  122. Skips compilation when `lsof` detects a BEAM process running from the project directory, to avoid competing with a running server or Mix task.
  123. ### mix-credo
  124. Runs `mix credo` for each surviving edited `.ex` or `.exs` file using the project's Credo configuration. Reports code quality issues and skips the check if the Credo task isn't installed. Dependency and project failures remain visible.
  125. ### elixir-lsp
  126. Connects Claude Code to [Expert](https://github.com/elixir-lang/expert) for navigation and compiler diagnostics in `.ex`, `.exs`, `.heex`, and `.leex` files.
  127. Install the `expert` binary using the [Expert installation guide](https://expert-lsp.org/docs/installation) and make sure it's on your PATH. The bundled wrapper also requires Python 3.
  128. The wrapper works around Claude Code's handling of server-initiated LSP requests, including `client/registerCapability` ([upstream issue](https://github.com/anthropics/claude-code/issues/32595)). See [expert-wrapper](plugins/elixir-lsp/bin/expert-wrapper) for the implementation.
  129. ## Developing the hooks
  130. Edit the canonical runner and parser helpers under `scripts/mix-hooks/`, then run `bash scripts/sync-mix-hooks.sh` to bundle them into the three independently installable plugins. The bundled JSON.sh source and its MIT license live under `vendor/` in each copy.
  131. Run `bash test/verify-plugins.sh` to check package structure and bundle consistency. Run `elixir test/test_mix_hooks.exs` for behavioral tests with isolated plugin installations and fake Mix commands. The development checks need Bash, Elixir, and perl. They don't affect the Mix hooks themselves, which use Bash only.
  132. ## License
  133. Copyright (c) 2025 George Guimarães
  134. Licensed under the Apache License, Version 2.0. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.