CtrlK
BlogDocsLog inGet started
Tessl Logo

session-logs

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

64

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/session-logs/SKILL.md
SKILL.md
Quality
Evals
Security

Security

1 high severity finding. You should review these findings carefully before considering using this skill.

High

W007: Insecure credential handling detected in skill instructions.

What this means

The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.

Why it was flagged

This skill provides shell/jq commands that extract and print raw message text from session JSONL files (e.g., user/assistant content), which can cause the LLM to read and output secrets verbatim if they appear in the logs.

Report incorrect finding

Low

Low-risk findings.

1 low severity finding. Worth noting, but not necessarily harmful.

Low

W011: Third-party content exposure detected (indirect prompt injection risk).

What this means

The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.

Why it was flagged

At runtime the skill reads outsider-authored prior conversation transcripts from session JSONL files under `~/.bitterbot/agents/<agentId>/sessions/` and injects that text into the LLM context to answer historical-context queries (those logs include messages authored by other parties than the operating user).

Repository
Bitterbot-AI/bitterbot-desktop
Audited
Security analysis
Snyk

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.