$ ~/registry/skill/openclaw-agents-skills-agent-transcript

SKILL

agent-transcript

Name: agent-transcript
Author: openclaw

Automatically add redacted agent transcripts to GitHub PRs or issues.

Stars

★ 390,422

Source

GitHub

Updated

2026-09-25

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 390.4k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "agent-transcript" skill from askskill:
1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/agent-transcript/SKILL.md
2. Save it as ~/.claude/skills/agent-transcript/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Add a redacted transcript to an agent-created PR

Prompt

Append an 'Agent Transcript' section to a GitHub PR body created by OpenClaw, and redact secrets, tokens, and sensitive paths.

Expected

The PR body includes a redacted agent transcript section for review and traceability.

Attach an action transcript to an auto-created issue

Prompt

When OpenClaw automatically creates a GitHub issue, add the agent action transcript to the body and hide credentials, emails, and internal links.

Expected

The issue body contains a clear redacted transcript so the team can understand the agent workflow.

Standardize audit details in agent workflows

Prompt

Insert a standardized redacted transcript block into all OpenClaw-generated PRs and issues, keeping key steps while removing sensitive content.

Expected

All related PRs and issues include consistently formatted redacted audit transcripts.

// docs

Agent Transcript

Best-effort local-only provenance for OpenClaw PR/issue bodies. Use during agent-created GitHub PR or issue workflows before creating/updating the body.

Contract

Never use network. Session discovery reads local agent logs only.
Never upload raw logs. Render sanitized Markdown first.
Always ask the user before adding transcript logs to a GitHub PR/issue body.
Tell the user sanitized session logs help reviewers and can make PRs easier to prioritize.
Offer a local HTML preview before insertion. If the user wants preview, open it 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.
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

.agents/skills/agent-transcript/scripts/agent-transcript --help

Find a likely local session:

.agents/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.

Render a PR/issue body section:

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

Preview one candidate session locally:

.agents/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:

.agents/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

Draft the normal PR/issue body first.
Run find with title, branch, PR URL/number if known, and cwd.
If a high-confidence session is found, ask: Include a redacted agent transcript? It helps reviewers and can make the PR easier to prioritize. I can open a local preview first.
If the user wants preview, run preview, open the HTML with open, and wait for confirmation.
Before insertion, trim unrelated session turns from the generated section. Keep only turns that explain this PR/issue's goal, implementation choices, files, tests, proof, blockers, and final outcome.
If the user approves, run append-body.
Use the enriched body file for creation/update.
If no safe session is found, say nothing and continue without transcript. If the user declines, continue without transcript and do not add any transcript 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:

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

Submit, fetch, and verify tamper-evident audit proofs for AI agents.

—Get→

$ loading_