CtrlK
BlogDocsLog inGet started
Tessl Logo

session-logs

Search and analyze your own session logs (older/parent conversations) using jq.

Install with Tessl CLI

npx tessl i github:attilaczudor/Test --skill session-logs
What are skills?

71

1.91x

Does it follow best practices?

Evaluation94%

1.91x

Agent success when using this skill

Validation for skill structure

SKILL.md
Review
Evals

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 (analyzing Claude's own session logs with jq) but lacks the explicit trigger guidance needed for reliable skill selection. It would benefit from a 'Use when...' clause and more specific action verbs describing what operations can be performed on the logs.

Suggestions

Add a 'Use when...' clause with trigger terms like 'previous conversations', 'chat history', 'past sessions', 'find in logs', or 'search my history'

List specific concrete actions such as 'filter conversations by date', 'search for specific topics', 'extract message patterns', or 'count token usage'

Include natural language variations users might say: 'old chats', 'earlier conversations', 'conversation history', 'log analysis'

DimensionReasoningScore

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, but the 'what' is also weak, warranting a 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', 'older/parent conversations', 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 high-quality skill that provides lean, actionable guidance for searching session logs. The executable jq examples are comprehensive and well-organized. The only weakness is the lack of explicit multi-step workflows connecting related queries (e.g., finding a session then analyzing it).

DimensionReasoningScore

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 patterns needed for this task.

3 / 3

Actionability

All examples are fully executable bash commands with proper jq syntax. Copy-paste ready queries cover the most common use cases with no pseudocode or vague instructions.

3 / 3

Workflow Clarity

While individual queries are clear, there's no explicit workflow for common multi-step tasks like 'find a session then extract content.' The skill is more of a reference than a guided process, which is appropriate but lacks validation checkpoints for operations.

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 focused scope, 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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

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.