session-logs

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

1.91x

Quality

63%

Does it follow best practices?

Impact

94%

1.91x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/session-logs/SKILL.md

Quality

Discovery

40%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies a clear and distinctive niche (searching session logs with jq) but lacks explicit trigger guidance ('Use when...') and could benefit from more specific action verbs and natural user keywords. The specificity of the domain prevents major conflict risk, but the missing 'when' clause and limited trigger terms reduce its effectiveness for skill selection.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about previous conversations, past sessions, conversation history, or wants to query/search through older chat logs.'

Include more natural trigger terms users might say, such as 'previous chats', 'conversation history', 'past sessions', 'log analysis', or 'find in old conversations'.

List more specific concrete actions, e.g., 'Search, filter, and analyze session logs from older/parent conversations using jq — including querying by date, extracting message content, and summarizing conversation patterns.'

Dimension	Reasoning	Score
Specificity	Names the domain (session logs / older conversations) and mentions two actions (search and analyze) plus the tool (jq), but doesn't list specific concrete actions like filtering by date, extracting metrics, or querying specific fields.	2 / 3
Completeness	Describes what it does (search and analyze session logs using jq) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also fairly thin, placing this at 1.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'session logs', 'older/parent conversations', and 'jq', but misses common user phrasings like 'previous chats', 'conversation history', 'past sessions', 'log files', or 'search history'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'own session logs', 'older/parent conversations', and 'jq' creates a very specific niche that is unlikely to conflict with other skills. This is a clearly distinct use case.	3 / 3
	Total	8 / 12 Passed

Implementation

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-crafted skill that provides immediately actionable jq/bash commands for searching session logs. It respects Claude's intelligence by jumping straight to file locations, data structure, and executable queries without unnecessary explanation. The only weakness is the lack of a guided workflow for common multi-step investigation scenarios and no error handling guidance.

Suggestions

Consider adding a brief recommended workflow for the most common scenario (e.g., 'To find what was discussed in a prior conversation: 1. List sessions by date, 2. Identify candidate sessions, 3. Search within them') to improve workflow clarity.

Add a note about error handling for edge cases like empty sessions, missing agent ID, or sessions with no cost data to make the queries more robust.

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It doesn't explain what jq is, what JSONL is, or how bash works. Every section provides directly usable information—file locations, data structure, and executable queries. No unnecessary padding.	3 / 3
Actionability	Every query is a fully executable, copy-paste-ready bash/jq command. The examples cover a comprehensive range of use cases (listing sessions, searching, cost analysis, tool usage) with concrete, working code rather than pseudocode or vague descriptions.	3 / 3
Workflow Clarity	The skill is primarily a reference of independent queries rather than a multi-step workflow, so sequencing is less critical. However, there's no guidance on a recommended workflow for common scenarios (e.g., 'first list sessions, then narrow by date, then search within') and no validation/error handling for cases like missing files or malformed JSONL.	2 / 3
Progressive Disclosure	For a skill of this scope (single-purpose, under 100 lines, no bundle), the content is well-organized with clear sections: trigger, location, structure, common queries, and tips. The sections flow logically from context to usage, and no external references are needed.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	9 / 11 Passed

Repository: Hung-Reo/hungreo-openclaw
Commit: a5bf5e0

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.