Agent skill

Session Logs

by z80dev in z80dev/lemon

Search and analyze your own Lemon session logs (older/parent conversations) using jq.

MITAuto-check passedBackend & APIs

Install Session Logs

skills CLI
$ npx skills add z80dev/lemon --skill session-logs -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install z80dev/lemon session-logs --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/z80dev/lemon.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/lemon_skills/priv/builtin_skills/session-logs .claude/skills/session-logs && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
session-logs
GitHub stars
131
Token cost
~949 tokens
SKILL.md length
213 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Search and analyze your own Lemon session logs (older/parent conversations) using jq.

  • Backend & APIs work in your project
  • SKILL.md covers Trigger, Location, Structure and Common Queries, plus 2 more sections
  • Calls jq and rg

What it does

Session Logs is an agent skill from z80dev/lemon. Search and analyze your own Lemon session logs (older/parent conversations) using jq.

Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs. The repository describes itself as: BEAM-native platform for LLM agents: OTP-supervised per-run processes, pluggable engines and channels, contract-tested extension points, and a deterministic multi-agent sim arena. The licence is MIT.

When your agent uses it

  • Backend & APIs work in your project

Example prompts

  • “/session-logs”

What it can do on your machine

Read from SKILL.md and the folder at commit 899e215. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq
    • rg

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Session Logs loads about 949 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 213 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~949

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from z80dev/lemon at commit 899e215, republished under its MIT licence (© z80dev). 213 words, ~949 tokens.

Download SKILL.mdSave it as .claude/skills/session-logs/SKILL.md (or your agent's skills folder).
name
session-logs
description
Search and analyze your own Lemon session logs (older/parent conversations) using jq.

session-logs

Search your complete conversation history stored in Lemon session JSONL files. Use this when a user references older/parent conversations or asks what was said before.

Trigger

Use this skill when the user asks about prior chats, parent conversations, or historical context that isn't in current memory files.

Location

Session logs live under ~/.lemon/agent/sessions/ and are organized by encoded working directory name:

  • <encoded-cwd>/*.jsonl - Full conversation transcript per session

For example: ~/.lemon/agent/sessions/--home-user-project--/2026...jsonl

The first line in each .jsonl is a session header with metadata.

Structure

Each .jsonl file contains messages with:

  • type: "session" (metadata header) or "message" (conversation entries)
  • timestamp: Epoch timestamp
  • message.role: "user", "assistant", etc.
  • message.content[]: Text, thinking, or tool calls (filter type=="text" for human-readable content)
  • message.usage.cost.total: Cost per response

Common Queries

List all sessions by date and size
bash
for f in ~/.lemon/agent/sessions/*/*.jsonl; do
  ts=$(jq -r 'select(.type=="session") | .timestamp' "$f")
  size=$(wc -c <"$f")
  started="$(date -r "$((ts / 1000))" '+%F %T' 2>/dev/null || printf 'ts=%s' "$ts")"
  echo "$started $size $(basename "$f")"
done | sort -r
Find sessions from a specific day
bash
for f in ~/.lemon/agent/sessions/*/*.jsonl; do
  ts=$(jq -r 'select(.type=="session") | .timestamp' "$f")
  day="$(date -r "$((ts / 1000))" '+%F' 2>/dev/null || true)"
  [[ "$day" == "2026-01-06" ]] && echo "$f"
done
Extract user messages from a session
bash
jq -r 'select(.type=="message" and .message.role == "user") | .message.content[]? | select(.type == "text") | .text' <session>.jsonl
Search for keyword in assistant responses
bash
jq -r 'select(.type=="message" and .message.role == "assistant") | .message.content[]? | select(.type == "text") | .text' <session>.jsonl | rg -i "keyword"
Get total cost for a session
bash
jq -s '[.[] | select(.type=="message") | .message.usage.cost.total // 0] | add' <session>.jsonl
Daily cost summary
bash
for f in ~/.lemon/agent/sessions/*/*.jsonl; do
  day="$(date -r "$(( $(jq -r 'select(.type=="session") | .timestamp' "$f") / 1000 ))" '+%F' 2>/dev/null || continue)"
  cost=$(jq -s '[.[] | select(.type=="message") | .message.usage.cost.total // 0] | add' "$f")
  echo "$day $cost"
done | awk '{a[$1]+=$2} END {for(d in a) print d, "$"a[d]}' | sort -r
Count messages and tokens in a session
bash
jq -s '{
  messages: length,
  user: [.[] | select(.type=="message" and .message.role == "user")] | length,
  assistant: [.[] | select(.type=="message" and .message.role == "assistant")] | length,
  first: .[0].timestamp,
  last: .[-1].timestamp
}' <session>.jsonl
Tool usage breakdown
bash
jq -r '.message.content[]? | select(.type == "toolCall") | .name' <session>.jsonl | sort | uniq -c | sort -rn
Search across ALL sessions for a phrase
bash
rg -l "phrase" ~/.lemon/agent/sessions/*/*.jsonl

Tips

  • Sessions are append-only JSONL (one JSON object per line)
  • Large sessions can be several MB - use head/tail for sampling
  • ~/.lemon/agent/sessions is the session root in Lemon
  • No separate sessions.json index file exists for logs

Fast text-only hint (low noise)

bash
jq -r 'select(.type=="message") | .message.content[]? | select(.type=="text") | .text' ~/.lemon/agent/sessions/*/*.jsonl | rg 'keyword'

© z80dev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in apps/lemon_skills/priv/builtin_skills/session-logs of z80dev/lemon.

Open the folder on GitHubat commit 899e215

Compare with similar skills

Session Logs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Session Logs compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Session Logs this skillz80dev/lemon131—~949Automated safety check: PassMIT
Configuring Horizoncoollabsio/coolify63k4 repos~898Automated safety check: PassMIT
Nestjs Best Practicesrolling-scopes/rsschool-app10k6 repos~1.2kAutomated safety check: PassMIT
Sub2API AdminWei-Shaw/sub2api43k1 repos~717Automated safety check: PassLGPL-3.0
Firecrawl Build Onboardingfirecrawl/firecrawl189k1 repos~1.4kAutomated safety check: NotesISC
Obsidian BasesAtmosphere/atmosphere3.8k22 repos~3.2kAutomated safety check: PassApache-2.0

Similar skills

  • Configuring Horizon

    coollabsio/coolify

    A skill your agent uses whenever the user mentions Horizon by name in a Laravel context.

    63k GitHub starsUsed in 4 repos~898 tokens
    Backend & APIsAuto-check passed
  • Nestjs Best Practices

    rolling-scopes/rsschool-app

    NestJS best practices and architecture patterns for building production-ready applications.

    10k GitHub starsUsed in 6 repos~1.2k tokens
    Backend & APIsAuto-check passed
  • Sub2API Admin

    Wei-Shaw/sub2api

    Manages a Sub2API deployment from the command line: accounts, redeem and invitation codes, groups, proxies, imports, exports and raw admin API calls.

    43k GitHub starsUsed in 1 repo~717 tokens
    Backend & APIsAuto-check passed
  • Firecrawl Build Onboarding

    firecrawl/firecrawl

    Gets Firecrawl working in a project: signs you in through the browser, saves FIRECRAWL_API_KEY to .env and picks the first SDK or REST path.

    189k GitHub starsUsed in 1 repo~1.4k tokens
    Backend & APIsAuto-check: notes
  • Obsidian Bases

    Atmosphere/atmosphere

    Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries.

    3.8k GitHub starsUsed in 22 repos~3.2k tokens
    Backend & APIsAuto-check passed
  • Fortify Development

    coollabsio/coolify

    ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.

    63k GitHub starsUsed in 4 repos~1.9k tokens
    Backend & APIsAuto-check passed

More from z80dev/lemon

  • Debug and stress-test lemon gateway behavior by acting as both sides of Telegram conversations: run lemon-gateway with debug logs, then use Telethon with user credentials to send/reply messages in a…

    131 GitHub stars~744 tokensUpdated 21 days ago
    Auto-check: notes
  • Verify Lemon

    z80dev/lemon

    Verify lemon features against a running (or disposable) instance using the cheapest sufficient tier: DIRECT (attach/RPC + control-plane WS + bus observation, no Telegram), FAKE TELEGRAM (hermetic…

    131 GitHub stars~4k tokensUpdated 21 days ago
    Auto-check: notes
  • Pinata

    z80dev/lemon

    Pin files and JSON to IPFS via Pinata (JWT auth + helper scripts).

    131 GitHub stars~418 tokensUpdated 21 days ago
    Auto-check passed
  • Discord Client

    z80dev/lemon

    Interact with Discord via a bot: read channels, send messages, list guilds/channels, upload files, manage threads.

    131 GitHub stars~771 tokensUpdated 21 days ago
    Auto-check: notes
  • Runtime Remsh

    z80dev/lemon

    Connect to a running Lemon or lemon-gateway BEAM node, run recompile() for hot code reload, and execute Elixir code in that live runtime via IEx remsh or rpc-eval.

    131 GitHub stars~819 tokensUpdated 21 days ago
    Auto-check passed

Categories

Questions about Session Logs

What does Session Logs do?

Search and analyze your own Lemon session logs (older/parent conversations) using jq. Session Logs is an agent skill from z80dev/lemon. Search and analyze your own Lemon session logs (older/parent conversations) using jq.

When should I use Session Logs?

Session Logs fits situations like: backend & APIs work in your project.

How do I install Session Logs in Claude Code?

Run `npx skills add z80dev/lemon --skill session-logs -a claude-code`. Or copy the skill folder (apps/lemon_skills/priv/builtin_skills/session-logs in z80dev/lemon) into .claude/skills/session-logs in your project. Claude Code loads it when a task matches its description.

How do I install Session Logs in Codex?

Run `npx skills add z80dev/lemon --skill session-logs -a codex`. Or copy the skill folder (apps/lemon_skills/priv/builtin_skills/session-logs in z80dev/lemon) into .agents/skills/session-logs in your project. Codex loads it when a task matches its description.

Can I use Session Logs in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add z80dev/lemon --skill session-logs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/session-logs, .gemini/skills/session-logs, .github/skills/session-logs and .opencode/skills/session-logs in your project.

What does Session Logs need to run?

Going by SKILL.md and its folder, Session Logs needs the command-line tools its instructions call (jq and rg).

Does Session Logs access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Session Logs safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Session Logs use?

Session Logs is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Session Logs use?

About 949 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Session Logs?

Skills that share tags, products or a category with Session Logs: Configuring Horizon (coollabsio/coolify, 63k stars), Nestjs Best Practices (rolling-scopes/rsschool-app, 10k stars), Sub2API Admin (Wei-Shaw/sub2api, 43k stars) and Firecrawl Build Onboarding (firecrawl/firecrawl, 189k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Session Logs?

z80dev (a GitHub user) maintains it in z80dev/lemon, which has 131 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 16, 2026.

Source: z80dev/lemon on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.