メニュー
Use when the user wants to export an opencode session transcript as a readable Markdown file — converts a specified session (or the most recent non-active one) into GitHub-flavored Markdown with metadata header, collapsible tool results, and reasoning blocks
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when analyzing a large corpus of text, code, or data that exceeds a single agent's effective context - orchestrates parallel Worker subagents, Critic review subagents, and a final Summarizer subagent with task tracking and failure recovery
Use to decide what kind of basic agent you should use
Use when creating a new opencode plugin or setting up plugin structure - provides complete file organization, manifest format, and component definitions for commands, agents, skills, hooks, and MCP servers
Use when creating specialized subagents for opencode or the task tool - covers description writing for auto-delegation, tool selection, prompt structure, and testing agents
Use when creating, releasing, or maintaining an opencode Plugin Marketplace - covers marketplace.json schema, version management, release checklists, changelog conventions, and validation to prevent sync drift between plugin.json and marketplace.json
Use when completing development phases or branches to identify and update AGENTS.md files that may have become stale - analyzes what changed, determines affected contracts and documentation, and coordinates updates
| name | export-session-as-markdown |
| description | Use when the user wants to export an opencode session transcript as a readable Markdown file — converts a specified session (or the most recent non-active one) into GitHub-flavored Markdown with metadata header, collapsible tool results, and reasoning blocks |
Export an opencode session transcript to a human-readable GitHub-flavored Markdown file.
opencode CLI must be available on PATH (provides opencode session list and opencode export).scripts/reduce-transcript.py (its absolute path is shown in the file list when this skill loads).The user may ask to:
ses_…) or by titleList the current project's sessions:
opencode session list
Session IDs match ses_[A-Za-z0-9]+.
Never export the active session — a session still being written can truncate mid-write. The active session is the most recently updated one (its title matches the running conversation).
If the user gave an output path, use it. Otherwise, default to the current working directory with a descriptive filename:
session-transcript-YYYY-MM-DD.md
If a file with that name already exists, append a counter: session-transcript-YYYY-MM-DD-2.md.
Export the session to JSON, then run scripts/reduce-transcript.py (shipped with this skill; its absolute path is shown in the file list when this skill loads) with the --markdown flag:
opencode export <sessionID> > /tmp/session-export.json
python3 scripts/reduce-transcript.py /tmp/session-export.json "<output_path>" --markdown
Tell the user where the file was written and its size. Example:
Exported session transcript to ./session-transcript-2026-03-20.md (346 KB)
Clean up the intermediate /tmp/session-export.json afterwards.