Agent skill

Phx Brief

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

Interactive briefing of a plan file — explains reasoning, schema decisions, component choices.

MITAuto-check passed

Install Phx Brief

skills CLI

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

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

GitHub CLI

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

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-brief -a codex

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

GitHub CLI

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

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

GitHub CLI

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

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

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-brief -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/pi/skills/phx-brief .github/skills/phx-brief && 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-brief" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/phx-brief into .github/skills/phx-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-brief", 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-brief -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-brief --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/pi/skills/phx-brief .opencode/skills/phx-brief && 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-brief" agent skill from https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/targets/pi/skills/phx-brief into .opencode/skills/phx-brief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "phx-brief", 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-brief
GitHub stars: 565
Token cost: ~1.2k tokens
SKILL.md length: 527 words
Files: 3 (incl. references)
Skills in repo: 109
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Interactive briefing of a plan file — explains reasoning, schema decisions, component choices.

Works in 3 steps: Locate and Load Plan → Load Supporting Artifacts → Present Briefing Sections
Developers need to understand a plan before approving
SKILL.md covers Why This Exists, Usage, Arguments and Mode Detection, plus 6 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Phx Brief is an agent skill from oliver-kriska/claude-elixir-phoenix. Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/briefing-guide.md` and `references/visual-explainer.md`).

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

Developers need to understand a plan before approving

Example prompts

“/phx-brief”

Workflow steps

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

Locate and Load Plan
Load Supporting Artifacts
Present Briefing Sections

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

Always · name and description, kept in context so the agent knows when to use it: ~42
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: ~4.2k

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). 527 words, ~1,196 tokens.

Download SKILL.mdSave it as .claude/skills/phx-brief/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: phx-brief
description: Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Use when developers need to understand a plan before approving.

Plan Briefing

Interactive walkthrough of a plan's reasoning, decisions, and solution shape. Designed for developers who need to understand a plan in 1-2 minutes instead of reading the full document.

Why This Exists

Plans answer "what to do" but bury "why." This skill bridges that gap with an interactive walkthrough.

Usage

/skill:phx-brief                                    # Latest plan
/skill:phx-brief .claude/plans/user-auth/plan.md    # Specific plan

Arguments

$ARGUMENTS = Path to plan file (optional, auto-detects latest)

Mode Detection

Read the plan file and determine mode from phase statuses:

All phases [PENDING] = Pre-work briefing (what WILL happen)
Any phase [COMPLETED] or [IN_PROGRESS] = Post-work briefing (what WAS done and why)

Execution Flow

Step 1: Locate and Load Plan

If $ARGUMENTS has a path, use it
Otherwise, find latest plan:

Use Glob to find .claude/plans/*/plan.md and pick the most recent.
If no plan found, tell user and suggest /skill:phx-plan
Read the plan file

Step 2: Load Supporting Artifacts

Read what's available (don't fail if missing):

.claude/plans/{slug}/summaries/consolidated.md (research summary)
.claude/plans/{slug}/scratchpad.md (decisions, dead-ends)
.claude/plans/{slug}/progress.md (work log, post-work only)

Step 3: Present Briefing Sections

Present ONE section at a time, wrapped in the visual briefing block (see references/briefing-guide.md Visual Formatting).

The section MUST be emitted as visible response text BEFORE the AskUserQuestion call. Content composed only in thinking/reasoning is invisible to the user, and the question field is too short to carry it. If the user would see only a "Continue?" dialog, the section was never shown. Write the ★ Briefing block as normal output first, then ask:

If sections remain: question "Continue the briefing?" with options "Next: {title}", "Ask me a question about this", "Stop here"
If final section: no question needed, show closing message

Section Flow (Pre-Work Mode)

#	Title	Source
1	What We're Building	Summary + Scope
2	Key Decisions	Technical Decisions + scratchpad rationale
3	Solution Shape	Phases overview + Data Model
4	Risks & Confidence	Risks table + unknowns/spikes

Show full SKILL.md (228 more words)Show less

Section Flow (Post-Work Mode)

#	Title	Source
1	What Was Built	Summary + completion status
2	Key Decisions & Why	Technical Decisions + scratchpad
3	How It Was Built	Phases with implementation notes
4	Lessons & Patterns	Risks encountered + patterns used

See references/briefing-guide.md for section content templates.

Iron Laws

ONE section at a time — never dump all content
User controls pace — always offer to stop
Explain WHY, not just WHAT — rationale over listing
Ground in artifacts — focus on insights specific to this plan's research, decisions, and scratchpad entries, not general programming concepts
Keep each section under 20 lines — this is a briefing, not a lecture
NEVER skip sections or auto-start work — briefing is read-only; do not execute plan tasks or launch /skill:phx-work without explicit user request
SECTION TEXT BEFORE THE QUESTION — every ★ Briefing block is visible response text emitted before its AskUserQuestion; never deliver a section only inside thinking or the question field

Closing Message

After final section (or when user stops):

That's the briefing! For full details, see:
{plan_path}

Ready to proceed? Try `/skill:phx-work {plan_path}` to start execution.

Post-work variant:

That's what was built! For full details, see:
{plan_path}

Consider `/skill:phx-compound` to capture key learnings for future reference.

Integration

text

/skill:phx-plan  -->  /skill:phx-brief (optional)  -->  /skill:phx-work  -->  /skill:phx-brief (optional)
  create       understand before            execute        understand after

Complex Plan Enhancement

For plans with 5+ phases or 4+ key decisions, consider suggesting visual rendering after Section 3. See references/visual-explainer.md for thresholds and commands.

Notes

Runs in main conversation context (not a subagent)
Model: no special requirement — uses default session model
No artifacts written — briefing is ephemeral, plan IS the artifact
Reference file readable since skill runs in user's session

Files

SKILL.md and 2 other files (references) in targets/pi/skills/phx-brief of oliver-kriska/claude-elixir-phoenix.

SKILL.md
references/briefing-guide.md
references/visual-explainer.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Phx Brief 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 Brief compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Phx Brief this skilloliver-kriska/claude-elixir-phoenix	565	—	~1.2k	Automated safety check: Pass	MIT	5 days ago
MCP Server Builderanthropics/skills	180k	63 repos	~2.3k	Automated safety check: Pass	Apache-2.0	yesterday
Vercel Composition Patternssupabase/supabase	111k	58 repos	~726	Automated safety check: Pass	MIT	yesterday
Finishing a Development Branchobra/superpowers	297k	5 repos	~1.9k	Automated safety check: Pass	MIT	yesterday
Agent Browser CLIvercel-labs/agent-browser	44k	24 repos	~864	Automated safety check: Pass	Apache-2.0	today
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official	38k	10 repos	~4.1k	Automated safety check: Notes	Apache-2.0	today

Similar skills

MCP Server Builder
anthropics/skills
Official
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
180k GitHub starsUsed in 63 repos~2.3k tokens
Agent WorkflowsAuto-check passed
Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 58 repos~726 tokens
DevelopmentAuto-check passed
Finishing a Development Branch
obra/superpowers
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
Agent Browser CLI
vercel-labs/agent-browser
Official
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…
44k GitHub starsUsed in 24 repos~864 tokens
Productivity & AutomationAuto-check passed
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
38k GitHub starsUsed in 10 repos~4.1k tokens
Agent WorkflowsAuto-check: notes
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
10k GitHub starsUsed in 25 repos~4.2k tokens
DevelopmentAuto-check passed

Questions about Phx Brief

What does Phx Brief do?

Interactive briefing of a plan file — explains reasoning, schema decisions, component choices. Phx Brief is an agent skill from oliver-kriska/claude-elixir-phoenix. Interactive briefing of a plan file — explains reasoning, schema decisions, component choices.

When should I use Phx Brief?

Phx Brief fits situations like: developers need to understand a plan before approving.

How do I install Phx Brief in Claude Code?

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

How do I install Phx Brief in Codex?

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

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

What does Phx Brief need to run?

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

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

Phx Brief 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 Brief 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 3k tokens, read only when the agent opens those files.

What are the alternatives to Phx Brief?

Skills that share tags, products or a category with Phx Brief: MCP Server Builder (anthropics/skills, 180k stars), Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars) and Agent Browser CLI (vercel-labs/agent-browser, 44k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phx Brief?

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 Brief

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

Plan Briefing

Why This Exists

Usage

Arguments

Mode Detection

Execution Flow

Step 1: Locate and Load Plan

Step 2: Load Supporting Artifacts

Step 3: Present Briefing Sections

Section Flow (Pre-Work Mode)

Section Flow (Post-Work Mode)

Iron Laws

Closing Message

Integration

Complex Plan Enhancement

Notes

Files

Compare with similar skills

Similar skills

More from oliver-kriska/claude-elixir-phoenix

Questions about Phx Brief