A skill your agent uses when the user asks which phx- command fits a task (review, plan, debug, test) or how two commands differ.

MITAuto-check passedDevelopment

Install Phx Help

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

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

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

At a glance

A skill your agent uses when the user asks which phx- command fits a task (review, plan, debug, test) or how two commands differ.

  • Works in 4 steps: Gather Context → Classify Intent → Respond or Clarify → …
  • The user asks which phx- command fits a task (review
  • SKILL.md covers Usage, Arguments, Execution Flow and Iron Laws, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Phx Help is an agent skill from oliver-kriska/claude-elixir-phoenix. Use when the user asks which phx- command fits a task (review, plan, debug, test) or how two commands differ. Checks plans and git state, then recommends from the routing table. Not for bare /help, a tour, or ambiguous requests (intent-detection).

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

It sits in Development. It works with Git. 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

  • The user asks which phx- command fits a task (review
  • How two commands differ

Example prompts

  • “/phx-help”

Workflow steps

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

  1. Gather Context
  2. Classify Intent
  3. Respond or Clarify
  4. Offer Follow-up

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

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

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). 497 words, ~1,110 tokens.

Download SKILL.mdSave it as .claude/skills/phx-help/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
phx-help
description
Use when the user asks which phx-* command fits a task (review, plan, debug, test) or how two commands differ. Checks plans and git state, then recommends from the routing table. Not for bare /help, a tour, or ambiguous requests (intent-detection).

Plugin Help — Interactive Command Advisor

Helps users find the right command, skill, or agent for their situation.

Usage

phx-help                          # Analyze context, suggest commands
phx-help how do I debug this?     # Route to phx-investigate
phx-help add a new feature        # Route to phx-plan -> phx-work

Arguments

  • $ARGUMENTS — optional description of what the user wants to do
  • Empty = analyze current context (git status, existing plans, file patterns)

Execution Flow

Step 1: Gather Context

If $ARGUMENTS is non-empty, use it as primary signal.

Always gather ambient context (run in parallel):

  1. Check for existing plans: use Glob on .claude/plans/*/plan.md — active work in progress?
  2. Check git status: uncommitted changes? which files?
  3. Check for solution docs: use Glob on .claude/solutions/**/*.md — prior knowledge?
Step 2: Classify Intent

Read references/tool-catalog.md for the full routing table.

Map the user's situation to one of these categories:

CategorySignalsPrimary Commands
Starting outNo plans, new to pluginphx-intro
Ideation"explore", "brainstorm", "not sure", "how to approach", "vague idea"phx-brainstorm
New feature"add", "build", "implement", multi-filephx-plan → phx-work
Quick changeSingle file, <50 lines, "fix typo"phx-quick
BugError, stack trace, "broken", "failing"phx-investigate
Review"check", "review", PR readyphx-review
Performance"slow", "N+1", "memory"phx-perf, ecto-n1-check, lv-assigns
Research"how to", "best practice", "evaluate lib"phx-research
Resume workExisting plan with unchecked tasksphx-work --continue
Post-fix"that worked", solved a hard bugphx-compound
Full cycleLarge feature, new domain areaphx-full
Project health"audit", "tech debt", "overall quality"phx-audit, phx-techdebt
Dep update audit"audit deps", "supply chain", "post-mix deps.update", "review mix.lock PR"phx-deps-audit
Manual dep vetting"vet this package", "approve dep", "trust ledger", "after phx-deps-audit findings"phx-deps-vet
Deployment"deploy", "release", "production"phx-verify then deploy skill
Permissions"too many prompts", "allow", "permission fatigue"phx-permissions
Returning after time off"what did I miss", "back from vacation", "catch up", "what changed while I was out"/catchup (companion plugin, separate install)
Show full SKILL.md (215 more words)Show less
Step 3: Respond or Clarify

If high confidence (clear match to one category): Present the recommendation with:

  • The command to run (with exact syntax)
  • One-line explanation of what it does
  • What artifacts it creates (if any)
  • Suggested next step after it completes

If medium confidence (2-3 possible matches): Use AskUserQuestion with the top options, each with a one-line explanation.

If low confidence (vague or no signal): Ask ONE focused clarifying question. Examples:

  • "Are you starting something new or continuing existing work?"
  • "Is this a bug fix or a new feature?"
  • "How many files do you expect to change?"

Then recommend based on the answer.

Step 4: Offer Follow-up

After recommending, always add:

  • "Run phx-help anytime to get routing advice"
  • If they seem new: "Try phx-intro for a full plugin walkthrough"

Iron Laws

  1. ONE recommendation — don't dump the full catalog, pick the best match
  2. MAX ONE clarifying question — don't interrogate, make your best guess
  3. Show exact syntax — phx-plan Add user notifications not just "use the plan command"
  4. Context over keywords — existing plans + git state matter more than word matching
  5. NEVER block — if user already knows what they want, DO NOT redirect

Integration

  • Complements intent-detection (auto-trigger) with explicit invocation
  • References same routing logic but adds interactive clarification
  • Can recommend phx-intro for onboarding

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

  • SKILL.md
  • references/tool-catalog.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Phx Help 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 Help compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phx Help this skilloliver-kriska/claude-elixir-phoenix565—~1.1kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed
  • Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    56k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

More from oliver-kriska/claude-elixir-phoenix

All 111 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 Help

What does Phx Help do?

A skill your agent uses when the user asks which phx- command fits a task (review, plan, debug, test) or how two commands differ. Phx Help is an agent skill from oliver-kriska/claude-elixir-phoenix. Use when the user asks which phx- command fits a task (review, plan, debug, test) or how two commands differ.

When should I use Phx Help?

Phx Help fits situations like: the user asks which phx- command fits a task (review; how two commands differ.

How do I install Phx Help in Claude Code?

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

How do I install Phx Help in Codex?

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

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

What does Phx Help need to run?

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

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

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

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

What are the alternatives to Phx Help?

Skills that share tags, products or a category with Phx Help: Finishing a Development Branch (obra/superpowers, 297k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars) and Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phx Help?

oliver-kriska (a GitHub user) maintains it in oliver-kriska/claude-elixir-phoenix, which has 565 GitHub stars. The repository holds 111 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.