agentleFS
Sign inStart free
bighamxbighamx/openclaw-android-node-apk/.agents/skills/agent-transcript/SKILL.md

agent-transcript

Skill59 starsChanged 16 days agoMITView on GitHub

Requested GitHub PR/issue agent transcripts: redact, trim, preview, and insert safely.

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use only when the user explicitly requests a transcript or preview.

    line 8
  2. Very specific:

    Keep the collapsed <details> section and replace existing transcript markers instead of duplicating them.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Transcript

Use only when the user explicitly requests a transcript or preview. Omit by default; never offer one or ask whether to include one during ordinary PR work. A preview request alone does not authorize publication.

Prepare Locally

The helper reads local Codex, Claude, Pi, and OpenClaw logs; no network is used for discovery/rendering. Never upload raw logs.

.agents/skills/agent-transcript/scripts/agent-transcript find \
  --query "$PR_TITLE $BRANCH_OR_PR_URL" --cwd "$PWD" --since-days 14
.agents/skills/agent-transcript/scripts/agent-transcript render \
  --session "$SESSION_JSONL" --out /tmp/agent-transcript.md

find scans the newest 400 matching logs by default; --max-files N widens local discovery. Treat matches as candidates, not proof of scope.

Automatically trim the rendered Markdown before showing, previewing, or inserting it. Keep only task-relevant user prompts, visible decisions, terse tool summaries, and proof outcomes. Use the PR/issue goal, branch, and changed files to remove unrelated earlier/later turns. Drop system/developer prompts, reasoning, raw tool output, environment data, local paths, credentials, browser/session/cookie details, and auth URLs. Inspect the trimmed result; helper redaction is not sufficient disclosure review. Unresolved sensitive content means omit the transcript.

Preview And Insert

Show the trimmed Markdown for a requested preview. If HTML is requested, build the local preview from that trimmed content. The helper's preview, html, and append-body modes render the session again; they do not consume an edited Markdown file and can reintroduce removed turns. Do not use their untrimmed output as the approved artifact.

Insert only the inspected, scoped text when the user's authorization specifically covers publishing that transcript to the named PR/issue. Generating or previewing a transcript does not authorize publication, even when ordinary PR creation or editing is already approved. If that scope is missing, show the trimmed result and obtain publication authorization before insertion. Existing explicit authorization covering transcript publication needs no repeat confirmation. Keep the collapsed <details> section and replace existing transcript markers instead of duplicating them. No safe match means continue the PR work without transcript or placeholder; explain the omission when it prevents the explicitly requested transcript. Do not promote transcript inclusion as a review priority requirement.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free