session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
75
66%
Does it follow best practices?
Impact
94%
1.91xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/session-logs/SKILL.mdQuality
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 be more specific about the concrete actions it supports. The trigger terms are adequate but miss common user phrasings for this task.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about past conversations, wants to search session history, review previous chats, or query log data.'
List more specific concrete actions, e.g., 'Search, filter, and analyze session logs (older/parent conversations) by date, keyword, or metadata using jq queries.'
Include additional natural trigger terms users might say, such as 'past sessions', 'conversation history', 'previous chats', 'log search', 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 'own 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
92%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, highly actionable skill that provides concrete, executable jq/bash commands for searching session logs. It's concise, assumes Claude's competence, and covers a wide range of practical use cases. The only minor weakness is that the extensive query catalog could be split into a separate reference file for better progressive disclosure.
| 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 location, structure, and executable queries. | 3 / 3 |
Actionability | All queries are fully executable bash commands with jq, rg, and standard Unix tools. They are copy-paste ready with only the agentId and session placeholders needing substitution. Covers a comprehensive range of use cases. | 3 / 3 |
Workflow Clarity | This is a reference/lookup skill rather than a multi-step destructive workflow, so explicit validation checkpoints aren't required. The queries are clearly organized by purpose, and the single-action nature of each query makes the workflow unambiguous. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections (Location, Structure, Common Queries, Tips), but it's moderately long (~90 lines of content) and could benefit from splitting the extensive query catalog into a separate reference file while keeping only the most common 2-3 queries inline. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%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
09cce3e
- Reviewed
Table of Contents
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.