Agent skill

Full

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

Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review.

MITAuto-check passedAI & LLM Engineering

Install Full

skills CLI

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

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

GitHub CLI

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

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

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

GitHub CLI

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

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

GitHub CLI

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

--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 full -a gemini-cli

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

GitHub CLI

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

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

At a glance

Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review.

Works in 3 steps: If CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH… → Otherwise, inspect claude --version: the… → If the version cannot be determined,…
Several coordinated workflows
SKILL.md covers Usage, Flags, Workflow Overview and State Machine, plus 4 more sections
Calls claude

What it does

Full is an agent skill from oliver-kriska/claude-elixir-phoenix. Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing plan; use /phx:work.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/cycle-patterns.md`, `references/example-run.md` and `references/execution-steps.md`).

It sits in AI & LLM Engineering, covering LLM observability. 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

Several coordinated workflows
Contexts must ship together

Example prompts

“/full”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

If CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH is a positive integer, use it.
Otherwise, inspect claude --version: the default is 1 in Claude Code
If the version cannot be determined, conservatively use 1.

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
Shell commands in SKILL.md call:
- claude
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

Full loads about 2k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 63 tokens; SKILL.md has 584 words of instructions outside code blocks.

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

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). 584 words, ~1,992 tokens.

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

name: full
description: Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Use when several coordinated workflows or contexts must ship together. NOT for an existing plan; use /phx:work.
effort: high
argument-hint: <feature description> [--codex]

Full Phoenix Feature Development

Execute complete Elixir/Phoenix feature development autonomously: research patterns, plan with specialist agents, implement with verification, Elixir code review. Cycles back automatically if review finds issues.

Usage

/phx:full Add user authentication with magic links
/phx:full Real-time notification system with Phoenix PubSub
/phx:full Background job processing for email campaigns --max-cycles 5
/phx:full Add magic-link auth --codex

Wrong input guard: if the argument is a path to an existing plan file (.claude/plans/*/plan.md), do NOT re-plan it. Say so and run /phx:work {path} instead — the plan phase already happened.

Flags

--codex — Codex CLI joins the review panel on every review cycle, matching /phx:review --codex.
Requires the codex CLI. A missing CLI degrades to a SKIPPED note — the cycle never fails.
Consensus findings (flagged by a Claude agent and codex) are marked HIGH CONFIDENCE.

Workflow Overview

┌──────────────────────────────────────────────────────────────────┐
│                       /phx:full {feature}                        │
├──────────────────────────────────────────────────────────────────┤
│                                                                  │
│  ┌────────┐  ┌────────┐  ┌────────┐  ┌────────┐  ┌────────┐  ┌────────┐  │
│  │Discover│→ │  Plan  │→ │  Work  │→ │ Verify │→ │ Review │→ │Compound│→Done│
│  │ Assess │  │[Pn-Tm] │  │Execute │  │  Full  │  │4 Agents│  │Capture │     │
│  │ Decide │  │ Phases │  │ Tasks  │  │  Loop  │  │Parallel│  │ Solve  │     │
│  └───┬────┘  └────────┘  └────────┘  └───┬────┘  └────────┘  └────────┘     │
│       │                            ↑      │    ↑              │         │
│       ├── "just do it" ────────────┤      │    │              │         │
│       ├── "plan it" ──┐            │      ↓    │              │         │
│       │               ↓            │ ┌────────┐│              │         │
│       │     ┌──────────────┐       │ │Fix     ││ ┌─────────┐ │         │
│       │     │   PLANNING   │       │ │Issues  │└─│ Fix     │←┘         │
│       │     └──────────────┘       │ └───┬────┘  │ Review  │           │
│       │                            │     ↓       │ Findings│           │
│       │                       ┌────┴─────────┐   └────┬────┘           │
│       │                       │   VERIFYING   │←──────┘                │
│       └── "research it" ─────┘  (re-verify)                            │
│            (comprehensive plan)                                         │
│                                                                  │
│  On Completion:                                                  │
│  Auto-compound: Capture solved problems → .claude/solutions/     │
│  Auto-suggest: /phx:document → /phx:learn-from-fix                       │
│                                                                  │
└──────────────────────────────────────────────────────────────────┘

State Machine

STATES: INITIALIZING → DISCOVERING → PLANNING → WORKING →
        VERIFYING → REVIEWING → COMPLETED → COMPOUNDING | BLOCKED

Claude Code nesting compatibility

Before delegating this cycle, determine the effective maximum nesting depth:

If CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH is a positive integer, use it.
Otherwise, inspect claude --version: the default is 1 in Claude Code 2.1.217–2.1.218 and 3 in 2.1.219+.
If the version cannot be determined, conservatively use 1.

Depth 3+ — the full nested topology is available; delegate to phx:workflow-orchestrator as usual.
Depth 1–2 — execute the same state machine in this main session. Read ${CLAUDE_PLUGIN_ROOT}/agents/workflow-orchestrator.md for the phase contract, but spawn leaf research/review specialists directly. Do not spawn workflow-orchestrator, planning-orchestrator, or parallel-reviewer, because those agents need to delegate again. Context supervision may still be spawned directly after its input files exist.

The fallback is a topology change only: preserve the same user decisions, artifacts, verification gates, retry/cycle limits, and review-to-fix loop. Never tell the user to set an environment variable just to make /phx:full work.

Save state in .claude/plans/{slug}/progress.md. If TaskCreate is in your tool list (Sonnet 5+ and Opus 4.8+ omit it unless CLAUDE_CODE_ENABLE_TODO_TOOLS=1; never ToolSearch for it), also create one task per phase at start, mark in_progress on entry and completed on exit:

TaskCreate({subject: "Discover & assess complexity", activeForm: "Discovering..."})
TaskCreate({subject: "Plan feature", activeForm: "Planning..."})
TaskCreate({subject: "Implement tasks", activeForm: "Working..."})
TaskCreate({subject: "Verify implementation", activeForm: "Verifying..."})
TaskCreate({subject: "Review with specialists", activeForm: "Reviewing..."})
TaskCreate({subject: "Capture solutions", activeForm: "Compounding..."})

Set up blockedBy dependencies between phases (sequential).

Run COMPOUNDING phase on COMPLETED to capture solved problems in .claude/solutions/. Suggest /phx:document for docs and /phx:learn-from-fix for quick pattern capture.

Cycle Limits

Setting	Default	Description
`--max-cycles`	10	Max plan→review cycles
`--max-retries`	3	Max retries per task
`--max-blockers`	5	Max blockers before stopping

Stop with INCOMPLETE status when limits exceeded. List remaining work and recommended action.

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

Integration

text

/phx:full = /phx:plan → /phx:work → /phx:verify → /phx:review → (fix → /phx:verify) → /phx:compound

Use Ralph Wiggum Loop for fully autonomous execution:

bash

/ralph-loop:ralph-loop "/phx:full {feature}" --completion-promise "DONE" --max-iterations 50

Iron Laws

NEVER skip verification — Every task must pass mix compile --warnings-as-errors before moving to the next. Run mix test <affected> per-phase, full suite only at final gate
Respect cycle limits — When --max-cycles is exhausted, STOP with INCOMPLETE status. Do not continue indefinitely hoping the next fix works
One state transition at a time — Follow the state machine strictly. Never jump from PLANNING to REVIEWING — each state produces artifacts the next state needs
Discover before deciding — Always run DISCOVERING phase to assess complexity. Skipping it for "simple" features leads to underplanned implementations
Agent output is findings, not fixes — Review agents report issues. Only the WORKING state makes code changes
Skip redundant review agents — In REVIEWING phase: skip verification-runner (work phase already verified), skip iron-law-judge if PostToolUse hooks verified all files. For <200 lines changed, spawn only elixir-reviewer + security-analyzer (if auth files)
Write text where the user needs it — In autonomous mode your text is how the user follows the cycle. Write it at phase transitions (one line: state, cycle N of max, what's next), for decisions that need a reason, and for errors and blockers. Routine tool calls need no preamble.

References

${CLAUDE_SKILL_DIR}/references/execution-steps.md — Detailed step-by-step execution
${CLAUDE_SKILL_DIR}/references/example-run.md — Example full cycle run
${CLAUDE_SKILL_DIR}/references/safety-recovery.md — Safety rails, resume, rollback
${CLAUDE_SKILL_DIR}/references/cycle-patterns.md — Advanced cycling strategies

Files

SKILL.md and 4 other files (references) in plugins/elixir-phoenix/skills/full of oliver-kriska/claude-elixir-phoenix.

SKILL.md
references/cycle-patterns.md
references/example-run.md
references/execution-steps.md
references/safety-recovery.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

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

Full compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Full this skilloliver-kriska/claude-elixir-phoenix	565	—	~2k	Automated safety check: Pass	MIT	3 days ago
Langfuse Codebase Navigatorlangfuse/langfuse	36k	—	~1.4k	Automated safety check: Pass	Custom licence	today
LLM Trace Review Interfaceai-evals-course/evals-skills	1.5k	—	~1.4k	Automated safety check: Pass	Apache-2.0	14 days ago
Langfuse Integration Pagelangfuse/langfuse-docs	247	—	~3.7k	Automated safety check: Pass	MIT	today
Langfuselangfuse/skills	300	—	~2.1k	Automated safety check: Notes	MIT	8 days ago
Livetablegurujada/live_table	211	—	~1.9k	Automated safety check: Pass	MIT	3 mo ago

Similar skills

Langfuse Codebase Navigator
langfuse/langfuse
Navigate Langfuse repositories, code areas, and agent skills.
36k GitHub stars~1.4k tokensUpdated today
AI & LLM EngineeringAuto-check passed
LLM Trace Review Interface
ai-evals-course/evals-skills
Builds a browser-based annotation page for reviewing LLM traces one at a time with pass/fail labels, notes and saved results, tailored to your data.
1.5k GitHub stars~1.4k tokensUpdated 14 days ago
AI & LLM EngineeringAuto-check passed
Langfuse Integration Page
langfuse/langfuse-docs
Create a new Langfuse integration page in the langfuse-docs repo.
247 GitHub stars~3.7k tokensUpdated today
AI & LLM EngineeringAuto-check passed
Langfuse
langfuse/skills
Interact with Langfuse and access its documentation: tracing, monitoring, creating datasets, running experiments, and evaluating AI applications.
300 GitHub stars~2.1k tokensUpdated 8 days ago
AI & LLM EngineeringAuto-check: notes
Livetable
gurujada/live_table
A skill your agent uses when building, modifying, or reviewing Phoenix LiveView tables with LiveTable, including schema-backed tables, context-owned data providers, joined queries, filters…
211 GitHub stars~1.9k tokensUpdated 3 mo ago
AI & LLM EngineeringAuto-check passed
Langsmith Online Eval Engineering
langchain-ai/langsmith-skills
Official
Design, test, create, and attach LangSmith online evaluators for production traces or conversation threads.
159 GitHub stars~1.4k tokensUpdated 6 days ago
AI & LLM EngineeringAuto-check passed

Questions about Full

What does Full do?

Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review. Full is an agent skill from oliver-kriska/claude-elixir-phoenix. Deliver a large, cross-domain Phoenix feature or complete end-to-end system through planning, implementation, verification, and review.

When should I use Full?

Full fits situations like: several coordinated workflows; contexts must ship together.

How do I install Full in Claude Code?

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

How do I install Full in Codex?

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

Can I use Full 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 full -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/full, .gemini/skills/full, .github/skills/full and .opencode/skills/full in your project.

What does Full need to run?

Going by SKILL.md and its folder, Full needs the command-line tools its instructions call (claude).

Does Full 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 Full 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 Full use?

Full 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 Full use?

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

What are the alternatives to Full?

Skills that share tags, products or a category with Full: Langfuse Codebase Navigator (langfuse/langfuse, 36k stars), LLM Trace Review Interface (ai-evals-course/evals-skills, 1.5k stars), Langfuse Integration Page (langfuse/langfuse-docs, 247 stars) and Langfuse (langfuse/skills, 300 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Full?

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.

Install Full

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

Full Phoenix Feature Development

Usage

Flags

Workflow Overview

State Machine

Claude Code nesting compatibility

Cycle Limits

Integration

Iron Laws

References

Files

Compare with similar skills

Similar skills

More from oliver-kriska/claude-elixir-phoenix

Related

Questions about Full