wiki-crystallize

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

1. Resolve vault and language. Run skillwiki path (fail if NO_VAULT_CONFIGURED) and skillwiki lang.
2. Identify type: entity / concept / comparison / query / summary.
3. Set provenance:. Default research. If in project context: project with provenance_projects: ["[[slug]]"].
4. 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

Disposition: no-op | concept | ADR | work-item | evidence-needed Reason: ... Follow-up: ...

Use exactly one disposition. Keep this as a prompt/template convention; do not add validation or lint enforcement.
4. **Sensitive content guard.** Before writing, scan the source and generated body for live credentials, access keys, tokens, passwords, cookies, bearer headers, or private keys. Redact generated prose before writing. If the source itself contains a live secret and would need to remain raw, STOP instead of preserving it.
5. `skillwiki validate <page>`. If non-zero, STOP.
6. Apply writes: page → `index.md` → `log.md`.
## Stop conditions
- `validate` non-zero.
- Missing `provenance:` for project-context runs.
- Source or generated content contains unredacted live credentials or other authenticating secrets.
## Forbidden
- Filing without explicit `provenance:`.
- Updating `index.md` before `validate` passes.
- Writing host-local absolute paths as canonical durable source references when a portable reference is available (see `using-skillwiki` → Portable Source References).
- Writing `[[wikilinks]]` to pages that don't exist in the vault. Before linking, verify the target exists: check `index.md` or `ls` the target directory. If the target doesn't exist yet, use plain text instead of a wikilink.
- Writing live credentials, access keys, tokens, passwords, cookies, bearer headers, private keys, or other authenticating secrets to the vault.
## Managed writes

Use managed SkillWiki commands (`skillwiki page publish`, `skillwiki archive`) rather than editing root index.md/log.md directly.