CtrlK
BlogDocsLog inGet started
Tessl Logo

session-logs

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

79

1.91x
Quality

71%

Does it follow best practices?

Impact

94%

1.91x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/session-logs/SKILL.md

The canonical home for this skill is session-logs in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, highly actionable catalog of executable jq/rg queries with clear structure and no padding of concepts Claude already knows; its main weakness is mild intro/trigger redundancy and the lack of an explicit sequenced workflow.

Suggestions

Merge the intro paragraph and the 'Trigger' section to remove redundancy and tighten conciseness toward 5.

Add a short 'Workflow' note (find session via sessions.json → inspect structure → run the matching query) to give the query catalog an explicit sequence for workflow_clarity.

Consider splitting the longer 'Common Queries' catalog into a referenced file if the skill grows, to preserve progressive disclosure at scale.

DimensionReasoningScore

Conciseness

The body is lean and mostly code with necessary domain-specific field documentation, but the intro paragraph and the separate 'Trigger' section slightly overlap and could be trimmed.

4 / 5

Actionability

Each common query is copy-paste-ready bash/jq with real syntax, and the examples comprehensively cover listing, finding, extracting, searching, cost, counts, and tool-usage cases.

5 / 5

Workflow Clarity

Location → Structure → Queries → Tips gives a clear, well-organized path; all operations are read-only so the destructive/batch validation cap does not apply, but it is a query catalog rather than a sequenced workflow with checkpoints.

4 / 5

Progressive Disclosure

Clean section headers and a well-organized query catalog make navigation easy with no external references needed; at ~110 lines it exceeds the under-50-line simple-skill exception for a 5.

4 / 5

Total

17

/

20

Passed

Description

61%Weight 40%Scale 1-5

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 is specific and clearly niched, with good natural trigger terms, but it lacks an explicit 'Use when...' clause, which caps its completeness.

Suggestions

Append an explicit 'Use when...' clause (e.g., 'Use when the user asks about prior chats, parent conversations, or what was said before.') to lift completeness above 3.

Add a couple of natural synonyms ('conversation history', 'previous chats') to broaden trigger-term coverage toward 5.

Replace the generic 'analyze' with one or two concrete actions (e.g., 'extract messages', 'summarize costs') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain ('session logs') and two concrete actions ('Search and analyze'), but the actions are not comprehensive and 'analyze' is somewhat generic.

3 / 5

Completeness

The 'what' is clear, but there is no explicit 'Use when...' trigger clause; the parenthetical '(older/parent conversations)' only weakly implies when, capping completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

'session logs' and 'older/parent conversations' are natural phrases users would say, though common synonyms like 'history' or 'previous chats' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'session logs / older/parent conversations' niche is distinct with specific triggers, with only minor overlap risk against general search or memory skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 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

14

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.