New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Phx Brainstorm

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

Brainstorm Elixir/Phoenix features — explore ideas, compare; Use when vague idea, not sure how to approach, or want…

MITAuto-check passedAgent Workflows

Install Phx Brainstorm

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

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

GitHub CLI
$ gh skill install oliver-kriska/claude-elixir-phoenix phx-brainstorm --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/codex/skills/phx-brainstorm .claude/skills/phx-brainstorm && 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/

Facts

Skill name
phx-brainstorm
GitHub stars
565
Token cost
~1.5k tokens
SKILL.md length
609 words
Files
3 (incl. references)
Skills in repo
109
Repo updated
First seen
Licence
MIT

At a glance

Brainstorm Elixir/Phoenix features — explore ideas, compare; Use when vague idea, not sure how to approach, or want…

  • Works in 3 steps: Adaptive Interview → Decision Point → Research (Diverge → Evaluate → Converge)
  • Not sure how to approach
  • SKILL.md covers Usage, Workflow, Phase 1: Adaptive Interview and Phase 2: Decision Point, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Phx Brainstorm is an agent skill from oliver-kriska/claude-elixir-phoenix. Brainstorm Elixir/Phoenix features — explore ideas, compare; Use when vague idea, not sure how to approach, or want…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/interview-techniques.md` and `references/research-integration.md`).

It sits in Agent Workflows, covering Brainstorming and LLM observability. It works with Elixir. 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

  • Not sure how to approach
  • Tasks that involve Brainstorming
  • Tasks that involve LLM observability

Example prompts

  • “/phx-brainstorm”

Workflow steps

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

  1. Adaptive Interview
  2. Decision Point
  3. Research (Diverge → Evaluate → Converge)

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

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

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). 609 words, ~1,498 tokens.

Download SKILL.mdSave it as .claude/skills/phx-brainstorm/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
phx-brainstorm
description
Brainstorm Elixir/Phoenix features — explore ideas, compare; Use when vague idea, not sure how to approach, or want…

Brainstorm — Adaptive Requirements Gathering

Interactive interview → research → synthesis loop. Produces structured interview.md that $elixir-phoenix:phx-plan detects and consumes (skipping clarification).

Usage

text
$elixir-phoenix:phx-brainstorm Add some kind of notification system
$elixir-phoenix:phx-brainstorm Improve authentication security
$elixir-phoenix:phx-brainstorm                    # starts with open question

Workflow

$elixir-phoenix:phx-brainstorm {topic}
    |
    v
[INTERVIEW] ←──────────────────┐
    |                           |
    v (sufficient OR user exit) |
[DECISION POINT]                |
    ├─ Research ──→ [RESEARCH] ─┘
    ├─ Continue interview ──────┘
    ├─ Make a plan ──→ STOP (suggest $elixir-phoenix:phx-plan {slug})
    ├─ Store & exit ──→ STOP (artifacts saved)
    └─ Discuss ──→ freeform ──→ [DECISION POINT]

Phase 1: Adaptive Interview

Create .claude/plans/{slug}/ directory. Start asking ONE question at a time.

Coverage Dimensions

Track coverage across 6 dimensions (0=uncovered, 1=partial, 2=sufficient). Ask Scope early — for "optimize X" topics, ask about boundaries (upstream OK? Local-only? CI vs dev?) before research, not during.

DimTargetSufficient signal
WhatSpecific behavior/featuresConcrete verbs, not "some kind of"
WhyProblem solved, user needClear benefit stated
ScopeIn/out boundariesExplicit exclusions stated
WhereModules, contexts, pagesFile paths or context names mentioned
HowApproach, constraintsAt least one concrete constraint
EdgeError states, scale, auth2+ edge cases identified

Interview is "sufficient" when total score >= 8 out of 12.

Context-Aware Questioning

Before each question, run a brief codebase scan on topics the user mentioned:

  1. User mentions a topic (e.g., "notifications") → run Grep/Glob for related patterns
  2. Use scan results to ground your next question in what actually exists
  3. Unknown/niche topic → suggest research pause before continuing
Signal Detection
  • Vague answer ("maybe", "not sure") → probe deeper on same dimension
  • Niche topic mentioned → "This involves {X}. Want me to research it first?"
  • Detailed answer covering 3+ dimensions → mark all covered, advance
  • No new coverage for 2 consecutive questions → suggest moving to Decision Point

Phase 2: Decision Point

Write interview.md first, then use AskUserQuestion — every option below relies on the saved file. Move past this point only on a formal choice.

  1. Write current state to .claude/plans/{slug}/interview.md

  2. Show coverage summary: "Coverage: What 2/2 | Why 2/2 | Scope 1/2 | ..."

  3. Use AskUserQuestion with EXACTLY these options (4 max — the tool's hard limit; the auto-added "Other" covers freeform discussion):

    • Research — search codebase + internet for approaches (2 agents)
    • Continue interview — ask more questions
    • Make a plan — I'll suggest: $elixir-phoenix:phx-plan .claude/plans/{slug}/interview.md
    • Store & exit — save everything, come back later

  4. Wait for user response. Do NOT proceed without explicit choice

AskUserQuestion discipline: decisions only, never narration or rhetorical check-ins. Every option states concrete impact (what happens, what it costs) so the user can pick without follow-up questions.

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

Phase 3: Research (Diverge → Evaluate → Converge)

First cycle: MAX 2 agents — keep it fast (~2-3 min). Spawn in ONE Tool Use block with run_in_background: true:

  • phoenix-patterns-analyst: "How does this codebase handle {topics}?" Write to .claude/plans/{slug}/research/codebase-scan.md
  • web-researcher: "Elixir/Phoenix approaches to {topics}" Return 500-word summary

Do NOT spawn additional specialist agents in the first cycle. If user wants deeper investigation, they pick "More research" at the next Decision Point — then spawn focused agents for specific questions.

Evaluate — for each approach found:

  • Thesis: why it works for THIS codebase
  • Antithesis: why it might NOT work (scale, complexity, pattern conflicts)

Converge — present 2-3 approaches with honest trade-offs. Do NOT recommend one. Return to Decision Point (AskUserQuestion).

See references/research-integration.md for details.

Iron Laws

  1. NEVER auto-transition to $elixir-phoenix:phx-plan — always present as option, let user choose
  2. ONE question at a time — never dump a question list
  3. Always write artifacts — interview.md is the contract with $elixir-phoenix:phx-plan
  4. Scan codebase between questions — every question must be context-aware
  5. AskUserQuestion at EVERY decision point — never flow past without formal choice. This is the most critical law. After interview, after research, after discuss — ALWAYS present options via AskUserQuestion. Never let conversation skip the checkpoint
  6. STOP after presenting options — do not proceed without user input
  7. MAX 2 agents in first research cycle — deeper dives are subsequent cycles. User picks "More research" to go deeper, not the skill

Integration

$elixir-phoenix:phx-brainstorm ──→ interview.md ──→ $elixir-phoenix:phx-plan (skips clarification)
                                 ──→ $elixir-phoenix:phx-plan --existing (deepens)
                                 ──→ stored for later session

Position: optional upstream of $elixir-phoenix:phx-plan in workflow cycle.

References

  • references/interview-techniques.md — coverage scoring, question templates, scan patterns, signal detection, interview.md format
  • references/research-integration.md — diverge-evaluate-converge, agent spawn templates, approach presentation format

© oliver-kriska, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

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

  • SKILL.md
  • references/interview-techniques.md
  • references/research-integration.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Phx Brainstorm 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 Brainstorm compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phx Brainstorm this skilloliver-kriska/claude-elixir-phoenix565—~1.5kAutomated safety check: PassMIT
Ash Frameworkpodlove/radiator136—~2.1kAutomated safety check: PassMIT
Sentry Elixir SDKgetsentry/sentry-for-ai268—~3.5kAutomated safety check: PassApache-2.0
Elixirstreamband/hydra-srt147—~804Automated safety check: PassApache-2.0
Change CleanupSimon-Initiative/oli-torus119—~3.7kAutomated safety check: PassMIT
Elixir AntipatternsGentleman-Programming/Gentleman-Skills658—~2.1kAutomated safety check: PassMIT

Similar skills

  • Ash Framework

    podlove/radiator

    Use this skill working with Ash Framework or any of its extensions.

    136 GitHub stars~2.1k tokensUpdated 16 days ago
    AI & LLM EngineeringAuto-check passed

  • Sentry Elixir SDK

    getsentry/sentry-for-ai

    Official

    Full Sentry SDK setup for Elixir. An agent skill from getsentry/sentry-for-ai.

    268 GitHub stars~3.5k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

  • Elixir

    streamband/hydra-srt

    A skill your agent uses for Elixir/Phoenix development in this repo: implementing features, refactors, debugging, tests, Ecto changes, and production-safe fixes.

    147 GitHub stars~804 tokensUpdated 24 days ago
    DevelopmentAuto-check passed

  • Change Cleanup

    Simon-Initiative/oli-torus

    Clean up and harden code introduced by the current branch without drifting into broad refactors.

    119 GitHub stars~3.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Elixir Antipatterns

    Gentleman-Programming/Gentleman-Skills

    Core catalog of 8 critical Elixir/Phoenix anti-patterns covering error handling, separation of concerns, Ecto queries, and testing.

    658 GitHub stars~2.1k tokensUpdated 6 mo ago
    DevelopmentAuto-check passed

  • Elixir Expert

    pass-agent/loomkin

    Expert in Elixir, Phoenix Framework, and OTP. An agent skill from pass-agent/loomkin.

    181 GitHub starsUsed in 1 repo~796 tokens
    AI & LLM EngineeringAuto-check passed

More from oliver-kriska/claude-elixir-phoenix

All 109 skills in this repo

  • Codex Ab

    oliver-kriska/claude-elixir-phoenix

    Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict.

    565 GitHub stars~977 tokensUpdated 5 days ago
    Auto-check passed

  • Audit

    oliver-kriska/claude-elixir-phoenix

    Project health audit and health check — architecture, performance, tests, dependencies, code quality.

    565 GitHub stars~2k tokensUpdated 5 days ago
    Auto-check passed

  • Compound Docs

    oliver-kriska/claude-elixir-phoenix

    Searchable Elixir/Phoenix/Ecto solution documentation system with; Use when consulting past solutions…

    565 GitHub stars~528 tokensUpdated 5 days ago
    Auto-check passed

  • Compound Docs

    oliver-kriska/claude-elixir-phoenix

    Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter.

    565 GitHub stars~547 tokensUpdated 5 days ago
    Auto-check passed

  • Deploy

    oliver-kriska/claude-elixir-phoenix

    Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays.

    565 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed

  • Deps Update

    oliver-kriska/claude-elixir-phoenix

    Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo).

    565 GitHub stars~1.4k tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Phx Brainstorm

What does Phx Brainstorm do?

Brainstorm Elixir/Phoenix features — explore ideas, compare; Use when vague idea, not sure how to approach, or want…. Phx Brainstorm is an agent skill from oliver-kriska/claude-elixir-phoenix.

When should I use Phx Brainstorm?

Phx Brainstorm fits situations like: not sure how to approach; tasks that involve Brainstorming; tasks that involve LLM observability.

How do I install Phx Brainstorm in Claude Code?

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

How do I install Phx Brainstorm in Codex?

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

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

What does Phx Brainstorm need to run?

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

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

Phx Brainstorm 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 Brainstorm use?

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

What are the alternatives to Phx Brainstorm?

Skills that share tags, products or a category with Phx Brainstorm: Ash Framework (podlove/radiator, 136 stars), Sentry Elixir SDK (getsentry/sentry-for-ai, 268 stars), Elixir (streamband/hydra-srt, 147 stars) and Change Cleanup (Simon-Initiative/oli-torus, 119 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phx Brainstorm?

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.