session-logs

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

1.91x

Quality

59%

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 ./openclaw/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 own session logs with jq) but is too terse. It lacks explicit trigger guidance ('Use when...') and doesn't enumerate specific capabilities beyond generic 'search and analyze'. The distinctiveness is its strongest quality, but the missing trigger clause and limited specificity weaken its effectiveness for skill selection.

Suggestions

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

List more specific actions, e.g., 'Search, filter, and analyze session logs from older/parent conversations using jq — extract messages, filter by date or topic, summarize past interactions.'

Include more natural trigger terms users might say, such as 'past sessions', 'conversation history', 'previous chats', 'log analysis', or 'query logs'.

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', 'conversations', and 'jq', but misses natural user phrases like 'past sessions', 'conversation history', 'previous chats', 'log files', or 'query logs'.	2 / 3
Distinctiveness Conflict Risk	The combination of 'session logs', '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

79%

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, actionable skill with excellent concrete examples that Claude can immediately use. The queries are well-crafted and cover realistic use cases. Minor improvements could be made by adding a brief workflow for the common pattern of 'find session → inspect → extract' and potentially splitting advanced queries into a reference file.

Suggestions

Add a brief 2-3 step workflow at the top showing the typical pattern: 1) List sessions to find the right one, 2) Sample it with head/tail, 3) Run targeted queries — this would improve workflow clarity.

Consider moving less common queries (daily cost summary, tool usage breakdown, message counting) to a separate QUERIES.md reference file to keep the main skill focused on the most frequent operations.

Dimension	Reasoning	Score
Conciseness	Every section earns its place. No unnecessary explanations of what JSONL is, how jq works, or what session logs are conceptually. The content jumps straight to locations, structure, and executable queries.	3 / 3
Actionability	All queries are fully executable bash/jq commands that can be copy-pasted with minimal substitution (just agentId and session file). Covers a comprehensive range of real use cases from keyword search to cost summaries to tool usage breakdowns.	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 the typical workflow (e.g., first find the right session, then query it) and no validation steps for confirming results are correct or handling empty/malformed JSONL files.	2 / 3
Progressive Disclosure	The content is well-organized with clear headers and a logical progression from structure to queries to tips. However, at ~90 lines with many query examples, some of the less common queries (daily cost summary, tool usage breakdown) could be split into a separate reference file to keep the main skill leaner.	2 / 3
	Total	10 / 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: trpc-group/trpc-agent-go
Commit: af8bd5f

Reviewed: 5 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.