terminal-discussion-export_skill

This skill exports terminal discussions from TriClaude logs to Google Drive as Markdown, preserving order and removing noise for easy archiving.
  • Python

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yousufjoyian/claude-skills --skill terminal-discussion-export

  • SKILL.md2.9 KB

Overview

This skill exports TriClaude terminal session content to Google Drive as clean Markdown files for archiving or sharing. It preserves the original line order, strips ANSI/control escape noise, and updates a project-level rolling "latest" file. Use it when you need an exact, readable capture of a terminal discussion saved under your Drive workspace.

How this skill works

The script reads the TriClaude runtime stream.log for a specified terminal id, removes control/ANSI escape sequences, and writes the ordered text to a timestamped Markdown file under the configured Drive export root. It also updates a project-level latest_<terminal-suffix>.md file and prints JSON that includes exportFile and latestFile paths for confirmation. The tool accepts options for number of lines, a short note header, and a custom output root.

When to use it

  • Save or archive a terminal discussion after a long troubleshooting session.
  • Share a reproducible terminal transcript with teammates or for documentation.
  • Capture an exact record before restarting or destroying a terminal instance.
  • Maintain a searchable, chronological record of terminal activity per project.
  • Quickly export the most recent N lines for postmortem analysis.

Best practices

  • Prefer the TC_TERMINAL_ID environment variable; fallback script lists project terminals if unknown.
  • Export from live stream.log only; do not edit or synthesize transcript content.
  • Specify an appropriate --lines value to avoid truncation or oversized files.
  • Add a concise --note when the export needs context or a decision summary.
  • Keep default output root unless you explicitly need a different Drive path.
  • Verify the printed JSON and returned exportFile path to confirm success.

Example use cases

  • Archive a debugging session for a bug report and attach the exported Markdown to the ticket.
  • Export the last 1800 lines before handing a project to another engineer.
  • Add a short note and export a CI troubleshooting session for retrospective review.
  • Produce a timestamped record for compliance or audit of important terminal operations.
  • Save a reproducible transcript to include in project documentation under the project subfolder.

FAQ

Run the provided Python fallback snippet to list projects and their terminal ids from the projects.json file.

What confirms a successful export?

The script prints JSON containing exportFile and latestFile paths; check those exact paths in Drive to confirm the saved Markdown.

Can I change how many lines are exported?

Yes—use the --lines option to specify the number of most recent lines to include.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational