Content
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, actionable skill that provides concrete, 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. Minor weaknesses include the lack of a guided workflow for common investigation patterns and the slightly long inline query catalog that could benefit from progressive disclosure into a separate reference file.
Suggestions
Add a brief recommended workflow section (e.g., 'To investigate a prior conversation: 1. List sessions by date, 2. Identify candidate sessions, 3. Search within them') to improve workflow clarity.
Consider splitting the less common queries (daily cost summary, tool usage breakdown, count messages) into a separate QUERIES.md reference file to improve progressive disclosure.
| 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. No unnecessary padding. | 3 / 3 |
Actionability | Every query is a fully executable, copy-paste-ready bash/jq command. The examples cover a comprehensive range of use cases (searching, cost analysis, message extraction, tool usage breakdown) with concrete, specific commands rather than pseudocode or vague descriptions. | 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 a recommended workflow for common scenarios (e.g., 'first list sessions, then narrow by date, then search within'), and no validation or error-handling steps for when queries return unexpected results or sessions are missing. | 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. No bundle files exist to offload this content. | 2 / 3 |
Total | 10 / 12 Passed |