Agent skill

Phx Help

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

Recommend the right $elixir-phoenix:phx- workflow. An agent skill from oliver-kriska/claude-elixir-phoenix.

MITAuto-check passedAI & LLM Engineering

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/codex/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/

Paste into Claude Code

Install the "phx-help" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-help into .claude/skills/phx-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-help", 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

$skill-installer install https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-help

Type 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.

skills CLI

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

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix phx-help --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .agents/skills && cp -r skills-src/targets/codex/skills/phx-help .agents/skills/phx-help && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "phx-help" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-help into .agents/skills/phx-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-help", 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.

skills CLI

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

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix phx-help --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/targets/codex/skills/phx-help .cursor/skills/phx-help && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "phx-help" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-help into .cursor/skills/phx-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-help", 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

$ gemini skills install https://github.com/oliver-kriska/claude-elixir-phoenix.git --path targets/codex/skills/phx-help

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-help -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix phx-help --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/targets/codex/skills/phx-help .gemini/skills/phx-help && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "phx-help" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-help into .gemini/skills/phx-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-help", 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.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix phx-help

Installs 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).

skills CLI

$ npx skills add oliver-kriska/claude-elixir-phoenix --skill phx-help -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .github/skills && cp -r skills-src/targets/codex/skills/phx-help .github/skills/phx-help && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "phx-help" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-help into .github/skills/phx-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-help", 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.

skills CLI

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

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install oliver-kriska/claude-elixir-phoenix phx-help --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/oliver-kriska/claude-elixir-phoenix.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/targets/codex/skills/phx-help .opencode/skills/phx-help && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "phx-help" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/codex/skills/phx-help into .opencode/skills/phx-help/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-help", 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.

Facts

Skill name: phx-help
GitHub stars: 565
Token cost: ~1.2k tokens
SKILL.md length: 497 words
Files: 2 (incl. references)
Skills in repo: 109
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Recommend the right $elixir-phoenix:phx- workflow. An agent skill from oliver-kriska/claude-elixir-phoenix.

Works in 4 steps: Gather Context → Classify Intent → Respond or Clarify → …
Choosing a plugin skill
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. Recommend the right $elixir-phoenix:phx- workflow. Use when choosing a plugin skill, not for Codex /help.

Its SKILL.md is about 1.2k 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 AI & LLM Engineering, 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

Choosing a plugin skill
Not for Codex /help

Example prompts

“/phx-help”

Workflow steps

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

Gather Context
Classify Intent
Respond or Clarify
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.2k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 29 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: ~29
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.9k

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,198 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: Recommend the right $elixir-phoenix:phx-* workflow. Use when choosing a plugin skill, not for Codex /help.

Plugin Help — Interactive Command Advisor

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

Usage

$elixir-phoenix:phx-help                          # Analyze context, suggest commands
$elixir-phoenix:phx-help how do I debug this?     # Route to $elixir-phoenix:phx-investigate
$elixir-phoenix:phx-help add a new feature        # Route to $elixir-phoenix:phx-plan -> $elixir-phoenix: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):

Check for existing plans: use Glob on .claude/plans/*/plan.md — active work in progress?
Check git status: uncommitted changes? which files?
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:

Category	Signals	Primary Commands
Starting out	No plans, new to plugin	`$elixir-phoenix:phx-intro`
Ideation	"explore", "brainstorm", "not sure", "how to approach", "vague idea"	`$elixir-phoenix:phx-brainstorm`
New feature	"add", "build", "implement", multi-file	`$elixir-phoenix:phx-plan` → `$elixir-phoenix:phx-work`
Quick change	Single file, <50 lines, "fix typo"	`$elixir-phoenix:phx-quick`
Bug	Error, stack trace, "broken", "failing"	`$elixir-phoenix:phx-investigate`
Review	"check", "review", PR ready	`$elixir-phoenix:phx-review`
Performance	"slow", "N+1", "memory"	`$elixir-phoenix:phx-perf`, `$elixir-phoenix:ecto-n1-check`, `$elixir-phoenix:lv-assigns`
Research	"how to", "best practice", "evaluate lib"	`$elixir-phoenix:phx-research`
Resume work	Existing plan with unchecked tasks	`$elixir-phoenix:phx-work --continue`
Post-fix	"that worked", solved a hard bug	`$elixir-phoenix:phx-compound`
Full cycle	Large feature, new domain area	`$elixir-phoenix:phx-full`
Project health	"audit", "tech debt", "overall quality"	`$elixir-phoenix:phx-audit`, `$elixir-phoenix:phx-techdebt`
Dep update audit	"audit deps", "supply chain", "post-`mix deps.update`", "review mix.lock PR"	`$elixir-phoenix:phx-deps-audit`
Manual dep vetting	"vet this package", "approve dep", "trust ledger", "after $elixir-phoenix:phx-deps-audit findings"	`$elixir-phoenix:phx-deps-vet`
Deployment	"deploy", "release", "production"	`$elixir-phoenix:phx-verify` then deploy skill
Permissions	"too many prompts", "allow", "permission fatigue"	`$elixir-phoenix: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 $elixir-phoenix:phx-help anytime to get routing advice"
If they seem new: "Try $elixir-phoenix:phx-intro for a full plugin walkthrough"

Iron Laws

ONE recommendation — don't dump the full catalog, pick the best match
MAX ONE clarifying question — don't interrogate, make your best guess
Show exact syntax — $elixir-phoenix:phx-plan Add user notifications not just "use the plan command"
Context over keywords — existing plans + git state matter more than word matching
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 $elixir-phoenix:phx-intro for onboarding

Files

SKILL.md and 1 other file (references) in targets/codex/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
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Phx Help this skilloliver-kriska/claude-elixir-phoenix	565	—	~1.2k	Automated safety check: Pass	MIT	4 days ago
Elixir Architectmaxim-ist/elixir-architect	145	—	~7.6k	Automated safety check: Pass	MIT	10 mo ago
Phoenix Frameworkpodlove/radiator	136	—	~562	Automated safety check: Pass	MIT	15 days ago
Elixir Expertpass-agent/loomkin	181	1 repos	~796	Automated safety check: Pass	MIT	4 mo ago
Usage Rulesbradleygolden/claude-marketplace-elixir	176	—	~4.9k	Automated safety check: Notes	MIT	9 mo ago
Elixir Prodavila7/claude-code-templates	33k	8 repos	~486	Automated safety check: Pass	MIT	today

Similar skills

Elixir Architect
maxim-ist/elixir-architect
A skill your agent uses when designing or architecting Elixir/Phoenix applications, creating comprehensive project documentation, planning OTP supervision trees, defining domain models with Ash…
145 GitHub stars~7.6k tokensUpdated 10 mo ago
AI & LLM EngineeringAuto-check passed
Phoenix Framework
podlove/radiator
Use this skill working with Phoenix Framework. An agent skill from podlove/radiator.
136 GitHub stars~562 tokensUpdated 15 days ago
AI & LLM EngineeringAuto-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
Usage Rules
bradleygolden/claude-marketplace-elixir
Search for package-specific usage rules and best practices from Elixir packages.
176 GitHub stars~4.9k tokensUpdated 9 mo ago
AI & LLM EngineeringAuto-check: notes
Elixir Pro
davila7/claude-code-templates
Write idiomatic Elixir code with OTP patterns, supervision trees, and Phoenix LiveView.
33k GitHub starsUsed in 8 repos~486 tokens
AI & LLM EngineeringAuto-check passed
Phoenix
ericrisco/rsc-harness
A skill your agent uses when building an Elixir web app with Phoenix — contexts, Ecto schemas, changesets and migrations, LiveView, channels and PubSub, the generators, and the boundary between…
180 GitHub stars~2.9k tokensUpdated today
AI & LLM EngineeringAuto-check: notes

Questions about Phx Help

What does Phx Help do?

Recommend the right $elixir-phoenix:phx- workflow. An agent skill from oliver-kriska/claude-elixir-phoenix. Phx Help is an agent skill from oliver-kriska/claude-elixir-phoenix. Recommend the right $elixir-phoenix:phx- workflow.

When should I use Phx Help?

Phx Help fits situations like: choosing a plugin skill; not for Codex /help.

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/codex/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/codex/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.2k tokens (SKILL.md is roughly 4.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 2.7k 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: Elixir Architect (maxim-ist/elixir-architect, 145 stars), Phoenix Framework (podlove/radiator, 136 stars), Elixir Expert (pass-agent/loomkin, 181 stars) and Usage Rules (bradleygolden/claude-marketplace-elixir, 176 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 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.

Install Phx Help

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plugin Help — Interactive Command Advisor

Usage

Arguments

Execution Flow

Step 1: Gather Context

Step 2: Classify Intent

Step 3: Respond or Clarify

Step 4: Offer Follow-up

Iron Laws

Integration

Files

Compare with similar skills

Similar skills

More from oliver-kriska/claude-elixir-phoenix

Related

Questions about Phx Help