wiki-crystallize

When This Skill Activates

User asks to crystallize, consolidate, or promote draft material into typed-knowledge pages.
A vault is resolvable (see step 0).

Output language

Run skillwiki lang at the start. Generate consolidated page prose and --human summaries in the resolved language. Frontmatter keys, file names, schema headers, index/log structural lines, citation markers, and wikilink slugs MUST stay English.

Pre-orientation reads

Standard four reads. If cwd is inside projects/{slug}/, also read project README and recent work logs.

Steps

Resolve vault and language. Run skillwiki path (fail if NO_VAULT_CONFIGURED) and skillwiki lang.
Identify type: entity / concept / comparison / query / summary.
Set provenance:. Default research. If in project context: project with provenance_projects: ["[[slug]]"].
Compose the page with citations pre-attached. Reuse existing raw/ sources where possible. Every page MUST include:

> **TL;DR:** blockquote as the first content after the title heading — a one-sentence summary of the page's key takeaway (under 200 chars). See SCHEMA.md ## TL;DR Convention.
For pages tagged architecture or explaining workflows/systems: include a Mermaid diagram (graph TB or sequenceDiagram) in the body. Follow Obsidian-compatible Mermaid rules (see SCHEMA.md ## Mermaid Diagrams).
When referring to local repo files in narrative prose, follow using-skillwiki → Portable Source References. For comparison, evaluation-style query, or research-summary pages, end the body with:

## Decision Closeout