Phx Freeze Skill for Claude

Apply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.

427 tokens

context cost

the whole folder, loaded on every use

files

instructions only

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-freeze

The instruction itself

3 sections, as written by the author

Freeze — advisory edit scope

Apply a current-session instruction that limits which files this agent may edit.

This generated runtime does not install an enforcement hook, so the scope is

advisory rather than a technical lock. Never claim that edits are blocked by the

runtime.

Usage

phx-freeze
phx-freeze lib/app_web priv/repo
phx-freeze status
phx-freeze off

Treat the text after the skill invocation as follows:

| Invocation | Current-session behavior |

|---|---|

| No arguments | Do not edit files; investigation and reporting remain read-only. |

| Path prefixes | Edit only files under the listed project-relative prefixes. |

| status | Report the advisory scope currently established in this conversation. |

| off | Clear the advisory scope for subsequent work. |

Do not create .claude/.freeze. That sentinel belongs to the canonical Claude

Code plugin and could affect a later Claude Code session even though this runtime

cannot enforce or clear it reliably.

Iron Laws

Never describe this scope as enforced — it is a binding instruction for

the current agent, not a runtime or security boundary.

Never create or modify .claude/.freeze in a generated runtime — no

matching enforcement component is installed here.

Honor the active scope until the user clears it or the focused task ends —

ask before editing outside listed prefixes.

Keep paths project-relative — lib/foo includes that directory and its

descendants, not a sibling such as lib/foobar.

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take oliver-kriska/phx-freeze 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.