How do I install the Phx Freeze skill?

Run npx skillmds@latest add oliver-kriska/phx-freeze-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Phx Freeze safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Phx Freeze?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Phx Freeze free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Phx Freeze?

oliver-kriska (@oliver-kriska) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Phx Freeze by oliver-kriska — Agent Skill

Name: Phx Freeze
Rating: 4.5 (4 reviews)
Author: oliver-kriska

File contents

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.

Native enforcement option

This skill remains advisory and never creates Claude's .claude/.freeze sentinel. When the generated Amp plugin is installed, use the phx: edit lock palette command for a persistent workspace lock enforced at Amp's tool.call boundary. It blocks Amp-recognized edits outside the selected scope and disables shell tools while active. Unknown third-party mutating tools remain outside Amp's file-classification helper, so this is not complete Claude-hook parity.

---name: phx-freeze-3description: Apply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.---# Freeze — advisory edit scopeApply a current-session instruction that limits which files this agent may edit.This generated runtime does not install an enforcement hook, so the scope isadvisory rather than a technical lock. Never claim that edits are blocked by theruntime.## Usage```textphx-freezephx-freeze lib/app_web priv/repophx-freeze statusphx-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 ClaudeCode plugin and could affect a later Claude Code session even though this runtimecannot enforce or clear it reliably.## Iron Laws1. **Never describe this scope as enforced** — it is a binding instruction for the current agent, not a runtime or security boundary.2. **Never create or modify `.claude/.freeze` in a generated runtime** — no matching enforcement component is installed here.3. **Honor the active scope until the user clears it or the focused task ends** — ask before editing outside listed prefixes.4. **Keep paths project-relative** — `lib/foo` includes that directory and its descendants, not a sibling such as `lib/foobar`.## Native enforcement optionThis skill remains advisory and never creates Claude's `.claude/.freeze`sentinel. When the generated Amp plugin is installed, use the `phx: edit lock`palette command for a persistent workspace lock enforced at Amp's `tool.call`boundary. It blocks Amp-recognized edits outside the selected scope and disablesshell tools while active. Unknown third-party mutating tools remain outsideAmp's file-classification helper, so this is not complete Claude-hook parity.

Frequently asked questions

Phx Freeze