Caveman Gateway Setup
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
A skill your agent uses when adding logging, metrics, or instrumentation — structured Logger usage, telemetry handler attachment, Ecto/Phoenix telemetry events.
$ npx skills add j-morgan6/elixir-phoenix-guide --skill telemetry-essentials -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide telemetry-essentials --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/telemetry-essentials .claude/skills/telemetry-essentials && 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 "telemetry-essentials" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/telemetry-essentials into .claude/skills/telemetry-essentials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry-essentials", 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/telemetry-essentialsType 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 telemetry-essentials -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide telemetry-essentials --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/telemetry-essentials .agents/skills/telemetry-essentials && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "telemetry-essentials" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/telemetry-essentials into .agents/skills/telemetry-essentials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry-essentials", 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 telemetry-essentials -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide telemetry-essentials --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/telemetry-essentials .cursor/skills/telemetry-essentials && 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 "telemetry-essentials" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/telemetry-essentials into .cursor/skills/telemetry-essentials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry-essentials", 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/telemetry-essentials--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 telemetry-essentials -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install j-morgan6/elixir-phoenix-guide telemetry-essentials --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/telemetry-essentials .gemini/skills/telemetry-essentials && 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 "telemetry-essentials" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/telemetry-essentials into .gemini/skills/telemetry-essentials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry-essentials", 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 telemetry-essentialsInstalls 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 telemetry-essentials -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/telemetry-essentials .github/skills/telemetry-essentials && 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 "telemetry-essentials" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/telemetry-essentials into .github/skills/telemetry-essentials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry-essentials", 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 telemetry-essentials -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 telemetry-essentials --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/telemetry-essentials .opencode/skills/telemetry-essentials && 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 "telemetry-essentials" agent skill from https://github.com/j-morgan6/elixir-phoenix-guide/tree/main/skills/telemetry-essentials into .opencode/skills/telemetry-essentials/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "telemetry-essentials", 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.
telemetry-essentialsA skill your agent uses when adding logging, metrics, or instrumentation — structured Logger usage, telemetry handler attachment, Ecto/Phoenix telemetry events.
Telemetry Essentials is an agent skill from j-morgan6/elixir-phoenix-guide. Use when adding logging, metrics, or instrumentation — structured Logger usage, telemetry handler attachment, Ecto/Phoenix telemetry events.
Its SKILL.md is about 2.7k 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 DevOps & Cloud, covering Observability and LLM observability. The licence is MIT.
6 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).
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.
Telemetry Essentials loads about 2.7k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 385 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). 385 words, ~2,707 tokens.
.claude/skills/telemetry-essentials/SKILL.md (or your agent's skills folder).Logger.info("action", key: value)) — never string interpolation in log messages; structured logs are searchable and parseableApplication.start/2 — :telemetry.attach/4 with an existing handler ID returns {:error, :already_exists}, so it never double-attaches; attach at boot anyway, since handlers detach permanently if they raise and boot-time attachment gives them a stable lifecycleEcto.Repo telemetry events for query monitoring — don't wrap every query manually; Ecto already emits eventsPhoenix.LiveDashboard in dev/staging — it's free observability with zero code:debug level in production — it includes query parameters and PIIStructured logs can be filtered, searched, and aggregated. String-interpolated logs cannot.
Bad:
# String interpolation — unsearchable, inconsistent format
Logger.info("User #{user.id} created order #{order.id} for $#{order.total}")
Logger.error("Failed to process payment for user #{user.id}: #{inspect(reason)}")Good:
# Structured logging — searchable, parseable by log aggregators
Logger.info("Order created", user_id: user.id, order_id: order.id, total: order.total)
Logger.error("Payment failed", user_id: user.id, reason: inspect(reason))Keyword data goes to Logger metadata and is dropped unless whitelisted — add the keys to
config :logger, :default_formatter, metadata: [...] (or metadata: :all in dev). Passing
user_id: user.id doesn't help if :user_id isn't in that list — it's silently discarded.
Set metadata once per request — it's automatically included in all subsequent log calls.
# In a Plug (added to your endpoint or router pipeline)
defmodule MyAppWeb.Plugs.RequestMetadata do
import Plug.Conn
def init(opts), do: opts
def call(conn, _opts) do
Logger.metadata(
request_id: conn.assigns[:request_id] || Ecto.UUID.generate(),
remote_ip: to_string(:inet.ntoa(conn.remote_ip))
)
conn
end
end
# In a LiveView mount
@impl true
def mount(_params, _session, socket) do
if connected?(socket) do
Logger.metadata(user_id: socket.assigns.current_user.id)
end
{:ok, socket}
end# config/prod.exs
config :logger, :console,
format: {LogfmtEx, :format}, # Or Jason-based formatter
metadata: [:request_id, :user_id, :module, :function]The :telemetry library is the standard for metrics in the BEAM ecosystem. Libraries (Ecto, Phoenix, Oban) emit events — you attach handlers.
# An event has: name (list of atoms), measurements (map), metadata (map)
:telemetry.execute(
[:my_app, :orders, :created], # event name
%{count: 1, total_cents: 4999}, # measurements
%{user_id: user.id, source: :web} # metadata
):telemetry.attach/4 called with an existing handler ID returns {:error, :already_exists} —
it never double-attaches. Attach at boot anyway: handlers detach permanently if they raise, and
boot-time attachment gives them a stable lifecycle instead of one tied to a GenServer that may
restart independently.
Bad:
# In a GenServer init — ties the handler's lifecycle to this process instead of boot;
# if the handler function ever raises, it detaches permanently and silently
defmodule MyApp.MetricsServer do
def init(_) do
:telemetry.attach("order-handler", [:my_app, :orders, :created], &handle/4, nil)
{:ok, %{}}
end
endGood:
# In application.ex — runs once at boot
defmodule MyApp.Application do
use Application
@impl true
def start(_type, _args) do
MyApp.Telemetry.attach_handlers()
children = [
MyApp.Repo,
MyAppWeb.Endpoint
]
Supervisor.start_link(children, strategy: :one_for_one)
end
end
# lib/my_app/telemetry.ex
defmodule MyApp.Telemetry do
require Logger
def attach_handlers do
:telemetry.attach_many("my-app-handlers", [
[:my_app, :orders, :created],
[:my_app, :payments, :processed],
[:my_app, :payments, :failed]
], &handle_event/4, nil)
end
def handle_event([:my_app, :orders, :created], measurements, metadata, _config) do
Logger.info("Order created",
total_cents: measurements.total_cents,
user_id: metadata.user_id
)
end
def handle_event([:my_app, :payments, :failed], _measurements, metadata, _config) do
Logger.error("Payment failed",
user_id: metadata.user_id,
reason: metadata.reason
)
end
endFor timing operations:
def process_order(order) do
:telemetry.span([:my_app, :orders, :process], %{order_id: order.id}, fn ->
result = do_process(order)
{result, %{order_id: order.id, status: :completed}}
end)
end
# Emits two events:
# [:my_app, :orders, :process, :start] — with measurements: %{system_time: ...}
# [:my_app, :orders, :process, :stop] — with measurements: %{duration: ...}
# [:my_app, :orders, :process, :exception] — if an exception is raisedEcto automatically emits telemetry events for every query. You don't need to instrument queries manually.
# Ecto emits: [:my_app, :repo, :query]
# Measurements: %{
# total_time: integer, # Total time in native units
# decode_time: integer, # Time decoding results
# query_time: integer, # Time executing the query
# queue_time: integer, # Time waiting for a connection
# idle_time: integer # Time the connection was idle
# }
# Metadata: %{
# query: "SELECT ...",
# source: "users",
# repo: MyApp.Repo,
# result: {:ok, %Postgrex.Result{}} | {:error, ...}
# }defmodule MyApp.Telemetry do
require Logger
def attach_handlers do
:telemetry.attach(
"ecto-slow-query",
[:my_app, :repo, :query],
&handle_slow_query/4,
%{threshold_ms: 100}
)
end
def handle_slow_query(_event, measurements, metadata, %{threshold_ms: threshold}) do
duration_ms = System.convert_time_unit(measurements.total_time, :native, :millisecond)
if duration_ms > threshold do
Logger.warning("Slow query",
duration_ms: duration_ms,
source: metadata.source,
query: metadata.query
)
end
end
endPhoenix emits events for the request lifecycle.
# Request events:
# [:phoenix, :endpoint, :start]
# [:phoenix, :endpoint, :stop]
# [:phoenix, :router_dispatch, :start]
# [:phoenix, :router_dispatch, :stop]
# LiveView events:
# [:phoenix, :live_view, :mount, :start]
# [:phoenix, :live_view, :mount, :stop]
# [:phoenix, :live_view, :handle_event, :start]
# [:phoenix, :live_view, :handle_event, :stop]
# Channel events:
# [:phoenix, :channel_joined]
# [:phoenix, :channel_handled_in]Phoenix.LiveDashboard provides free observability with zero code.
# mix.exs — add dependency (already included in new Phoenix projects)
{:phoenix_live_dashboard, "~> 0.8"}
# router.ex
import Phoenix.LiveDashboard.Router
scope "/" do
pipe_through :browser
# Only in dev/staging — never expose in production without auth
live_dashboard "/dashboard",
metrics: MyAppWeb.Telemetry,
ecto_repos: [MyApp.Repo],
ecto_psql_extras_options: [long_running_queries: [threshold: "200 milliseconds"]]
end# lib/my_app_web/telemetry.ex
defmodule MyAppWeb.Telemetry do
use Supervisor
import Telemetry.Metrics
def start_link(arg) do
Supervisor.start_link(__MODULE__, arg, name: __MODULE__)
end
@impl true
def init(_arg) do
children = [
{:telemetry_poller, measurements: periodic_measurements(), period: 10_000}
]
Supervisor.init(children, strategy: :one_for_one)
end
def metrics do
[
# Phoenix metrics
summary("phoenix.endpoint.stop.duration", unit: {:native, :millisecond}),
summary("phoenix.router_dispatch.stop.duration", unit: {:native, :millisecond}),
# Ecto metrics
summary("my_app.repo.query.total_time", unit: {:native, :millisecond}),
summary("my_app.repo.query.queue_time", unit: {:native, :millisecond}),
# VM metrics
summary("vm.memory.total", unit: :byte),
summary("vm.total_run_queue_lengths.total"),
# Custom business metrics
counter("my_app.orders.created.count"),
summary("my_app.payments.processed.duration", unit: {:native, :millisecond})
]
end
defp periodic_measurements do
[
{MyApp.Metrics, :dispatch_queue_depth, []}
]
end
endEmit telemetry events from your contexts for important business operations.
defmodule MyApp.Orders do
def create_order(attrs) do
:telemetry.span([:my_app, :orders, :create], %{}, fn ->
case %Order{}
|> Order.changeset(attrs)
|> Repo.insert() do
{:ok, order} ->
:telemetry.execute([:my_app, :orders, :created], %{
count: 1,
total_cents: order.total_cents
}, %{user_id: order.user_id})
{{:ok, order}, %{status: :ok}}
{:error, changeset} ->
{{:error, changeset}, %{status: :error}}
end
end)
end
end# mix.exs
{:telemetry_metrics_prometheus, "~> 1.1"}
# application.ex children
TelemetryMetricsPrometheus.child_spec(metrics: MyAppWeb.Telemetry.metrics())
# Exposes /metrics endpoint for Prometheus scraping# mix.exs
{:telemetry_metrics_statsd, "~> 0.7"}
# application.ex children
{TelemetryMetricsStatsd, metrics: MyAppWeb.Telemetry.metrics()}Default to :info in production — :debug logs SQL query parameters, which is a PII risk.
Production log level config lives in the deployment-gotchas skill (§7).
See deployment-gotchas skill for production configuration patterns.
See security-essentials skill for sensitive data logging rules.
See otp-essentials skill for process monitoring 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/telemetry-essentials of j-morgan6/elixir-phoenix-guide.
Open the folder on GitHubat commit cdfddac
Telemetry Essentials 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 |
|---|---|---|---|---|---|---|
| Telemetry Essentials this skillj-morgan6/elixir-phoenix-guide | 166 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Caveman Gateway SetupJuliusBrussee/caveman | 110k | 1 repos | ~2.6k | Automated safety check: Warn | Apache-2.0 | |
| Agent Platform Alert Configurationgoogle/skills | 21k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Agent Observability Experiment Bootstrapdatadog-labs/agent-skills | 177 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Arize PhoenixArize-ai/phoenix | 12k | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Arize Instrumentationgithub/awesome-copilot | 40k | — | ~6.2k | Automated safety check: Notes | MIT |
JuliusBrussee/caveman
Routes every LLM call in a repository through the Caveman Cloud gateway in record mode, so requests and costs are measured without changing behavior.
google/skills
Writes Terraform alerting policies for AI agents that emit OpenTelemetry metrics, covering reliability, cost, safety, security and quality signals on Google Cloud.
datadog-labs/agent-skills
Bootstrap a reproducible LLM Observability experiment through the Python ddtrace SDK or the Node dd-trace SDK.
Arize-ai/phoenix
Open-source AI observability platform for tracing, evaluating, and improving LLM applications with OpenTelemetry integration
github/awesome-copilot
Adds Arize AX tracing to an LLM application for the first time.
pifferologo/cloud-agents-cli
This skill should be used when the user wants to "set up tracing", "monitor my ADK agent", "configure logging", "add observability", "debug production traffic", or needs guidance on monitoring…
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 adding logging, metrics, or instrumentation — structured Logger usage, telemetry handler attachment, Ecto/Phoenix telemetry events. Telemetry Essentials is an agent skill from j-morgan6/elixir-phoenix-guide. Use when adding logging, metrics, or instrumentation — structured Logger usage, telemetry handler attachment, Ecto/Phoenix telemetry events.
Telemetry Essentials fits situations like: instrumentation — structured Logger usage; telemetry handler attachment; ecto/Phoenix telemetry events.
Run `npx skills add j-morgan6/elixir-phoenix-guide --skill telemetry-essentials -a claude-code`. Or copy the skill folder (skills/telemetry-essentials in j-morgan6/elixir-phoenix-guide) into .claude/skills/telemetry-essentials in your project. Claude Code loads it when a task matches its description.
Run `npx skills add j-morgan6/elixir-phoenix-guide --skill telemetry-essentials -a codex`. Or copy the skill folder (skills/telemetry-essentials in j-morgan6/elixir-phoenix-guide) into .agents/skills/telemetry-essentials 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 telemetry-essentials -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/telemetry-essentials, .gemini/skills/telemetry-essentials, .github/skills/telemetry-essentials and .opencode/skills/telemetry-essentials in your project.
SKILL.md names no scripts, command-line tools or credentials: Telemetry Essentials 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.
Telemetry Essentials 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.7k 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 Telemetry Essentials: Caveman Gateway Setup (JuliusBrussee/caveman, 110k stars), Agent Platform Alert Configuration (google/skills, 21k stars), Agent Observability Experiment Bootstrap (datadog-labs/agent-skills, 177 stars) and Arize Phoenix (Arize-ai/phoenix, 12k 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.