# Crystallize

Capture the current session as a reusable skill, staged as a candidate by default, or...

- Repository: https://github.com/kirodotdev/KiroCrew (4711 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kirodotdev/KiroCrew --skill crystallize -g -a claude-code -y`
Codex: `npx skills add kirodotdev/KiroCrew --skill crystallize -g -a codex -y`
Cursor: `npx skills add kirodotdev/KiroCrew --skill crystallize -g -a cursor -y`
Gemini CLI: `npx skills add kirodotdev/KiroCrew --skill crystallize -g -a gemini-cli -y`

## Description

Capture the current session as a reusable skill, staged as a candidate by default, or live only when the user explicitly asks for a live/active skill.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Crystallize a session into a skill

Use this whenever the user asks to capture work as a reusable skill, "crystallize this", "create a skill", "save this as a skill", "make this
reusable", or "turn this into a skill". This is the **on-demand** counterpart to
the automatic post-session skill generation: the user is telling you *now* that
the work is worth keeping.

**Two modes, chosen from the user's wording:**

- **Candidate (default).** Stage the skill in the pending queue for human
  approval. Every phrasing above means this unless the user says otherwise.
- **Live (explicit only).** Write the skill straight to a live,
  immediately-loadable location, bypassing approval. Take this path **ONLY**
  when the user explicitly says "create a live skill" or "create an active
  skill" (or confirms it when asked). Never infer it from a plain "create a
  skill", that stays a candidate.

## When to use

- The user says any trigger phrase above (candidate mode), or explicitly asks
  for a "live" / "active" skill (live mode).
- The session demonstrated a procedure that will **recur**, one a future
  session, working on a DIFFERENT target, would run again substantially
  unchanged: a repeatable debugging method for a class of error, a fixed
  command/API sequence, a verification technique, a research-synthesis flow.

Apply the same recurrence test the automatic pass uses: name the future session
that would load this skill and the different target it would run against. If the
only honest answer reuses this session's own artifact, this bug, this file,
this component, this one question, the procedure does not recur. Effort is not evidence of recurrence: a long, many-step, genuinely difficult session is still one-off if its steps were chosen for one target.

The rest: https://github.com/kirodotdev/KiroCrew/blob/HEAD/src/kiro_crew/builtin_skills/crystallize/SKILL.md