Save Claude Code Q&A conversations as structured Obsidian-compatible knowledge notes, or rewrite fact-checks into corporate-friendly Teams publish format. Use when user wants to persist conversation content as a markdown file, or rewrite analysis for team sharing.
Save Claude Code conversations as structured Obsidian-compatible knowledge notes. Supports three modes: Standard (reorganizes Q&A into encyclopedia-style articles with tables, Mermaid diagrams, and source links), Direct write (preserves source content verbatim without restructuring), and Teams publish (rewrites fact-checks into a corporate-friendly "extended analysis" format for group sharing — displayed in conversation and appended to the same note file).
Use when the user says any of:
This skill has three writing modes:
| Mode | Behavior | Output | Default? |
|---|---|---|---|
| Standard | Restructure Q&A into encyclopedia-style knowledge article |
| Write to file |
| Yes |
| Direct write | Save source content verbatim — no restructuring, no rewriting | Write to file | No |
| Teams publish | Rewrite fact-check/analysis into corporate-friendly "extended analysis" format | Display in conversation + append to note file | No |
Teams publish triggers:
Direct write triggers:
Standard triggers: everything else (default).
If ambiguous, ask:
要我整理成知識筆記、原文直接存檔、還是改寫成 Teams 發佈版?
Determine what to save:
Ask the user to confirm:
If Teams publish mode: skip to Step 2T. If direct write mode: skip to Step 2D. Otherwise continue below.
Do NOT produce a verbatim conversation transcript. Instead, reorganize the Q&A into a structured knowledge article:
Structure template:
---