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 Recall

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

Recall prior work from past sessions — how a bug was fixed, what was; Use when asked 'have we done this before'…

MITAuto-check passed

Install Phx Recall

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

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

GitHub CLI
$ gh skill install oliver-kriska/claude-elixir-phoenix phx-recall --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-recall .claude/skills/phx-recall && 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-recall
GitHub stars
565
Token cost
~849 tokens
SKILL.md length
338 words
Files
2 (incl. references)
Skills in repo
109
Repo updated
First seen
Licence
MIT

At a glance

Recall prior work from past sessions — how a bug was fixed, what was; Use when asked 'have we done this before'…

  • Works in 4 steps: Cheapest layer first — solution docs… → ONE ccrider fetch = ONE subagent —… → Cite the evidence — every claim names… → …
  • Asked have we done this before…
  • SKILL.md covers Usage, Iron Laws, Workflow and Integration, plus 1 more section
  • Calls git

What it does

Phx Recall is an agent skill from oliver-kriska/claude-elixir-phoenix. Recall prior work from past sessions — how a bug was fixed, what was; Use when asked 'have we done this before'…

Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/archaeology-patterns.md`).

It works with Model Context Protocol. 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

  • Asked have we done this before…

Example prompts

  • “have we done this before”
  • “/phx-recall”

Workflow steps

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

  1. Cheapest layer first — solution docs (local grep) → git history →
  2. ONE ccrider fetch = ONE subagent — get_session_messages responses
  3. Cite the evidence — every claim names its source (solution doc
  4. Graceful degradation, stated plainly — if ccrider MCP is absent,

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:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

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

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~849
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.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). 338 words, ~849 tokens.

Download SKILL.mdSave it as .claude/skills/phx-recall/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
phx-recall
description
Recall prior work from past sessions — how a bug was fixed, what was; Use when asked 'have we done this before'…

Recall — Session & History Archaeology

Search three evidence layers, cheapest first, to answer "have we solved this before?". Stop at the first layer that answers the question.

Usage

$elixir-phoenix:phx-recall how did we fix the LiveView form that saved silently?
$elixir-phoenix:phx-recall what did we decide about the billing context boundaries?
$elixir-phoenix:phx-recall which library did we pick for rate limiting and why?

Iron Laws

  1. Cheapest layer first — solution docs (local grep) → git history → session transcripts. Don't fetch sessions when a solution doc answers
  2. ONE ccrider fetch = ONE subagent — get_session_messages responses are 3–15KB each. Spawn a subagent per session that writes a summary file and exits; NEVER batch multiple session fetches into one context
  3. Cite the evidence — every claim names its source (solution doc path, commit hash, or session date + match snippet). No vague "we did this once"
  4. Graceful degradation, stated plainly — if ccrider MCP is absent, say so once and use the fallback layers; never error out

Workflow

Layer 1: Compound Solution Docs (always)

Run Grep with keywords from the question over .claude/solutions/. Treat a hit here as the best answer — it was written for exactly this purpose. Present it and stop unless the user wants more.

Layer 2: Git Archaeology (always available)
bash
git log --oneline --grep="{keyword}" -i -20      # commit messages
git log -S "{code-symbol}" --oneline -10          # when a symbol changed
git log --follow --oneline -10 -- {file}          # one file's history
git show {hash} --stat                            # inspect a candidate

Use -S (pickaxe) when the question names code; --grep when it names intent. Show matching commits with one-line context each.

Layer 3: Session Transcripts (ccrider MCP, gated)

Check for mcp__ccrider__* tools (load via ToolSearch if deferred).

If absent: report "ccrider MCP not connected — answered from solution docs + git history" and stop after Layers 1–2.

If present:

  1. mcp__ccrider__search_sessions with the question's key phrases — returns ranked hits with session IDs and snippets
  2. Present the top 3–5 hits (date, snippet) and pick the most relevant (or ask, if genuinely ambiguous)
  3. Per selected session, spawn ONE subagent: "Fetch session {id} via mcp__ccrider__get_session_messages, extract only what answers '{question}', write ≤30 lines to .claude/recall/{id}.md" (Iron Law 2)
  4. Read the summary files, synthesize the answer with citations
Step 4: Answer + Compound

Present the answer with its evidence trail. If the recalled knowledge was NOT already in .claude/solutions/, offer $elixir-phoenix:phx-compound so the next recall stops at Layer 1.

Integration

text
"have we done this before?" → $elixir-phoenix:phx-recall
   Layer 1 .claude/solutions/ ──hit──► answer + cite
   Layer 2 git log --grep/-S  ──hit──► answer + cite
   Layer 3 ccrider sessions (gated) ─► answer + cite → offer $elixir-phoenix:phx-compound

References

  • references/archaeology-patterns.md — git pickaxe recipes, ccrider query patterns, subagent prompt template

© 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 1 other file (references) in targets/codex/skills/phx-recall of oliver-kriska/claude-elixir-phoenix.

  • SKILL.md
  • references/archaeology-patterns.md

Open the folder on GitHubat commit 9767a82

Compare with similar skills

Phx Recall 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 Recall compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Phx Recall this skilloliver-kriska/claude-elixir-phoenix565—~849Automated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Figma use_figma Plugin API Ruleswarpdotdev/warp65k4 repos~4.4kAutomated safety check: PassAGPL-3.0
Stitch to Remotion Walkthrough Videosgoogle-labs-code/stitch-skills8.5k6 repos~3.2kAutomated safety check: NotesApache-2.0

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

  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed

  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed

  • Figma use_figma Plugin API Rules

    warpdotdev/warp

    Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.

    65k GitHub starsUsed in 4 repos~4.4k tokens
    Frontend & DesignAuto-check passed

  • Stitch to Remotion Walkthrough Videos

    google-labs-code/stitch-skills

    Official

    Builds walkthrough videos from Stitch design projects using Remotion, with transitions, zoom effects and text overlays on each screen.

    8.5k GitHub starsUsed in 6 repos~3.2k tokens
    Media & CreativeAuto-check: notes

  • MCP Development

    coollabsio/coolify

    A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 1 repo~949 tokens
    Frontend & DesignAuto-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

Questions about Phx Recall

What does Phx Recall do?

Recall prior work from past sessions — how a bug was fixed, what was; Use when asked 'have we done this before'…. Phx Recall is an agent skill from oliver-kriska/claude-elixir-phoenix.

When should I use Phx Recall?

Phx Recall fits situations like: asked have we done this before….

How do I install Phx Recall in Claude Code?

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

How do I install Phx Recall in Codex?

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

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

What does Phx Recall need to run?

Going by SKILL.md and its folder, Phx Recall needs the command-line tools its instructions call (git).

Does Phx Recall access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Phx Recall 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 Recall use?

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

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

What are the alternatives to Phx Recall?

Skills that share tags, products or a category with Phx Recall: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Phx Recall?

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.