Agent skill

Phoenix Uploads

by j-morgan6 in j-morgan6/elixir-phoenix-guide

A skill your agent uses when implementing file uploads — allowupload, consumeuploadedentries, validation, dev vs production storage (local, S3/:external), serving files.

MITAuto-check passedBackend & APIs

Install Phoenix Uploads

skills CLI
$ npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-uploads -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install j-morgan6/elixir-phoenix-guide phoenix-uploads --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guide.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/phoenix-uploads .claude/skills/phoenix-uploads && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
phoenix-uploads
GitHub stars
166
Token cost
~3.2k tokens
SKILL.md length
592 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when implementing file uploads — allowupload, consumeuploadedentries, validation, dev vs production storage (local, S3/:external), serving files.

  • Works in 7 steps: Define static_paths/0 → Verify Plug.Static Configuration → Sanitize File Paths → …
  • Implementing file uploads — allowupload
  • SKILL.md covers RULES — Follow these with no…, Upload Configuration, Complete Upload Pattern and Error Handling, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Phoenix Uploads is an agent skill from j-morgan6/elixir-phoenix-guide. Use when implementing file uploads — allowupload, consumeuploadedentries, validation, dev vs production storage (local, S3/:external), serving files.

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering File uploads and storage and LLM observability. The licence is MIT.

When your agent uses it

  • Implementing file uploads — allowupload
  • Consumeuploadedentries
  • Dev vs production storage (local

Example prompts

  • “/phoenix-uploads”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Define static_paths/0
  2. Verify Plug.Static Configuration
  3. Sanitize File Paths
  4. Validate File Types
  5. Generate Unique Filenames
  6. Limit File Sizes
  7. Content-Type Headers

What it can do on your machine

Read from SKILL.md and the folder at commit cdfddac. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are elixir and heex).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Phoenix Uploads loads about 3.2k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 592 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from j-morgan6/elixir-phoenix-guide at commit cdfddac, republished under its MIT licence (© j-morgan6). 592 words, ~3,213 tokens.

Download SKILL.mdSave it as .claude/skills/phoenix-uploads/SKILL.md (or your agent's skills folder).
name
phoenix-uploads
description
Use when implementing file uploads — allow_upload, consume_uploaded_entries, validation, dev vs production storage (local, S3/:external), serving files.
file_patterns
**/live/**/*.ex, **/*_live.ex, **/uploads/**/*.ex, **/endpoint.ex, **/*_web.ex
auto_suggest
true

Phoenix File Uploads

RULES — Follow these with no exceptions

⚠️ priv/static/uploads is a DEV-ONLY pattern. In a release/container, priv/static is replaced on every deploy — user uploads are silently lost, and runtime files are never in the digest manifest. In production use object storage (S3 via :external uploads) or a configured writable directory outside the release (e.g. a mounted volume), served by a dedicated Plug.Static.

  1. Default to manual uploads — auto_upload: true works with submit, but entries must be fully uploaded before you consume them; prefer manual uploads unless you need incremental upload UX
  2. Always add upload directory to static_paths() — files won't be accessible without this
  3. Handle upload errors — display error_to_string/1 output in templates
  4. Create upload directories with File.mkdir_p! before saving files
  5. Generate unique filenames — prevent collisions and path traversal attacks
  6. Validate file types server-side — never trust client MIME types
  7. If static_paths() changes don't take effect, restart the server — the code reloader usually recompiles the endpoint on the next request

Upload Configuration

elixir
allow_upload(:upload_name,
  accept: ~w(.jpg .jpeg .png .pdf),
  max_entries: 10,
  max_file_size: 10_000_000
)

Template Requirements:

  • Form with phx-submit event
  • Submit button to trigger upload
  • <.live_file_input> component
  • Progress indicators
Auto Upload (Advanced - Use Sparingly)

Only use auto_upload: true when:

  • Files should upload immediately on selection
  • You have handle_progress/3 callback
  • You consume entries outside form submission

auto_upload: true works with submit, but entries must be fully uploaded before you consume them — check entry.done? / rely on consume_uploaded_entries only after progress completes. Default to manual uploads unless you need incremental upload UX.

Complete Upload Pattern

LiveView Module
elixir
@impl true
def mount(_params, _session, socket) do
  socket =
    socket
    |> assign(:uploaded_files, [])
    |> allow_upload(:photos,
         accept: ~w(.jpg .jpeg .png),
         max_entries: 5,
         max_file_size: 10_000_000
       )

  {:ok, socket}
end

@impl true
def handle_event("validate", _params, socket) do
  {:noreply, socket}
end

@impl true
def handle_event("save", _params, socket) do
  uploaded_files =
    consume_uploaded_entries(socket, :photos, fn %{path: path}, entry ->
      dest = Path.join(["priv", "static", "uploads", safe_filename(entry.client_name)])
      File.mkdir_p!(Path.dirname(dest))
      File.cp!(path, dest)
      {:ok, ~s(/uploads/#{Path.basename(dest)})}
    end)

  # Save to database with uploaded_files paths
  {:noreply, assign(socket, :uploaded_files, uploaded_files)}
end

defp safe_filename(original_name) do
  # Generate unique name to prevent collisions and attacks
  ext = Path.extname(original_name)
  "#{Ecto.UUID.generate()}#{ext}"
end
Template
heex
<%!-- Phoenix 1.8 removed the old simple-form component; use <.form> --%>
<.form for={@form} phx-change="validate" phx-submit="save">
  <.input field={@form[:title]} label="Title" />

  <div>
    <.label>Upload Photos</.label>
    <.live_file_input upload={@uploads.photos} />
  </div>

  <!-- Upload errors -->
  <%= for err <- upload_errors(@uploads.photos) do %>
    <p class="error"><%= error_to_string(err) %></p>
  <% end %>

  <!-- Entry previews and errors -->
  <%= for entry <- @uploads.photos.entries do %>
    <div>
      <.live_img_preview entry={entry} />
      <progress value={entry.progress} max="100"><%= entry.progress %>%</progress>

      <%= for err <- upload_errors(@uploads.photos, entry) do %>
        <p class="error"><%= error_to_string(err) %></p>
      <% end %>
    </div>
  <% end %>

  <:actions>
    <.button phx-disable-with="Uploading...">Upload</.button>
  </:actions>
</.form>

Error Handling

Always implement error_to_string/1:

elixir
defp error_to_string(:too_large), do: "File is too large (max 10MB)"
defp error_to_string(:not_accepted), do: "File type not accepted"
defp error_to_string(:too_many_files), do: "Too many files selected"
defp error_to_string(:external_client_failure), do: "Upload failed"

Static File Serving Configuration

Critical: After uploading files, they MUST be served via static_paths.

Step 1: Define static_paths/0
elixir
# lib/my_app_web.ex
def static_paths do
  ~w(assets fonts images uploads favicon.ico robots.txt)
end

Rule: Any directory you serve files from must be listed here.

Step 2: Verify Plug.Static Configuration
elixir
# lib/my_app_web/endpoint.ex
plug Plug.Static,
  at: "/",
  from: :my_app,
  gzip: false,
  only: MyAppWeb.static_paths()
File Structure

Static files must be in priv/static/:

my_app/
├── priv/
│   └── static/
│       ├── assets/        # CSS, JS (from esbuild)
│       ├── uploads/       # User uploads
│       │   ├── image1.jpg
│       │   └── doc.pdf
│       └── favicon.ico

Serving Uploaded Files

From Templates
heex
<!-- Image -->
<img src="/uploads/photo.jpg" alt="Photo" />

<!-- Document download -->
<.link href="/uploads/document.pdf" download>Download</.link>
From Controllers
elixir
def download(conn, %{"filename" => filename}) do
  # Sanitize filename to prevent path traversal
  safe_name = Path.basename(filename)
  path = Path.join(["priv", "static", "uploads", safe_name])

  if File.exists?(path) and String.starts_with?(path, "priv/static/uploads") do
    send_download(conn, {:file, path}, filename: safe_name)
  else
    conn
    |> put_status(:not_found)
    |> text("File not found")
  end
end

Image Previews

For image uploads, show previews:

heex
<%= for entry <- @uploads.photos.entries do %>
  <div class="preview">
    <.live_img_preview entry={entry} width={200} />
    <button type="button" phx-click="cancel-upload" phx-value-ref={entry.ref}>
      Cancel
    </button>
  </div>
<% end %>
elixir
@impl true
def handle_event("cancel-upload", %{"ref" => ref}, socket) do
  {:noreply, cancel_upload(socket, :photos, ref)}
end

Multiple Upload Slots

You can have multiple upload configurations:

elixir
socket
|> allow_upload(:photos, accept: ~w(.jpg .jpeg .png), max_entries: 5)
|> allow_upload(:documents, accept: ~w(.pdf .docx), max_entries: 3)

External Storage (S3, etc.)

For external storage, use the :external option:

elixir
allow_upload(:photos,
  accept: ~w(.jpg .jpeg .png),
  max_entries: 5,
  external: &presign_upload/2
)

defp presign_upload(entry, socket) do
  # Generate presigned URL for S3
  {:ok, %{uploader: "S3", key: key, url: url}, socket}
end

Troubleshooting

Show full SKILL.md (257 more words)Show less
Files Return 404

Problem: Accessing /uploads/file.jpg returns 404

Fixes:

  1. Check static_paths includes "uploads"
  2. Verify file exists in priv/static/uploads/
  3. If the fix doesn't take effect, restart the server (the code reloader usually recompiles the endpoint on the next request, but a restart guarantees it)
  4. Check file permissions (should be readable)
elixir
# Debug helper
def check_static_file(path) do
  full_path = Path.join(["priv", "static", path])

  cond do
    not File.exists?(full_path) ->
      "File does not exist: #{full_path}"

    not File.readable?(full_path) ->
      "File exists but not readable: #{full_path}"

    true ->
      "File OK: #{full_path}"
  end
end
Files Work in Dev but Not Production

Problem: Uploaded files serve correctly locally but are missing (404) after a production deploy

This is almost always the priv/static/uploads DEV-ONLY pattern described in the rules above — priv/static is replaced on every release deploy, so anything written there at runtime is gone after the next deploy. mix phx.digest does not help here; it only fingerprints assets that existed at build time, not files uploaded at runtime.

Fix: Move uploads to object storage (S3 via :external uploads) or a writable directory outside the release, served by a dedicated Plug.Static. See the warning at the top of this skill.

Security Best Practices

1. Sanitize File Paths

Never use user input directly in file paths:

elixir
# ❌ DANGEROUS - Path traversal attack
def serve_file(conn, %{"path" => user_path}) do
  send_file(conn, 200, "priv/static/#{user_path}")
end

# ✅ SAFE - Validate and constrain
def serve_file(conn, %{"filename" => filename}) do
  safe_name = Path.basename(filename)  # Remove directory traversal
  path = Path.join(["priv", "static", "uploads", safe_name])

  if File.exists?(path) and String.starts_with?(path, "priv/static/uploads") do
    send_file(conn, 200, path)
  else
    send_resp(conn, 404, "Not found")
  end
end
2. Validate File Types

Don't trust client MIME types:

elixir
def validate_file_type(path) do
  # Use a library like `file_type` to verify actual content
  case FileType.from_path(path) do
    {:ok, %{mime_type: "image/" <> _}} -> :ok
    _ -> {:error, :invalid_type}
  end
end
3. Generate Unique Filenames

Prevent collisions and path traversal:

elixir
defp safe_filename(original_name) do
  ext = Path.extname(original_name)
  "#{Ecto.UUID.generate()}#{ext}"
end
4. Limit File Sizes

Set reasonable limits:

elixir
allow_upload(:photos,
  accept: ~w(.jpg .jpeg .png),
  max_entries: 5,
  max_file_size: 10_000_000  # 10MB
)
5. Content-Type Headers

Set proper content types to prevent XSS:

elixir
def serve_image(conn, %{"id" => id}) do
  image = get_image!(id)

  conn
  |> put_resp_header("content-type", image.content_type)
  |> put_resp_header("x-content-type-options", "nosniff")
  |> send_file(200, image.path)
end

Testing Uploads

elixir
test "uploads image successfully", %{conn: conn} do
  {:ok, lv, _html} = live(conn, "/gallery")

  image =
    file_input(lv, "#upload-form", :photos, [
      %{
        name: "test.png",
        content: File.read!("test/fixtures/test.png"),
        type: "image/png"
      }
    ])

  assert render_upload(image, "test.png") =~ "100%"

  lv
  |> form("#upload-form")
  |> render_submit()

  assert has_element?(lv, "img[alt='test.png']")
end

Common Pitfalls

⚠️ Using auto_upload with form submit without checking entry state
elixir
# Risky — consumes entries that may not be done uploading yet
allow_upload(:photos, auto_upload: true, ...)

def handle_event("save", _params, socket) do
  consume_uploaded_entries(socket, :photos, ...)  # Fine only once all entries are done
end
✅ Prefer manual upload unless you need incremental UX
elixir
# DO THIS — simplest correct default
allow_upload(:photos, ...)

def handle_event("save", _params, socket) do
  consume_uploaded_entries(socket, :photos, ...)  # Works!
end
❌ Not handling upload errors
heex
<!-- Missing error display -->
<.live_file_input upload={@uploads.photos} />
✅ Always show errors
heex
<.live_file_input upload={@uploads.photos} />
<%= for err <- upload_errors(@uploads.photos) do %>
  <p class="error"><%= error_to_string(err) %></p>
<% end %>
❌ Forgetting static_paths
elixir
# File saved to priv/static/uploads/
# But "uploads" not in static_paths
def static_paths, do: ~w(assets favicon.ico)  # Missing uploads!
✅ Include upload directory
elixir
def static_paths, do: ~w(assets uploads favicon.ico)

Quick Reference

elixir
# 1. Add directory to static_paths
def static_paths, do: ~w(assets uploads favicon.ico)

# 2. Create directory structure (DEV ONLY — see warning at top of skill;
#    use object storage or a mounted volume in production)
priv/static/uploads/

# 3. Configure upload in mount
allow_upload(:photos, accept: ~w(.jpg .png), max_entries: 5)

# 4. Consume in handle_event
consume_uploaded_entries(socket, :photos, fn %{path: path}, entry ->
  dest = Path.join(["priv", "static", "uploads", safe_filename(entry.client_name)])
  File.mkdir_p!(Path.dirname(dest))
  File.cp!(path, dest)
  {:ok, "/uploads/#{Path.basename(dest)}"}
end)

# 5. Reference in templates
<img src="/uploads/#{filename}" />

# 6. If static_paths() changes don't take effect, restart the server
mix phx.server

Testing

When writing tests for file upload functionality, invoke elixir-phoenix-guide:testing-essentials before writing any _test.exs file.

© j-morgan6, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/phoenix-uploads of j-morgan6/elixir-phoenix-guide.

Open the folder on GitHubat commit cdfddac

Compare with similar skills

Phoenix Uploads next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Phoenix Uploads compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phoenix Uploads this skillj-morgan6/elixir-phoenix-guide166—~3.2kAutomated safety check: PassMIT
Databuddydatabuddy-analytics/Databuddy1.2k—~2.1kAutomated safety check: PassAGPL-3.0
Phoenix GraphqlArize-ai/phoenix12k—~2.2kAutomated safety check: PassCustom licence
Phoenix REST APIArize-ai/phoenix12k—~286Automated safety check: PassCustom licence
Multimodal Dataprep Useropen-edge-platform/edge-ai-libraries169—~2.2kAutomated safety check: PassApache-2.0
Python SDKaiskillstore/marketplace4301 repos~2.8kAutomated safety check: PassNone

Similar skills

  • Databuddy

    databuddy-analytics/Databuddy

    Integrate Databuddy analytics using the SDK, REST API, or MCP.

    1.2k GitHub stars~2.1k tokensUpdated today
    Backend & APIsAuto-check passed
  • Phoenix Graphql

    Arize-ai/phoenix

    Write efficient GraphQL queries against the Phoenix API. An agent skill from Arize-ai/phoenix.

    12k GitHub stars~2.2k tokensUpdated today
    Backend & APIsAuto-check passed
  • Phoenix REST API

    Arize-ai/phoenix

    REST API development for Phoenix. An agent skill from Arize-ai/phoenix.

    12k GitHub stars~286 tokensUpdated today
    Backend & APIsAuto-check passed
  • Multimodal Dataprep User

    open-edge-platform/edge-ai-libraries

    Deploy and consume Intel Multimodal DataPrep from prebuilt images or a repository checkout.

    169 GitHub stars~2.2k tokensUpdated today
    Backend & APIsAuto-check passed
  • Python SDK

    aiskillstore/marketplace

    Python SDK for inference.sh - run AI apps, build agents, and integrate with 150+ models.

    430 GitHub starsUsed in 1 repo~2.8k tokens
    Backend & APIsAuto-check passed
  • Langfuse Rate Limits

    jeremylongshore/tons-of-skills-marketplace

    Implement Langfuse rate limiting, batching, and backoff patterns.

    2.8k GitHub stars~1.8k tokensUpdated today
    Backend & APIsAuto-check passed

More from j-morgan6/elixir-phoenix-guide

All 19 skills in this repo
  • Code Quality

    j-morgan6/elixir-phoenix-guide

    A skill your agent uses when refactoring for duplication, complexity, or dead code — includes the plugin's on-demand analysis scripts.

    166 GitHub stars~1.4k tokensUpdated 3 mo ago
    Auto-check passed
  • Deployment Gotchas

    j-morgan6/elixir-phoenix-guide

    A skill your agent uses when preparing releases or deployment config — runtime.exs vs compile-time config, release migrations, PHXHOST/PHXSERVER, assets, health checks.

    166 GitHub stars~2.6k tokensUpdated 3 mo ago
    Auto-check passed
  • Ecto Changeset Patterns

    j-morgan6/elixir-phoenix-guide

    A skill your agent uses when a resource needs multiple changesets (registration vs update), conditional validation, field transforms, or uniqueness validation — changeset composition.

    166 GitHub stars~2.1k tokensUpdated 3 mo ago
    Auto-check passed
  • Ecto Essentials

    j-morgan6/elixir-phoenix-guide

    A skill your agent uses when defining schemas, writing queries, or creating migrations — schema design, Repo usage, indexes, query composition.

    166 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Ecto Nested Associations

    j-morgan6/elixir-phoenix-guide

    A skill your agent uses when a form or operation manages parent and child records together — castassoc/castembed, onreplace, Ecto.Multi across tables, FK cascade design.

    166 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Elixir Essentials

    j-morgan6/elixir-phoenix-guide

    A skill your agent uses when writing or refactoring core Elixir — pattern matching, case/cond/with, pipes, {:ok, }/{:error, } contracts.

    166 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Phoenix Uploads

What does Phoenix Uploads do?

A skill your agent uses when implementing file uploads — allowupload, consumeuploadedentries, validation, dev vs production storage (local, S3/:external), serving files. Phoenix Uploads is an agent skill from j-morgan6/elixir-phoenix-guide. Use when implementing file uploads — allowupload, consumeuploadedentries, validation, dev vs production storage (local, S3/:external), serving files.

When should I use Phoenix Uploads?

Phoenix Uploads fits situations like: implementing file uploads — allowupload; consumeuploadedentries; dev vs production storage (local.

How do I install Phoenix Uploads in Claude Code?

Run `npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-uploads -a claude-code`. Or copy the skill folder (skills/phoenix-uploads in j-morgan6/elixir-phoenix-guide) into .claude/skills/phoenix-uploads in your project. Claude Code loads it when a task matches its description.

How do I install Phoenix Uploads in Codex?

Run `npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-uploads -a codex`. Or copy the skill folder (skills/phoenix-uploads in j-morgan6/elixir-phoenix-guide) into .agents/skills/phoenix-uploads in your project. Codex loads it when a task matches its description.

Can I use Phoenix Uploads in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-uploads -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/phoenix-uploads, .gemini/skills/phoenix-uploads, .github/skills/phoenix-uploads and .opencode/skills/phoenix-uploads in your project.

What does Phoenix Uploads need to run?

SKILL.md names no scripts, command-line tools or credentials: Phoenix Uploads is instructions for the agent only.

Does Phoenix Uploads access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Phoenix Uploads safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Phoenix Uploads use?

Phoenix Uploads is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Phoenix Uploads use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Phoenix Uploads?

Skills that share tags, products or a category with Phoenix Uploads: Databuddy (databuddy-analytics/Databuddy, 1.2k stars), Phoenix Graphql (Arize-ai/phoenix, 12k stars), Phoenix REST API (Arize-ai/phoenix, 12k stars) and Multimodal Dataprep User (open-edge-platform/edge-ai-libraries, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phoenix Uploads?

j-morgan6 (a GitHub user) maintains it in j-morgan6/elixir-phoenix-guide, which has 166 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on July 6, 2026.

Source: j-morgan6/elixir-phoenix-guide on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.