Agent skill · Testing & QA

help

Choose Phoenix review, plan, debug, or test command. Use when user asks which /phx: command or plugin skill handles a task; do not route only to a domain skill. NEVER for bare /help; NOT for ambiguous requests (use intent-detection) or a plugin tour.

oliver-kriskagithub.com/oliver-kriskaGitHub ↗
claude-codeMIT
Install
npx skills add oliver-kriska/claude-elixir-phoenix --skill help --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: plugins/elixir-phoenix/skills/help/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 515
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 `${CLAUDE_SKILL_DIR}/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 | `/phx:intro` | | **Ideation** | "explore", "brainstorm", "not

What's inside
Steps it walks through
  1. Usage
  2. Arguments
  3. Execution Flow
  4. Step 1: Gather Context
  5. Step 2: Classify Intent
  6. Step 3: Respond or Clarify
  7. Step 4: Offer Follow-up
  8. Iron Laws
  9. Integration
Ships with 1 file
  • references/tool-catalog.md
More from claude-elixir-phoenix
All skills →
About this skill
What does the help skill do?

Choose Phoenix review, plan, debug, or test command. Use when user asks which /phx: command or plugin skill handles a task; do not route only to a domain skill. NEVER for bare /help; NOT for ambiguous requests (use intent-detection) or a plugin tour.

How do I install it?

Run `npx skills add oliver-kriska/claude-elixir-phoenix --skill help --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From oliver-kriska/claude-elixir-phoenix, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going