New to Claude Skills? Learn how to install them →

steipete on GitHub

Agent Transcript

Free

Safely manage agent session transcripts for PRs and issues.

Get this skill

Free · Opens the source repo

What Agent Transcript does

The Agent Transcript skill provides a way to manage and insert transcripts of agent sessions into GitHub pull requests (PRs) and issues. It focuses on preserving user privacy and security by ensuring that sensitive information is never shared. This skill is particularly useful for developers who want to document their coding sessions while maintaining confidentiality. By using this skill, users can redact sensitive information and provide a sanitized version of their session logs when explicitly requested.

This skill operates entirely on local logs and does not require any network access. It reads from the user's local agent logs, which allows it to generate transcripts that are tailored to specific PRs or issues. Users can request a preview of the transcript before it is inserted, ensuring that they have control over what information is shared. The skill automatically trims unnecessary details from the logs, focusing only on relevant information related to the PR or issue at hand, such as goals, implementation choices, and outcomes.

The workflow for using the Agent Transcript skill is straightforward. After drafting the PR or issue body, users can run a command to find relevant session logs based on the title or branch name. If a preview is requested, the skill generates an HTML preview for user confirmation. Once approved, the skill appends the sanitized transcript to the PR or issue body. This process not only enhances documentation but also provides a clear narrative of the development process without exposing sensitive data.

Overall, the Agent Transcript skill is designed for developers who need to document their work while adhering to best practices in data privacy. It streamlines the process of including relevant session information in PRs and issues, making it an essential tool for maintaining clear and secure project documentation.

When to use it

Use this skill when you need to include a transcript of an agent session in a GitHub PR or issue while ensuring privacy and security.

When not to use it

This skill is not suitable for use cases where network access is required or when you do not need to document agent sessions.

What you can build with it

Documenting a PR

When creating a pull request, use the skill to safely include relevant session logs that explain your code changes.

Previewing Session Logs

Before submitting an issue, request a preview of the session logs to ensure no sensitive information is included.

Maintaining Privacy in Team Projects

In collaborative projects, use the skill to document agent sessions without exposing private keys or sensitive data.

How to install Agent Transcript

View source

1. Install with the skills CLI

npx skills add steipete/agent-scripts/agent-transcript --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by steipete

Agent Transcript

Best-effort local-only provenance for OpenClaw PR/issue bodies. Use only when the user explicitly requests a transcript or preview.

Contract

  • Never use network. Session discovery reads local agent logs only.
  • Never upload raw logs. Render sanitized Markdown first.
  • Omit transcripts by default; do not offer or ask about them.
  • If explicitly requested, offer a local HTML preview before insertion and wait for confirmation before adding the section.
  • Fail closed on unresolved secrets, private keys, browser/session/cookie details, or auth URLs.
  • Drop system/developer prompts, raw tool outputs, reasoning, env, cookies, tokens, and broad local paths.
  • Keep user prompts, assistant visible decisions, terse tool summaries, and test/proof outcomes.
  • Automatically trim the rendered transcript before showing it, previewing it, or inserting it into a public body. Never paste the raw full-session render into a PR/issue body just because render or append-body produced it.
  • Remove session turns unrelated to the PR/issue work. Use the PR/issue title, branch name, changed files, and stated goal as scope; omit earlier/later unrelated tasks even when they are in the same session log.
  • Best effort only: PR/issue creation must continue if no safe transcript is found.
  • Add the ## Agent Transcript section only when inserting a real transcript. Never add a placeholder transcript heading or text such as "A sanitized local transcript preview was generated but not included."
  • Use a collapsed <details> section and update existing markers instead of duplicating sections.

Helper

skills/agent-transcript/scripts/agent-transcript --help

Find a likely local session:

skills/agent-transcript/scripts/agent-transcript find \
  --query "$PR_TITLE $BRANCH_OR_PR_URL" \
  --cwd "$PWD" \
  --since-days 14

find scans the newest 400 matching local JSONL logs by default across Codex, Claude, Pi, and OpenClaw agent sessions. Use --max-files N for a wider local search.

In a downstream repo that syncs shared skills under .agents/skills, replace skills/agent-transcript with .agents/skills/agent-transcript.

Render a PR/issue body section:

skills/agent-transcript/scripts/agent-transcript render \
  --session "$SESSION_JSONL" \
  --out /tmp/agent-transcript.md

Preview one candidate session locally:

skills/agent-transcript/scripts/agent-transcript preview \
  --session "$SESSION_JSONL" \
  --out /tmp/agent-transcript-preview.html
open /tmp/agent-transcript-preview.html

Append/update a body file before gh pr create --body-file or connector PR creation:

skills/agent-transcript/scripts/agent-transcript append-body \
  --body /tmp/pr-body.md \
  --session "$SESSION_JSONL" \
  --out /tmp/pr-body.with-transcript.md

PR/Issue Workflow

Run this workflow only after the user explicitly requests a transcript or preview.

  1. Draft the normal PR/issue body first.
  2. Run find with title, branch, PR URL/number if known, and cwd.
  3. If preview was requested, run preview, open the HTML, and wait for confirmation.
  4. Render or append to a temp body, then automatically trim the ## Agent Transcript section before showing it to the user or inserting it publicly. Keep only turns that explain this PR/issue's goal, implementation choices, files, tests, proof, blockers, and final outcome.
  5. Inspect the trimmed transcript text. If it still includes unrelated earlier/later work, trim again before proceeding.
  6. Use the enriched trimmed body file only after the user approves it.
  7. If no safe session is found or the user declines, continue without a transcript or placeholder section.

Review Artifacts

For manual audits across many PR/session candidates, create a local HTML preview from a local JSON file. This is for maintainers only and is not part of the PR/issue workflow:

skills/agent-transcript/scripts/agent-transcript html \
  --prs /tmp/recent-prs.json \
  --out /tmp/agent-transcript-preview.html

Frequently asked questions about Agent Transcript

Similar skills