session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
71
Quality
60%
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
32%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 specific niche (session log analysis with jq) but lacks the explicit trigger guidance needed for Claude to reliably select it. The actions described are too high-level, and the description misses natural language variations users might employ when needing this functionality.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about previous conversations, chat history, past sessions, or wants to query/search their conversation logs'
Expand trigger terms to include natural variations: 'chat history', 'previous sessions', 'past conversations', 'conversation history', 'log queries'
List more specific actions: 'filter sessions by date, search for specific topics across conversations, extract patterns from chat history, aggregate session statistics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (session logs) and mentions two actions (search and analyze) plus a tool (jq), but doesn't list comprehensive concrete actions like 'filter by date', 'extract patterns', or 'aggregate statistics'. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps this at 2, and the weak 'what' pushes it to 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms ('session logs', 'jq', 'conversations') but misses common variations users might say like 'chat history', 'previous sessions', 'past conversations', 'log files', or 'query logs'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'session logs' and 'jq' provides some distinctiveness, but 'search and analyze' is generic enough that it could overlap with general log analysis or search skills. | 2 / 3 |
Total | 7 / 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 reference skill that efficiently documents session log querying with executable jq commands. It excels at conciseness and actionability, providing copy-paste ready queries without explaining concepts Claude already knows. The main gap is the lack of a guided workflow for common multi-step investigation patterns.
Suggestions
Add a brief workflow section showing how to chain queries (e.g., 'To find and analyze a past conversation: 1. Search for keyword across sessions, 2. Identify the relevant session ID, 3. Extract full context')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place with no unnecessary explanation of what JSONL is or how jq works. The skill assumes Claude's competence and provides only the specific paths, structures, and queries needed. | 3 / 3 |
Actionability | All examples are fully executable bash commands with proper jq syntax. The queries are copy-paste ready with clear placeholders (<agentId>, <session>.jsonl) that are easy to substitute. | 3 / 3 |
Workflow Clarity | While individual queries are clear, there's no explicit workflow for common multi-step tasks like 'find a conversation then extract context from it.' The skill is more of a reference than a guided process, which is appropriate but lacks validation steps for complex searches. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections (Trigger, Location, Structure, Common Queries, Tips). Content is appropriately contained in a single file given its scope as a reference skill, with logical grouping of related queries. | 3 / 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
50ef2f3
- 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.