session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
71
59%
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 ./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, or needs to query log files.'
List more specific concrete actions, e.g., 'Search, filter, and analyze session logs from older/parent conversations using jq — extract messages, filter by date or topic, summarize conversation metadata.'
Include additional natural trigger terms like '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 '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
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, highly actionable skill that provides concrete, executable jq/bash commands for searching session logs. Its main strength is the breadth of ready-to-use queries covering common use cases. The main weakness is the lack of a guiding workflow for how to approach a user's question about prior conversations (e.g., which session to look at first), and the inline content is slightly heavy for a single file.
Suggestions
Add a brief workflow section at the top showing the typical sequence: check sessions.json index → identify candidate sessions by date/size → search/extract → summarize findings for the user.
Consider splitting the less common queries (daily cost summary, tool usage breakdown, count messages) into a separate QUERIES_REFERENCE.md to keep the main skill focused on the most frequent operations.
| 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 novel, domain-specific information (file locations, data structure, ready-to-use queries). The tips section is brief and adds genuinely useful operational knowledge. | 3 / 3 |
Actionability | Every query is a fully executable bash/jq command that can be copy-pasted with only the agentId and session-id substituted. The examples cover a comprehensive range of real use cases (search, cost analysis, tool usage breakdown, cross-session search) with no pseudocode. | 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 for answering a user's question about prior conversations (e.g., first check sessions.json index → identify relevant session → extract messages → summarize). A light workflow would improve usability. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers and a logical progression from structure to queries to tips. However, with ~100 lines of query examples inline, some of the less common queries (daily cost summary, tool usage breakdown) could be split into a reference file. For a standalone skill with no bundle, the organization is reasonable but slightly heavy for a single file. | 2 / 3 |
Total | 10 / 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
- Hung-Reo/hungreo-openclaw
- Commit
d8d7f4b
- 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.