agent-transcript
Add a redacted agent transcript section to GitHub PR or issue bodies during OpenClaw agent-created PR/issue workflows.
What this skill does
# 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. - 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 ```bash skills/agent-transcript/scripts/agent-transcript --help ``` Find a likely local session: ```bash 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: ```bash skills/agent-transcript/scripts/agent-transcript render \ --session "$SESSION_JSONL" \ --out /tmp/agent-transcript.md ``` Preview one candidate session locally: ```bash 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: ```bash 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 1. Draft the normal PR/issue body first. 2. Run `find` with title, branch, PR URL/number if known, and cwd. 3. 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.` 4. If the user wants preview, run `preview`, open the HTML with `open`, and wait for confirmation. 5. 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. 6. Inspect the trimmed transcript text. If it still includes unrelated earlier/later work, trim again before proceeding. 7. If the user approves, use the enriched trimmed body file for creation/update. 8. 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: ```bash skills/agent-transcript/scripts/agent-transcript html \ --prs /tmp/recent-prs.json \ --out /tmp/agent-transcript-preview.html ```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.