session-logs
Search and analyze your own session logs (older/parent conversations) using jq.
69
56%
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
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 reasonably specific domain (self-referential session log analysis with jq) but lacks explicit trigger guidance ('Use when...') and concrete action details. It would benefit from listing specific capabilities and adding natural trigger terms users might use when needing this skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about previous conversations, past sessions, chat history, or wants to query session logs.'
List more specific concrete actions, e.g., 'Search session logs by keyword, filter conversations by date, extract message content, and aggregate statistics from past sessions using jq.'
Include more natural trigger term variations like 'previous chats', 'conversation history', 'past sessions', 'older messages', 'log analysis'.
| 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 messages, counting tokens, etc. | 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 only moderately detailed, placing this at 1-2. Given the missing 'when' clause entirely, scoring at 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'session logs', 'conversations', and 'jq', but misses natural user phrases like 'previous chats', 'conversation history', 'past sessions', 'log files', or 'query logs'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'session logs', 'parent conversations', and 'jq' is fairly specific, but 'search and analyze' is generic enough that it could overlap with general log analysis or jq-related skills. The niche is somewhat clear but not sharply defined. | 2 / 3 |
Total | 7 / 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 reference skill with excellent conciseness and executable examples. Its main weakness is the lack of a guided workflow for the common pattern of 'find the right session, then extract information from it,' and the content could benefit from slightly better progressive disclosure by separating advanced analytics queries from basic search patterns.
Suggestions
Add a brief 'Typical workflow' section at the top showing the sequence: 1) List sessions to find the right one, 2) Search/extract from that session, 3) Verify results make sense — this would improve workflow clarity.
Consider splitting advanced analytics queries (cost summaries, token counts, tool usage) into a separate ANALYTICS.md reference to keep the main skill focused on the most common search/lookup patterns.
| 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, which is appropriate for its purpose. However, there's no guidance on the typical workflow sequence (e.g., first find the right session, then search within it) and no validation steps for confirming results are correct or complete. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear headers and logical grouping, but everything is inline in a single file. The 'Common Queries' section is quite long and could benefit from splitting advanced queries (cost analysis, tool usage) into a separate reference file, with the main skill focusing on the most common lookup patterns. | 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
- attilaczudor/Test
- Commit
b3cef5f
- 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.