Databuddy
databuddy-analytics/Databuddy
Integrate Databuddy analytics using the SDK, REST API, or MCP.
A skill your agent uses when building JSON API endpoints — :api pipeline, FallbackController, error rendering, pagination, versioning, Bearer auth.
$ npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide phoenix-json-api --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-json-api .claude/skills/phoenix-json-api && rm -rf skills-srcUse ~/.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/
Install the "phoenix-json-api" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/phoenix-json-api into .claude/skills/phoenix-json-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-json-api", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/phoenix-json-apiType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide phoenix-json-api --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guide.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/phoenix-json-api .agents/skills/phoenix-json-api && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "phoenix-json-api" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/phoenix-json-api into .agents/skills/phoenix-json-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-json-api", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide phoenix-json-api --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guide.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/phoenix-json-api .cursor/skills/phoenix-json-api && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "phoenix-json-api" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/phoenix-json-api into .cursor/skills/phoenix-json-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-json-api", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/j-morgan6/elixir-phoenix-guide.git --path skills/phoenix-json-api--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide phoenix-json-api --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guide.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/phoenix-json-api .gemini/skills/phoenix-json-api && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "phoenix-json-api" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/phoenix-json-api into .gemini/skills/phoenix-json-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-json-api", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install j-morgan6/elixir-phoenix-guide phoenix-json-apiInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guide.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/phoenix-json-api .github/skills/phoenix-json-api && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "phoenix-json-api" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/phoenix-json-api into .github/skills/phoenix-json-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-json-api", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide phoenix-json-api --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/j-morgan6/elixir-phoenix-guide.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/phoenix-json-api .opencode/skills/phoenix-json-api && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "phoenix-json-api" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/phoenix-json-api into .opencode/skills/phoenix-json-api/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phoenix-json-api", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
phoenix-json-apiA skill your agent uses when building JSON API endpoints — :api pipeline, FallbackController, error rendering, pagination, versioning, Bearer auth.
Phoenix JSON API is an agent skill from j-morgan6/elixir-phoenix-guide. Use when building JSON API endpoints — :api pipeline, FallbackController, error rendering, pagination, versioning, Bearer auth.
Its SKILL.md is about 2.8k 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 AI & LLM Engineering, covering LLM observability and REST APIs. The licence is MIT.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit cdfddac. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are elixir and json).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Phoenix JSON API loads about 2.8k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 251 words of instructions outside code blocks.
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.
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.
The full file from j-morgan6/elixir-phoenix-guide at commit cdfddac, republished under its MIT licence (© j-morgan6). 251 words, ~2,805 tokens.
.claude/skills/phoenix-json-api/SKILL.md (or your agent's skills folder).:api pipeline — don't mix HTML and JSON pipelines; API routes skip CSRF, sessions, and browser headers{:error, changeset} must become {"errors": {...}}; never return raw text or HTML errors/api/v1/) — not headers; URL versioning is visible, cacheable, and debuggableFallbackController for consistent error handling — every action returns {:ok, result} or {:error, reason}; the fallback renders errorsAuthorization header — not cookies; API clients don't have browser sessionsjson/2 helper — ensures Content-Type: application/json; avoid render for simple JSON responses# lib/my_app_web/router.ex
defmodule MyAppWeb.Router do
use MyAppWeb, :router
pipeline :api do
plug :accepts, ["json"]
# No :fetch_session, :protect_from_forgery, :put_secure_browser_headers
# APIs use tokens, not sessions
end
pipeline :api_auth do
plug MyAppWeb.Plugs.ApiAuth
end
# Public endpoints (no auth required)
scope "/api/v1", MyAppWeb.API.V1, as: :api_v1 do
pipe_through :api
post "/auth/login", AuthController, :login
post "/auth/register", AuthController, :register
end
# Protected endpoints
scope "/api/v1", MyAppWeb.API.V1, as: :api_v1 do
pipe_through [:api, :api_auth]
resources "/posts", PostController, except: [:new, :edit]
resources "/users", UserController, only: [:index, :show, :update]
end
endControllers return {:ok, result} or {:error, reason} — the FallbackController handles error rendering.
defmodule MyAppWeb.API.V1.PostController do
use MyAppWeb, :controller
alias MyApp.Blog
alias MyApp.Blog.Post
action_fallback MyAppWeb.FallbackController
def index(conn, params) do
page =
case Integer.parse(params["page"] || "1") do
{n, ""} when n > 0 -> n
_ -> 1
end
per_page = Map.get(params, "per_page", "20") |> String.to_integer() |> min(100)
{posts, total} = Blog.list_posts(page: page, per_page: per_page)
conn
|> put_resp_header("x-total-count", to_string(total))
|> json(%{
data: Enum.map(posts, &post_json/1),
meta: %{page: page, per_page: per_page, total: total}
})
end
def show(conn, %{"id" => id}) do
with {:ok, post} <- Blog.get_post(id) do
json(conn, %{data: post_json(post)})
end
end
def create(conn, %{"post" => post_params}) do
with {:ok, %Post{} = post} <- Blog.create_post(post_params) do
conn
|> put_status(:created)
|> put_resp_header("location", ~p"/api/v1/posts/#{post}")
|> json(%{data: post_json(post)})
end
end
def update(conn, %{"id" => id, "post" => post_params}) do
with {:ok, post} <- Blog.get_post(id),
{:ok, %Post{} = updated} <- Blog.update_post(post, post_params) do
json(conn, %{data: post_json(updated)})
end
end
def delete(conn, %{"id" => id}) do
with {:ok, post} <- Blog.get_post(id),
{:ok, _} <- Blog.delete_post(post) do
send_resp(conn, :no_content, "")
end
end
defp post_json(%Post{} = post) do
%{
id: post.id,
title: post.title,
body: post.body,
inserted_at: post.inserted_at,
updated_at: post.updated_at
}
end
endBad:
# Mixing concerns — error handling inline, inconsistent responses
def show(conn, %{"id" => id}) do
case Repo.get(Post, id) do
nil -> conn |> put_status(404) |> text("Not found")
post -> conn |> put_status(200) |> render("show.json", post: post)
end
endCentralized error handling — every error gets a consistent JSON response.
defmodule MyAppWeb.FallbackController do
use MyAppWeb, :controller
# Ecto changeset errors
def call(conn, {:error, %Ecto.Changeset{} = changeset}) do
conn
|> put_status(:unprocessable_entity)
|> json(%{errors: format_changeset_errors(changeset)})
end
# Not found
def call(conn, {:error, :not_found}) do
conn
|> put_status(:not_found)
|> json(%{errors: %{detail: "Not found"}})
end
# Unauthorized — no valid credentials (401)
def call(conn, {:error, :unauthorized}) do
conn
|> put_status(:unauthorized)
|> json(%{errors: %{detail: "Unauthorized"}})
end
# Forbidden — authenticated, but not allowed to do this (403)
def call(conn, {:error, :forbidden}) do
conn
|> put_status(:forbidden)
|> json(%{errors: %{detail: "Forbidden"}})
end
# Generic error
def call(conn, {:error, reason}) when is_binary(reason) do
conn
|> put_status(:bad_request)
|> json(%{errors: %{detail: reason}})
end
defp format_changeset_errors(changeset) do
Ecto.Changeset.traverse_errors(changeset, fn {msg, opts} ->
Regex.replace(~r"%{(\w+)}", msg, fn _, key ->
opts |> Keyword.get(String.to_existing_atom(key), key) |> to_string()
end)
end)
end
endContext functions should return tagged tuples:
defmodule MyApp.Blog do
def get_post(id) do
case Repo.get(Post, id) do
nil -> {:error, :not_found}
post -> {:ok, post}
end
end
enddefmodule MyAppWeb.Plugs.ApiAuth do
import Plug.Conn
def init(opts), do: opts
def call(conn, _opts) do
with ["Bearer " <> token] <- get_req_header(conn, "authorization"),
{:ok, user} <- MyApp.Accounts.verify_api_token(token) do
assign(conn, :current_user, user)
else
_ ->
conn
|> put_status(:unauthorized)
|> Phoenix.Controller.json(%{errors: %{detail: "Unauthorized"}})
|> halt()
end
end
endToken generation in the auth controller:
defmodule MyAppWeb.API.V1.AuthController do
use MyAppWeb, :controller
alias MyApp.Accounts
def login(conn, %{"email" => email, "password" => password}) do
case Accounts.authenticate_user(email, password) do
{:ok, user} ->
token = Accounts.generate_api_token(user)
json(conn, %{data: %{token: token, user_id: user.id}})
{:error, :invalid_credentials} ->
conn
|> put_status(:unauthorized)
|> json(%{errors: %{detail: "Invalid email or password"}})
end
end
endNever return unbounded collections. Cap per_page to prevent abuse.
defmodule MyApp.Blog do
import Ecto.Query
def list_posts(opts \\ []) do
page = Keyword.get(opts, :page, 1)
per_page = Keyword.get(opts, :per_page, 20) |> min(100)
offset = (page - 1) * per_page
posts =
from(p in Post,
order_by: [desc: p.inserted_at],
limit: ^per_page,
offset: ^offset
)
|> Repo.all()
total = Repo.aggregate(Post, :count)
{posts, total}
end
endResponse format:
{
"data": [...],
"meta": {
"page": 1,
"per_page": 20,
"total": 142
}
}Version via URL prefix. It's visible in logs, cacheable by CDNs, and simple to implement.
# router.ex
scope "/api/v1", MyAppWeb.API.V1, as: :api_v1 do
pipe_through [:api, :api_auth]
resources "/posts", PostController, except: [:new, :edit]
end
# When v2 is needed, add a new scope
scope "/api/v2", MyAppWeb.API.V2, as: :api_v2 do
pipe_through [:api, :api_auth]
resources "/posts", PostController, except: [:new, :edit]
endController directory structure:
lib/my_app_web/controllers/api/
├── v1/
│ ├── post_controller.ex
│ ├── user_controller.ex
│ └── auth_controller.ex
└── v2/
└── post_controller.ex # Only modules that changedFor simple responses, use json/2. For complex or reusable serialization, use JSON views.
# Direct — good for simple responses
json(conn, %{data: %{id: post.id, title: post.title}})# lib/my_app_web/controllers/api/v1/post_json.ex
defmodule MyAppWeb.API.V1.PostJSON do
alias MyApp.Blog.Post
def index(%{posts: posts, meta: meta}) do
%{data: for(post <- posts, do: data(post)), meta: meta}
end
def show(%{post: post}) do
%{data: data(post)}
end
def data(%Post{} = post) do
%{
id: post.id,
title: post.title,
body: post.body,
author: author_data(post.author),
inserted_at: post.inserted_at,
updated_at: post.updated_at
}
end
defp author_data(nil), do: nil
defp author_data(author) do
%{id: author.id, name: author.name}
end
end
# In controller — use render with the JSON view
def show(conn, %{"id" => id}) do
with {:ok, post} <- Blog.get_post(id) do
render(conn, :show, post: post)
end
enddefmodule MyAppWeb.API.V1.PostControllerTest do
use MyAppWeb.ConnCase
setup %{conn: conn} do
user = user_fixture()
token = MyApp.Accounts.generate_api_token(user)
conn =
conn
|> put_req_header("accept", "application/json")
|> put_req_header("authorization", "Bearer #{token}")
%{conn: conn, user: user}
end
describe "GET /api/v1/posts" do
test "lists posts with pagination", %{conn: conn} do
for _ <- 1..25, do: post_fixture()
conn = get(conn, ~p"/api/v1/posts?page=1&per_page=10")
response = json_response(conn, 200)
assert length(response["data"]) == 10
assert response["meta"]["total"] == 25
assert response["meta"]["page"] == 1
end
end
describe "POST /api/v1/posts" do
test "creates post with valid data", %{conn: conn} do
attrs = %{"post" => %{"title" => "Test", "body" => "Content"}}
conn = post(conn, ~p"/api/v1/posts", attrs)
assert %{"data" => %{"id" => id, "title" => "Test"}} = json_response(conn, 201)
assert get_resp_header(conn, "location") == ["/api/v1/posts/#{id}"]
end
test "returns errors with invalid data", %{conn: conn} do
attrs = %{"post" => %{"title" => ""}}
conn = post(conn, ~p"/api/v1/posts", attrs)
assert %{"errors" => errors} = json_response(conn, 422)
assert errors["title"] != nil
end
end
describe "unauthenticated requests" do
test "returns 401 without token" do
conn = build_conn()
conn = get(conn, ~p"/api/v1/posts")
assert json_response(conn, 401)["errors"]["detail"] == "Unauthorized"
end
end
endSee ecto-essentials skill for query and changeset patterns.
See security-essentials skill for token handling and auth security.
See testing-essentials skill for comprehensive testing patterns.
© 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
Just SKILL.md in skills/phoenix-json-api of j-morgan6/elixir-phoenix-guide.
Open the folder on GitHubat commit cdfddac
Phoenix JSON API 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Phoenix JSON API this skillj-morgan6/elixir-phoenix-guide | 166 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Databuddydatabuddy-analytics/Databuddy | 1.2k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Phoenix REST APIArize-ai/phoenix | 12k | — | ~286 | Automated safety check: Pass | Custom licence | |
| Backend Dev Guidelineslangfuse/langfuse | 36k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Elixir Expertpass-agent/loomkin | 181 | 1 repos | ~796 | Automated safety check: Pass | MIT | |
| Hex Docs Searchbradleygolden/claude-marketplace-elixir | 176 | — | ~4.1k | Automated safety check: Notes | MIT |
databuddy-analytics/Databuddy
Integrate Databuddy analytics using the SDK, REST API, or MCP.
Arize-ai/phoenix
REST API development for Phoenix. An agent skill from Arize-ai/phoenix.
langfuse/langfuse
Build or review Langfuse backend code. An agent skill from langfuse/langfuse.
pass-agent/loomkin
Expert in Elixir, Phoenix Framework, and OTP. An agent skill from pass-agent/loomkin.
bradleygolden/claude-marketplace-elixir
Research Hex packages (Sobelow, Phoenix, Ecto, Credo, Ash, etc).
SharpAI/DeepCamera
Reolink camera integration — RTSP and HTTP API. An agent skill from SharpAI/DeepCamera.
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.
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.
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.
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.
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.
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.
Categories
A skill your agent uses when building JSON API endpoints — :api pipeline, FallbackController, error rendering, pagination, versioning, Bearer auth. Phoenix JSON API is an agent skill from j-morgan6/elixir-phoenix-guide. Use when building JSON API endpoints — :api pipeline, FallbackController, error rendering, pagination, versioning, Bearer auth.
Phoenix JSON API fits situations like: building JSON API endpoints — :api pipeline; fallbackController; error rendering.
Run `npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a claude-code`. Or copy the skill folder (skills/phoenix-json-api in j-morgan6/elixir-phoenix-guide) into .claude/skills/phoenix-json-api in your project. Claude Code loads it when a task matches its description.
Run `npx skills add j-morgan6/elixir-phoenix-guide --skill phoenix-json-api -a codex`. Or copy the skill folder (skills/phoenix-json-api in j-morgan6/elixir-phoenix-guide) into .agents/skills/phoenix-json-api in your project. Codex loads it when a task matches its description.
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-json-api -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-json-api, .gemini/skills/phoenix-json-api, .github/skills/phoenix-json-api and .opencode/skills/phoenix-json-api in your project.
SKILL.md names no scripts, command-line tools or credentials: Phoenix JSON API is instructions for the agent only.
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.
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.
Phoenix JSON API is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Phoenix JSON API: Databuddy (databuddy-analytics/Databuddy, 1.2k stars), Phoenix REST API (Arize-ai/phoenix, 12k stars), Backend Dev Guidelines (langfuse/langfuse, 36k stars) and Elixir Expert (pass-agent/loomkin, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.