Name: freeze
Rating: 63.2 (1 reviews)
Author: alirezarezvani

freeze

/cs:freeze <decision> <days> — Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. Use when an irreversible decision was made under pressure — e.g. a layoff plan or multi-year contract — and deserves a cooling-off lock before execution.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/freeze/SKILL.md

The canonical home for this skill is freeze in alirezarezvani/claude-skills

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable, with concrete file paths, templates, and a sequenced workflow that includes a validation checkpoint. Its main weakness is motivational prose that pads the token budget without adding instructional value.

Suggestions

Trim or remove the 'Why This Beats Just Don't Re-Decide' section and the pattern-matcher intro paragraph; they explain rationale Claude can infer rather than instruct action, improving conciseness.

Add a brief feedback loop to the workflow specifying what to do when the decision record lacks APPROVED status (e.g., route to /cs:boardroom or report and stop), which would close the workflow_clarity gap.

Make abstract workflow steps concrete: specify how to locate and read the decision record and how to verify APPROVED status, so every step is executable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete tables and templates, but includes motivational rationale Claude does not need ('Founders are pattern-matchers; pattern-matching after a tough decision often produces a reversal that's actually just decision fatigue') and a 'Why This Beats Just Don't Re-Decide' section that pads the body. Not a 4 because several sentences are explanatory rather than instructional.	3 / 5
Actionability	Provides concrete, copy-paste-ready guidance: exact file path ('~/.claude/freezes/active.md'), the field to write ('freeze_until: YYYY-MM-DD'), full markdown output templates, and the /cs:unfreeze command. Not a 5 because a few steps remain abstract ('Read the decision record', 'Validate it has APPROVED status') without specifying how.	4 / 5
Workflow Clarity	The 5-step workflow is clearly sequenced with an explicit validation checkpoint (step 2: 'Validate it has APPROVED status') before the mutating write. Not a 5 because there is no feedback loop specifying what to do when validation fails, leaving a minor gap.	4 / 5
Progressive Disclosure	Self-contained single file with well-labeled sections (When to Use, Default Freeze Periods, Workflow, Output, Override, Routing, Related) and clearly signaled cross-skill links. Not a 5 because the body slightly exceeds the simple-skill line and a couple of rationale sections could be trimmed or externalized.	4 / 5
	Total	15 / 20 Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description cleanly states what the skill does and when to use it, with concrete trigger phrases and a distinct command niche. Its only weakness is that it describes a single action rather than enumerating multiple capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('strategic decision') and one concrete action ('Lock a strategic decision for a cooldown period to prevent impulse reversal'), but coverage is a single action rather than a comprehensive set. Not a 4 because the 4-anchor requires several specific actions, and the description offers essentially one.	3 / 5
Completeness	Explicitly answers both what ('Lock a strategic decision for a cooldown period to prevent impulse reversal') and when ('Use when an irreversible decision was made under pressure — e.g. a layoff plan or multi-year contract — and deserves a cooling-off lock before execution'), matching the 5-anchor pattern.	5 / 5
Trigger Term Quality	Includes natural business phrases a founder would say — 'irreversible decision', 'made under pressure', 'layoff plan', 'multi-year contract', 'cooling-off lock' — giving good keyword coverage. Not a 5 because it lacks synonym/extension-level breadth of the 5-anchor example.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — strategic-decision cooldown locking under a distinct /cs:freeze command — with triggers unlikely to fire for unrelated skills, giving minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: .gemini/skills/freeze/SKILL.md
Commit: 19392f7

Reviewed: ~7 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.