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 Triage

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

Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…

MITAuto-check passedAI & LLM Engineering

Install Phx Triage

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

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

GitHub CLI
$ gh skill install oliver-kriska/claude-elixir-phoenix phx-triage --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/codex/skills/phx-triage .claude/skills/phx-triage && 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-triage
GitHub stars
565
Token cost
~948 tokens
SKILL.md length
325 words
Files
2 (incl. references)
Skills in repo
109
Repo updated
First seen
Licence
MIT

At a glance

Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…

  • Works in 5 steps: Load Review → Present ALL Findings for Batch Selection → Gather Context on Selected Items → …
  • Tasks that involve LLM observability
  • SKILL.md covers Usage, Why Triage, Workflow and Iron Laws, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Phx Triage is an agent skill from oliver-kriska/claude-elixir-phoenix. Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…

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

It sits in AI & LLM Engineering, covering LLM observability and Code review. 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
  • Tasks that involve Code review

Example prompts

  • “/phx-triage”

Workflow steps

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

  1. Load Review
  2. Present ALL Findings for Batch Selection
  3. Gather Context on Selected Items
  4. Generate Triage Summary
  5. Present Next Steps

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 Triage loads about 948 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 32 tokens; SKILL.md has 325 words of instructions outside code blocks.

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

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). 325 words, ~948 tokens.

Download SKILL.mdSave it as .claude/skills/phx-triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
phx-triage
description
Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…

Triage — Interactive Review Resolution

Walk through review findings one by one for human decision before committing to fixes.

Usage

$elixir-phoenix:phx-triage .claude/plans/user-auth/reviews/user-auth-review.md
$elixir-phoenix:phx-triage                  # Uses most recent review

Why Triage

After $elixir-phoenix:phx-review produces findings, you have three options:

  1. Fix everything — $elixir-phoenix:phx-plan .claude/plans/{slug}/reviews/...
  2. Triage first — $elixir-phoenix:phx-triage (filter, then fix what matters)
  3. Handle manually — Read review, pick what to fix yourself

Best when review has 5+ findings and you want to prioritize.

Workflow

Step 1: Load Review

Read the review file. Parse all findings with severity.

Iron Law violations first: list findings that match an Iron Law at the top, recommended as "Fix it". The user still makes the call (Iron Law 6).

Step 2: Present ALL Findings for Batch Selection

Use AskUserQuestion with multiSelect: true. Start with severity shortcuts, then list individual findings:

AskUserQuestion:
  question: "Which findings do you want to fix? (Iron Law violations auto-included)"
  header: "Triage"
  multiSelect: true
  options:
    - label: "All BLOCKERs ({count})"
      description: "Fix all critical issues"
    - label: "All WARNINGs ({count})"
      description: "Fix all should-fix issues"
    - label: "[BLOCKER] {title 1}"
      description: "{file}:{line} — {brief description}"
    - label: "[WARNING] {title 2}"
      description: "{file}:{line} — {brief description}"

If >4 options, batch into groups of 4 with severity shortcuts in the first batch. Severity shortcuts select all findings of that level — user can mix shortcuts with individual picks.

AskUserQuestion discipline: decisions only — never use it to narrate progress. Every option carries {file}:{line} + counts so the user decides without opening the review file.

Step 3: Gather Context on Selected Items

For selected items, ask ONE batch follow-up: "Any specific approach for any of these?" If they say "just fix them", proceed.

Step 4: Generate Triage Summary

Write to .claude/plans/{slug}/reviews/{slug}-triage.md with Fix Queue (approved items with checkboxes), Skipped, and Deferred sections.

Step 5: Present Next Steps
Triage complete: {n} to fix, {n} skipped, {n} deferred.

1. Plan fixes — $elixir-phoenix:phx-plan .claude/plans/{slug}/reviews/{slug}-triage.md
2. Fix directly — $elixir-phoenix:phx-work (for simple fixes)
3. Review deferred items later
4. Capture solutions — $elixir-phoenix:phx-compound (if patterns were solved)

Iron Laws

  1. Batch selection over one-by-one — Use multiSelect for efficiency
  2. User decides, not the agent — Present facts, don't push
  3. BLOCKERs cannot be skipped silently — Warn if user tries
  4. Capture user context — Every "fix it" should include any user guidance for better fixes
  5. Suggest compound after triage — If triage reveals solved patterns (root cause identified, fix known), mention $elixir-phoenix:phx-compound
  6. NEVER auto-decide severity or auto-dismiss findings — the human assigns final priority; present the agent's severity as a recommendation, not a verdict

Integration with Workflow

text
$elixir-phoenix:phx-review
       |
$elixir-phoenix:phx-triage  ← YOU ARE HERE (interactive filtering)
       |
$elixir-phoenix:phx-plan (with triage file) → $elixir-phoenix:phx-work → $elixir-phoenix:phx-compound

References

  • references/triage-patterns.md — Common triage decisions

© 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/codex/skills/phx-triage of oliver-kriska/claude-elixir-phoenix.

  • SKILL.md
  • references/triage-patterns.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Phx Triage 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 Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phx Triage this skilloliver-kriska/claude-elixir-phoenix565—~948Automated safety check: PassMIT
Code Reviewlangfuse/langfuse36k—~591Automated safety check: PassCustom licence
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

Similar skills

  • Code Review

    langfuse/langfuse

    Review Langfuse code changes for correctness, regressions, and best practices.

    36k GitHub stars~591 tokensUpdated today
    AI & LLM EngineeringAuto-check passed

  • Ash Framework

    podlove/radiator

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

    136 GitHub stars~2.1k tokensUpdated 16 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 yesterday
    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 25 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 yesterday
    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

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 5 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 5 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 5 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 5 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 5 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 5 days ago
    Auto-check passed

Works with

Categories

Questions about Phx Triage

What does Phx Triage do?

Triage review findings interactively — approve, skip, or prioritize; Use after $elixir-phoenix:phx-review to filter…. Phx Triage is an agent skill from oliver-kriska/claude-elixir-phoenix.

When should I use Phx Triage?

Phx Triage fits situations like: tasks that involve LLM observability; tasks that involve Code review.

How do I install Phx Triage in Claude Code?

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

How do I install Phx Triage in Codex?

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

Can I use Phx Triage 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-triage -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-triage, .gemini/skills/phx-triage, .github/skills/phx-triage and .opencode/skills/phx-triage in your project.

What does Phx Triage need to run?

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

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

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

About 948 tokens (SKILL.md is roughly 3.8k 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 706 tokens, read only when the agent opens those files.

What are the alternatives to Phx Triage?

Skills that share tags, products or a category with Phx Triage: Code Review (langfuse/langfuse, 36k stars), Ash Framework (podlove/radiator, 136 stars), Sentry Elixir SDK (getsentry/sentry-for-ai, 268 stars) and Elixir (streamband/hydra-srt, 147 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phx Triage?

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.