Plugin Dev Workflow (Elixir/Phoenix plugin repo)
Enforces the edit → eval → lint → test → commit workflow when modifying skills, agents, hooks, or the eval framework inside the claude-elixir-phoenix repo.
Dev & CodingIntermediate★ 535⑂ 38AI score 7/10Last updated: Aug 27, 2026
What it does
- Triggers when you edit files under
plugins/elixir-phoenix/,lab/eval/, orlab/autoresearch/and imposes a standard sequence of checks. - Spells out skill requirements the scorer enforces: frontmatter (name, description starting with an action verb plus "Use when..."), an Iron Laws section, 185/150 line caps, 45-line section cap, and valid
/phx:andreferences/*.mdpaths. - Covers agent rules:
permissionMode: bypassPermissions,disallowedToolsfor review agents, model/effort matching (haiku/sonnet/opus), and line limits. - Gives exact CLI invocations (
make eval,make eval-all,make test,make ci,python3 -m lab.eval.scorer <file>), with an explicit warning never to run scorer.py directly. - Ends with a pre-commit checklist including CHANGELOG and plugin.json version bumps, plus the autoresearch self-improvement loop.
Who it's for
- Contributors to or forkers of the claude-elixir-phoenix plugin repository.
- Anyone studying how to build a plugin repo with an automated skill-quality scoring pipeline.
- Teams customizing Claude Code tooling for Elixir/Phoenix.
Examples
- Edit
skills/verify/SKILL.md, runmake evalto score only changed skills, fix the failing dimension, runmake lint, then commit. - Add a new agent and run
make eval-agentsto confirm permission mode and model/effort alignment. - Add a matcher in
lab/eval/, add tests inlab/eval/tests/test_matchers.py, runmake test, thenmake eval-allto check for regressions.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/oliver-kriska/claude-elixir-phoenix/HEAD/.claude/skills/plugin-dev-workflow/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the .claude/skills/plugin-dev-workflow folder from the GitHub repo oliver-kriska/claude-elixir-phoenix into my ~/.claude/skills/plugin-dev-workflow/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/oliver-kriska/claude-elixir-phoenix.git && mkdir -p ~/.claude/skills && cp -r claude-elixir-phoenix/.claude/skills/plugin-dev-workflow ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal and go to your projects folder.
- Clone the repo:
git clone https://github.com/oliver-kriska/claude-elixir-phoenix.git - Create the skills folder:
mkdir -p ~/.claude/skills - Copy the skill:
cp -r claude-elixir-phoenix/.claude/skills/plugin-dev-workflow ~/.claude/skills/ - Because the skill only makes sense inside this repo, the practical move is to run Claude Code from the cloned
claude-elixir-phoenixdirectory. - Prerequisites:
make,python3, and the repo's Python dependencies (pytest and friends). Runmake helpto list available targets. - Ask Claude something like "I'm editing a SKILL.md here — follow the plugin dev workflow" to trigger it.
View source on GitHub ↗License: MIT