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 own session logs with jq) but lacks explicit trigger guidance ('Use when...') and could benefit from more specific action verbs and natural user keywords. The specificity of the domain prevents major conflicts but the description is too terse to reliably guide skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to search, review, or analyze past conversations, chat history, or session logs.'
Include more natural trigger terms users might say, such as 'chat history', 'previous conversations', 'past sessions', 'log analysis'.
List more concrete actions beyond 'search and analyze', e.g., 'filter logs by date, extract conversation metadata, query session fields, summarize past interactions'.
| 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 'chat history', 'previous sessions', 'past conversations', 'log files', or 'conversation history'. | 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, highly actionable skill that provides immediately executable jq/bash commands for searching session logs. Its main strengths are conciseness and actionability—every example is copy-paste ready and no tokens are wasted on explanations Claude doesn't need. The main weakness is the lack of a suggested workflow for the most common use case (finding and analyzing a specific past conversation), and the inline content is slightly heavy for a single file.
Suggestions
Add a brief 'Typical workflow' section at the top showing the recommended sequence: 1) identify the target session (via sessions.json or date search), 2) extract/search within it, to guide Claude through the most common use case.
Consider splitting the less common queries (daily cost summary, tool usage breakdown, message counting) into a separate 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 directly usable information—file locations, data structure, and executable 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, message extraction, tool usage) with no pseudocode or vague instructions. | 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 relevant session (via sessions.json or date search), then drill into it. A suggested sequence for the common 'find what was discussed' task would improve clarity. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear 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
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.