CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-search

Search captured agent Runs and raw local/remote Pi sessions, especially flagg sessions, using the joelclaw sessions bridge. Use when the user asks to search sessions, find prior flagg/Panda/pi/codex/claude context, recover conversation history, verify session indexing, or bypass stale rag_search_sessions/Typesense results.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/session-search/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 body is exceptionally lean and policy-like, with clear boundaries around authorization and evidence handling. Its weakness is executability: key operational details (which tool, which script, where the runbook lives) are referenced but never resolved, and the workflow is implied by paragraph order rather than explicitly sequenced with validation loops for the mutation path.

Suggestions

Resolve the vague pointers: name the actual tool that accepts 'evidenceDrilldownReceipt', and give a path or location for 'the current operator archive-maintenance runbook' and 'the existing repair script' so the guidance is executable without discovery work.

Make the workflow sequence explicit — a short ordered list (recall first -> obtain receipt -> metadata diagnosis -> bounded transcript access -> repair via runbook -> return receipt/conclusion) with the existing verification steps as explicit checkpoints.

Add an error-recovery loop for the mutation path: what to check before running a replay/repair, and what to do if validation of capture receipts or indexing health fails, since the skill itself flags these as mutations rather than read-only diagnostics.

DimensionReasoningScore

Conciseness

Roughly 250 words of dense, imperative instruction with zero padding and no explanation of concepts Claude already knows; every sentence directs behavior ('Keep private queries in MCP arguments', 'Preserve native evidence and other sessions' work'). Matches the lean-and-efficient top anchor; there is nothing to trim.

5 / 5

Actionability

Names specific artifacts ('evidenceDrilldownReceipt', 'agent-session-capture-backup') and concrete inspection items ('capture timestamps, file counts, outbox counts, indexing health, and admission receipts'), but key execution details are unresolved: no commands, paths, or tool names behind 'use the discovered tool schema that accepts it', 'the current operator archive-maintenance runbook', and 'the existing repair script'. Some concrete guidance but incomplete; not 4 because the guidance is not executable without external lookup, not 2 because specific artifacts and inspection lists are given.

3 / 5

Workflow Clarity

An implicit sequence exists (recall first, obtain receipt before transcript search, metadata diagnosis, repairs via runbook, bounded window, return receipt/conclusion) and some checkpoints are stated ('Verify runtime, session identity, and source dates'; 'Inspect the existing repair script and help before use'), but steps are never enumerated and the mutation path ('Replay and environment repair are mutations') has no error-recovery or feedback loop. Sequence present with implicit checkpoints matches 3; not 4 because there is no explicit step list with validation gates.

3 / 5

Progressive Disclosure

A single-file skill under 50 lines with all guidance appropriately inline and no bundle files to misplace. Minor gaps: only a single H1 with no section headers, and the runbook/repair-script references are vague pointers without paths. Good structure with minor organization gaps matches 4; not 5 because the external references are not clearly signaled or navigable, not 3 because nothing that belongs in a separate file is inlined.

4 / 5

Total

15

/

20

Passed

Description

83%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.

A strong description with an explicit 'Use when' clause, concrete trigger phrases, and a clearly staked-out niche. Keyword coverage is good but misses a few natural synonyms (transcripts, logs), and the generic 'search sessions / recover conversation history' phrasing carries minor conflict risk with related recall skills.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Search captured agent Runs and raw local/remote Pi sessions', 'verify session indexing', 'bypass stale rag_search_sessions/Typesense results') tied to a named tool (joelclaw sessions bridge). Not 5 because coverage has minor gaps (e.g., no mention of what results look like or repair capabilities); not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: 'what' ('Search captured agent Runs and raw local/remote Pi sessions... using the joelclaw sessions bridge') and 'when' ('Use when the user asks to search sessions, find prior... context, recover conversation history, verify session indexing, or bypass stale... results') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'search sessions', 'recover conversation history', 'find prior flagg/Panda/pi/codex/claude context', plus system-specific terms (Typesense, rag_search_sessions). Not 5 because common synonyms like 'transcripts', 'chat history', or 'logs' are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is highly distinct (joelclaw bridge, flagg, Pi, Typesense), but generic trigger phrases like 'search sessions' and 'recover conversation history' create minor overlap risk with general memory/recall skills. Not 5 for this overlap; not 3 because the specific system names anchor it firmly.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

joelhooks/joelclaw

Path

skills/session-search/SKILL.md

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.