mcpbeat

Phx Intro

oliver-kriska/claude-elixir-phoenix-phx-intro

Walk through the Elixir/Phoenix plugin commands, workflow; Use when a new user wants to learn what the plugin offers…

5k tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
514
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill phx-intro

What comes with it

18 366 bytes besides the instruction
references/tutorial-content.md

What it tells the agent to use

found in the instruction text
Task spawns other agents

The instruction itself

8 sections, as written by the author

Plugin Introduction Tutorial

Interactive walkthrough of the Elixir/Phoenix plugin in 6 sections (~5 min).

Arguments

  • $ARGUMENTS may contain --section N to jump to a specific section (1-6)
  • No arguments = start from Section 1

Execution Flow

  • Read references/tutorial-content.md for all section content
  • Parse $ARGUMENTS for --section N flag (1-6)
  • If --section N specified, jump directly to that section
  • Otherwise start from Section 1

Section Presentation Loop

For each section:

  • Present the section content completely — do NOT abbreviate or summarize. Every paragraph, table, and code block in the reference file must appear in output

— as visible response text emitted BEFORE the AskUserQuestion call; content composed only in thinking is invisible to the user

  • After presenting, use AskUserQuestion with options:
  • If sections remain: "Next: [next section title]", "Skip to Cheat Sheet", "Stop here"
  • If on final section (6): no question needed, end with closing message

Section Titles

| N | Title |

|---|-------|

| 1 | Welcome |

| 2 | Core Workflow Commands |

| 3 | Knowledge & Safety Net |

| 4 | Hooks & Behavioral Rules |

| 5 | Init, Review & Gaps |

| 6 | Cheat Sheet & Next Steps |

Iron Laws

  • ONE section at a time — never dump all content at once
  • User controls pace — always offer to stop between sections
  • Clean formatting — use tables and code blocks, not walls of text
  • NEVER skip the user's questions — tutorial is interactive, not a monologue; if the user asks a question mid-section, answer it before continuing

Closing Message

After Section 6 (or when user stops):

You're all set! Try `$elixir-phoenix:phx-plan` with your next feature to see the workflow in action.
Run `$elixir-phoenix:phx-intro --section N` anytime to revisit a specific section.

Notes

  • This runs in main conversation context (not a subagent)
  • Reference file is readable since skill runs in user's session
  • Keep tone welcoming but concise — developers don't want fluff

How to use it

Copy the folder

Take oliver-kriska/claude-elixir-phoenix-phx-intro from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.