geronimo-iia/llm-wiki-skills/crystallize
Claude Code and agent skill by geronimo-iia/llm-wiki-skills
- community
Checking that the SKILL.md file is still in the repository.
Distil a session into durable wiki pages — extract decisions, findings, and open questions into concept or query-result pages.
Install
npx vskill@latest install geronimo-iia/llm-wiki-skills/crystallizeSKILL.md
Crystallize
Distil a session into durable wiki pages. Valuable knowledge emerges from conversations — decisions reached, patterns discovered, questions resolved. Without crystallization, this knowledge disappears when the session ends.
What to capture
Keep: decisions made, patterns established, lessons learned, open questions, current understanding, key findings, agreed frameworks, design rationale.
Discard: exploratory back-and-forth, dead ends, process chat, superseded drafts, corrections already incorporated.
The output is always significantly shorter and more structured than the input. Crystallize distils — it does not transcribe.
When to crystallize
- A decision was reached → crystallize the decision and rationale
- New knowledge was absorbed → crystallize into a concept page
- A question was resolved → update the page that had the open question
- A design was settled → crystallize into a query-result or concept
- The chat is getting heavy → crystallize before context degrades
- Closing a long thread → crystallize everything worth keeping
Search for an existing home
Before creating anything new, orient with the full wiki map:
This produces all pages grouped by type with summaries — a complete map in a single call. Use it to identify existing pages that may cover the same ground, then search for candidates:
If a concept page, section index, or prior query-result already covers this ground, prefer updating it over creating a new page.
Read candidates to check scope:
Analyse before writing
Before creating or updating any page, produce a concise extraction plan.
For each item of durable knowledge in the session, note:
- What — one sentence describing the knowledge
- Type —
decision,finding,pattern,open-question - Action —
create <type> <slug>,update <slug>, ordiscard - Confidence — estimated score (see calibration table below)
Example plan output:
Present the plan to the user and confirm before writing. This keeps the user in control and prevents the session from producing redundant or misclassified pages.
Confidence calibration for session knowledge
| Knowledge type | Suggested confidence | |
|---|---|---|
| Decision explicitly reached, agreed by all parties | 0.85–0.95 | |
| Pattern observed, confirmed by evidence in session | 0.70–0.85 | |
| Finding confirmed and cross-referenced with existing pages | 0.80–0.95 | |
| Pattern observed, not yet tested broadly | 0.50–0.65 | |
| Hypothesis raised, plausible but unvalidated | 0.30–0.50 | |
| Open question noted, no resolution | 0.20–0.35 | |
| Speculation or brainstorm output | 0.10–0.25 |
These ranges are starting points. Adjust up when the session provided strong evidence (code confirmed to work, multiple independent sources); adjust down when the conclusion was tentative or context-specific.
The default when no calibration applies is 0.5 (neutral — present but unreviewed). Never leave confidence absent on session-derived pages: the lint rule will flag them as stale if they stay at default for long.
Create a new page
When no existing page fits, use type: query-result for session conclusions or type: concept for synthesized knowledge.
Get the frontmatter scaffold:
Create and write:
Set sources to the source pages that contributed claims, concepts to the concept pages discussed. These create typed graph edges (fed-by and depends-on).
Update an existing page
Respect the accumulation contract:
- Read the current page:
wiki_content_read(uri: "<slug>") - Preserve existing list values (
tags,aliases,read_when,sources,
concepts, claims) — add, do not replace
- Update scalar fields (
summary,tldr,confidence) only with
clear reason
- Write the complete file:
Validate and index
Dry-run to catch errors (including edge target type mismatches):
Then ingest for real:
Check structural quality
After ingest, run the engine lint for the pages just written:
This catches:
- Dead references in
sources,concepts, or body wikilinks introduced
by the new pages
- Orphan pages if the new page was not linked from anywhere
Fix any Error findings before closing the session. Warning findings (orphan on a newly created standalone page) can be deferred.
Verify
Confirm the knowledge was captured correctly:
Check graph edges are connected as expected:
Suggest links for the new page:
Suggested body structure
Adapt to the content — not every section is needed:
| Section | When to include | |
|---|---|---|
| Summary | Always — 2–4 sentences of what was established | |
| Decisions | When decisions were made | |
| Findings | When new knowledge was discovered | |
| Current Understanding | When the session advanced understanding | |
| Open Questions | When questions remain unresolved | |
| Related Pages | When connections to other wiki pages are worth noting |
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/crystallize/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/geronimo-iia/llm-wiki-skills/crystallize)