agentleFS
Sign inStart free
spongetimblinspongetimblin/claude-skill-library/skills/transcript-path/SKILL.md

transcript-path

Skill1 starsChanged 5 days agoMITView on GitHub

Give the user the full local file path of the transcript (.jsonl) of the Claude Code session they are in right now. The usual flow is typing /transcript-path on its own, often as a side question in the middle of other work. Also trigger when the user asks for it in words, such as "give me the local file path for the transcript of this Claude Code session", "what's the path to this session's transcript" or "where is this conversation's jsonl". Not for finding a different or older session's transcript, or for exporting, reading or summarizing a transcript.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. tz5514/zet-agent-skills-dist★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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. Very specific:

    Every Claude Code session writes its transcript to ~/.claude/projects/<working folder, with / and other punctuation turned into ->/<session …

    line 9
  2. Distinctive:

    Add one short sentence only when the lookup above is off:

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

transcript-path

Every Claude Code session writes its transcript to ~/.claude/projects/<working folder, with / and other punctuation turned into ->/<session ID>.jsonl. This session's ID is ${CLAUDE_SESSION_ID}, and looking it up finds:

!find ~/.claude/projects -maxdepth 2 -name ${CLAUDE_SESSION_ID}.jsonl

Reply

Give the path in a fenced code block with no language tag, and nothing else. The user pastes the path into other sessions and tools, so the code block's copy button is what they need. The file's size, format and session ID are noise unless they ask.

Add one short sentence only when the lookup above is off:

  • Two paths. Renaming the session's working folder, or moving the session to a different folder, leaves a stale copy under the old folder's name. Run ls -lt on both, give the most recently modified one, and name the other as a stale copy.
  • No path. The file is created when the session's first message is saved, so the lookup can come up empty if this is the first message. Run the same find with the Bash tool. If the session ID above shows as a variable name rather than an ID, use $CLAUDE_CODE_SESSION_ID in its place. If the file is still missing, say so. Do not fall back to the newest file in the project folder, because another session open in the same working folder would make that the wrong file.

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