New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Phx Verify

by oliver-kriska in oliver-kriska/claude-elixir-phoenix

Verify Elixir/Phoenix changes — compile, format, and test in one loop.

MITAuto-check passedTesting & QA

Install Phx Verify

skills CLI
$ npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-verify -a claude-code

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

GitHub CLI
$ gh skill install oliver-kriska/claude-elixir-phoenix phx-verify --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/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/targets/pi/skills/phx-verify .claude/skills/phx-verify && 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
phx-verify
GitHub stars
565
Token cost
~1.3k tokens
SKILL.md length
563 words
Files
2 (incl. references)
Skills in repo
109
Repo updated
First seen
Licence
MIT

At a glance

Verify Elixir/Phoenix changes — compile, format, and test in one loop.

  • Tasks that involve LLM observability
  • SKILL.md covers Iron Laws, Step 0: Project Discovery…, Verification Sequence and Quick Reference, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Phx Verify is an agent skill from oliver-kriska/claude-elixir-phoenix. Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/project-discovery.md`).

It sits in Testing & QA, covering LLM observability. It works with Elixir. The repository describes itself as: Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute… The licence is MIT.

When your agent uses it

  • Tasks that involve LLM observability

Example prompts

  • “/phx-verify”

What it can do on your machine

Read from SKILL.md and the folder at commit 9767a82. 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.

    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

Phx Verify loads about 1.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 35 tokens; SKILL.md has 563 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~35
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.4k

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 oliver-kriska/claude-elixir-phoenix at commit 9767a82, republished under its MIT licence (© oliver-kriska). 563 words, ~1,252 tokens.

Download SKILL.mdSave it as .claude/skills/phx-verify/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
phx-verify
description
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.

Verification Loop

Project-aware verification for Elixir/Phoenix. Reads mix.exs and .check.exs to discover tools, test commands, and custom aliases before running anything.

Iron Laws

  1. Discover before running — Read mix.exs first; never run mix credo if credo isn't a dependency
  2. Prefer ex_check — If :ex_check + .check.exs exists, mix check replaces individual steps
  3. Prefer project aliases — If mix ci or composite alias exists, use it over individual steps
  4. Run in order — Later steps assume earlier ones pass
  5. Ask before E2E tests — Unit tests run automatically; E2E/integration tests need user confirmation
  6. NEVER report success without showing actual command output — "should work" is not verification

Step 0: Project Discovery (ALWAYS FIRST)

Read mix.exs — extract deps/0, aliases/0, and cli/0 (for preferred_envs). Also check for .check.exs. See references/project-discovery.md for full patterns.

Discover tools (deps): :credo, :dialyxir, :sobelow, :ex_check, :excoveralls, :boundary

Discover test commands (aliases + deps):

  • Unit: mix test (always), or custom alias like mix test.with_coverage
  • E2E: mix playwright.test, mix cypress.run, or similar (check preferred_envs for MIX_ENV)
  • Fast E2E: mix playwright.run (skips setup — for re-runs)

Discover composite runner: If .check.exs exists, read it — mix check may handle compile, format, credo, test, dialyzer, sobelow, and more.

Report discovery:

Project tools: compile ✓ | format ✓ | credo ✓ | dialyzer ✓ | sobelow ✓ | ex_check ✓
Test commands: mix test (unit) | mix playwright.test (E2E, MIX_ENV=int_test)
Composite runner: mix check (.check.exs covers: compiler, formatter, credo, dialyzer, sobelow, tests)
Strategy: Running `mix check` then asking about E2E

Verification Sequence

Before using any discovered alias or composite command, confirm it runs:

  1. Check the dependency is in mix.lock (not just mix.exs) — deps may not be fetched
  2. Run the command — if it fails with "command not found" or dependency error, fall back to individual steps
  3. Log the fallback: "mix check failed (ex_check not installed?), falling back to individual steps"

If ex_check installed + .check.exs exists: Try mix check. If it fails, fall back to individual steps.

If composite alias found (e.g., mix ci, mix precommit): Try it. If it fails, fall back to individual steps.

Otherwise (or after fallback): Run individual steps, skipping unavailable tools.

Step 1: Compile

mix compile --warnings-as-errors — always

Elixir 1.20+ (OTP 27+): the compiler's built-in type checker emits type violations / verified bugs as warnings, so --warnings-as-errors now fails the build on them — no Dialyzer needed. If a previously-green build fails after a 1.20 bump, suspect a newly-detected type violation, not a regression. Read the message literally (accepted vs supplied type); it is almost always a real bug. See ../elixir-idioms/references/elixir-120-type-system.md.

Show full SKILL.md (194 more words)Show less
Step 2: Format

mix format --check-formatted — always (auto-fix with mix format if fails)

Step 3: Credo

mix credo --strict — if :credo in deps, else skip

Step 4: Test

mix test --trace — use project test alias if available

Step 5: Dialyzer

mix dialyzer — if :dialyxir in deps, pre-PR only

Step 6: Sobelow

mix sobelow --config — if :sobelow in deps

Skip unavailable tools with: "Credo: ⏭ Not installed"

Step 7: Additional Test Offer

After core verification passes, check if project has additional test commands (E2E, integration, coverage). Ask the user:

Core verification passed. Additional test commands available:
1. mix playwright.test (E2E, MIX_ENV=int_test) — ~5min
2. mix test.with_coverage (unit + coverage report)
Run any of these? [1/2/both/skip]

Respect preferred_envs / cli/0 for correct MIX_ENV on each command.

Quick Reference

StepCommandCondition
DiscoveryRead mix.exs + .check.exsAlways first
Compositemix checkIf :ex_check installed
Compilemix compile --warnings-as-errorsAlways
Formatmix format --check-formattedAlways
Credomix credo --strict:credo in deps
Testmix test --traceAlways (use alias if exists)
Dialyzermix dialyzer:dialyxir in deps, pre-PR
Sobelowmix sobelow --config:sobelow in deps
E2E/ExtraAsk userIf additional test commands found

Usage

  1. Run /skill:phx-verify — discovery happens automatically
  2. Core checks run in order, adapted to project
  3. After pass, offered additional test commands (E2E, coverage)
  4. Commit only after all chosen checks pass

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

Files

SKILL.md and 1 other file (references) in targets/pi/skills/phx-verify of oliver-kriska/claude-elixir-phoenix.

  • SKILL.md
  • references/project-discovery.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Phx Verify 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.

Phx Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phx Verify this skilloliver-kriska/claude-elixir-phoenix565—~1.3kAutomated safety check: PassMIT
Ash Frameworkpodlove/radiator136—~2.1kAutomated safety check: PassMIT
Sentry Elixir SDKgetsentry/sentry-for-ai268—~3.5kAutomated safety check: PassApache-2.0
Elixirstreamband/hydra-srt147—~804Automated safety check: PassApache-2.0
Change CleanupSimon-Initiative/oli-torus119—~3.7kAutomated safety check: PassMIT
Elixir Expertpass-agent/loomkin1811 repos~796Automated safety check: PassMIT

Similar skills

  • Ash Framework

    podlove/radiator

    Use this skill working with Ash Framework or any of its extensions.

    136 GitHub stars~2.1k tokensUpdated 15 days ago
    AI & LLM EngineeringAuto-check passed

  • Sentry Elixir SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for Elixir. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~3.5k tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Elixir

    streamband/hydra-srt

    A skill your agent uses for Elixir/Phoenix development in this repo: implementing features, refactors, debugging, tests, Ecto changes, and production-safe fixes.

    147 GitHub stars~804 tokensUpdated 24 days ago
    DevelopmentAuto-check passed

  • Change Cleanup

    Simon-Initiative/oli-torus

    Clean up and harden code introduced by the current branch without drifting into broad refactors.

    119 GitHub stars~3.7k tokensUpdated today
    DevelopmentAuto-check passed

  • Elixir Expert

    pass-agent/loomkin

    Expert in Elixir, Phoenix Framework, and OTP. An agent skill from pass-agent/loomkin.

    181 GitHub starsUsed in 1 repo~796 tokens
    AI & LLM EngineeringAuto-check passed

  • Hydra Architect

    streamband/hydra-srt

    A skill your agent uses when designing or evolving Hydra platform architecture across Elixir/Phoenix, SQLite, VictoriaMetrics/VictoriaLogs analytics, native/Rust, and runtime boundaries.

    147 GitHub stars~1.2k tokensUpdated 24 days ago
    DatabasesAuto-check passed

More from oliver-kriska/claude-elixir-phoenix

All 109 skills in this repo

  • Codex Ab

    oliver-kriska/claude-elixir-phoenix

    Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict.

    565 GitHub stars~977 tokensUpdated 4 days ago
    Auto-check passed

  • Audit

    oliver-kriska/claude-elixir-phoenix

    Project health audit and health check — architecture, performance, tests, dependencies, code quality.

    565 GitHub stars~2k tokensUpdated 4 days ago
    Auto-check passed

  • Compound Docs

    oliver-kriska/claude-elixir-phoenix

    Searchable Elixir/Phoenix/Ecto solution documentation system with; Use when consulting past solutions…

    565 GitHub stars~528 tokensUpdated 4 days ago
    Auto-check passed

  • Compound Docs

    oliver-kriska/claude-elixir-phoenix

    Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter.

    565 GitHub stars~547 tokensUpdated 4 days ago
    Auto-check passed

  • Deploy

    oliver-kriska/claude-elixir-phoenix

    Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays.

    565 GitHub stars~1.1k tokensUpdated 4 days ago
    Auto-check passed

  • Deps Update

    oliver-kriska/claude-elixir-phoenix

    Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo).

    565 GitHub stars~1.4k tokensUpdated 4 days ago
    Auto-check passed

Works with

Categories

Questions about Phx Verify

What does Phx Verify do?

Verify Elixir/Phoenix changes — compile, format, and test in one loop. Phx Verify is an agent skill from oliver-kriska/claude-elixir-phoenix. Verify Elixir/Phoenix changes — compile, format, and test in one loop.

When should I use Phx Verify?

Phx Verify fits situations like: tasks that involve LLM observability.

How do I install Phx Verify in Claude Code?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-verify -a claude-code`. Or copy the skill folder (targets/pi/skills/phx-verify in oliver-kriska/claude-elixir-phoenix) into .claude/skills/phx-verify in your project. Claude Code loads it when a task matches its description.

How do I install Phx Verify in Codex?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-verify -a codex`. Or copy the skill folder (targets/pi/skills/phx-verify in oliver-kriska/claude-elixir-phoenix) into .agents/skills/phx-verify in your project. Codex loads it when a task matches its description.

Can I use Phx Verify 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 oliver-kriska/claude-elixir-phoenix --skill phx-verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/phx-verify, .gemini/skills/phx-verify, .github/skills/phx-verify and .opencode/skills/phx-verify in your project.

What does Phx Verify need to run?

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

Does Phx Verify 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 Phx Verify 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 Phx Verify use?

Phx Verify 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 Phx Verify use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Phx Verify?

Skills that share tags, products or a category with Phx Verify: Ash Framework (podlove/radiator, 136 stars), Sentry Elixir SDK (getsentry/sentry-for-ai, 268 stars), Elixir (streamband/hydra-srt, 147 stars) and Change Cleanup (Simon-Initiative/oli-torus, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phx Verify?

oliver-kriska (a GitHub user) maintains it in oliver-kriska/claude-elixir-phoenix, which has 565 GitHub stars. The repository holds 109 skills in this directory. The repository was last updated on October 5, 2026.

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