CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

coding-agent-sessions

Finds, reads, and reconstructs coding-agent sessions across Codex, Claude, OpenCode, OMO/Senpi, and other local agent logs. Use when asked to find or search past sessions, transcripts, or subagent runs, or to recover what an earlier session did.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is coding-agent-sessions in code-yeongyu/oh-my-openagent

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary operational skill body: executable commands throughout, a clear phased workflow with an explicit verification step, and clean one-level-deep progressive disclosure verified against the actual bundle. The main improvement opportunity is removing the redundancy between the Activation section and PHASE 0 steps 2-3.

Suggestions

Trim the Activation section: it duplicates PHASE 0 steps 2-3 (multi-query expansion, --include-subagents, explorer-style lanes, narrowing by platform/cwd/model/time) — either collapse it into a one-line pointer to PHASE 0 or merge the unique memory-recall phrasings into step 2.

Move the OpenCode implementation paragraph in Filters (opencode db path, SQLite queries, CLI fallback, messages/parts scan avoidance) into references/opencode.md, keeping only the operational implication (e.g., 'OpenCode reads its DB first; pass --root only for nonstandard stores').

DimensionReasoningScore

Conciseness

The body is dense and operational — tables, ready-to-run commands, and terse notes like "prints JSON for stdout and `jq`" with no basic-concept explanations. It is not a 5 because the Activation section restates PHASE 0 steps 2-3 (query expansion, explorer-style lanes, --include-subagents) almost verbatim, and the OpenCode SQLite/DB paragraph is implementation detail that could be trimmed to a pointer.

4 / 5

Actionability

Guidance is fully executable: a copy-paste bash block covering list/find/read with real flag combinations, a router table mapping each platform to an exact reference path, `detail_hint` commands for the next step, and a troubleshooting table with exact flags and paths. This matches the 5 anchor (copy-paste ready, covers common cases); a 4 would have minor gaps in the concrete examples.

5 / 5

Workflow Clarity

PHASE 0 gives a clear 5-step sequence — route by platform, expand queries and run the finder, split parallel lanes, read `detail_hint` details, verify against raw transcripts — with an explicit validation step ("the raw `path` remains the source of truth") and a troubleshooting section as feedback loops. The operations are read-only, so the destructive/batch validation cap does not apply; it exceeds the 4 anchor because checkpoints are explicit rather than implied.

5 / 5

Progressive Disclosure

The body is a well-organized overview: a router table clearly signals one-level-deep references (references/codex.md, claude.md, senpi.md, opencode.md, all-platforms.md — all verified to exist, with no nested references inside them), the finder script is bundled, and platform storage detail is appropriately split into per-platform files. Navigation is unambiguous, matching the 5 anchor rather than the 4 anchor's 'minor organization gaps'.

5 / 5

Total

19

/

20

Passed

Description

92%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: it states concrete capabilities, enumerates the supported platforms, and gives an explicit 'Use when' clause with natural trigger phrases. The only gap is a few missing synonyms (e.g., 'history', 'conversation') that users might naturally say.

DimensionReasoningScore

Specificity

"Finds, reads, and reconstructs coding-agent sessions across Codex, Claude, OpenCode, OMO/Senpi, and other local agent logs" lists three concrete actions covering the full workflow plus an explicit platform enumeration. It matches the 5 anchor (multiple specific concrete actions, comprehensive for the domain) rather than 4, where coverage would show minor gaps.

5 / 5

Completeness

Both halves are explicit: the what ("Finds, reads, and reconstructs coding-agent sessions...") and a concrete when ("Use when asked to find or search past sessions, transcripts, or subagent runs, or to recover what an earlier session did"). This matches the 5 anchor exactly; a 4 would require the when-clause to be less specific.

5 / 5

Trigger Term Quality

Natural phrases are present — "find or search past sessions, transcripts, or subagent runs" and "recover what an earlier session did" — plus product names users would say. It falls short of the 5 anchor because common variations like "chat history", "conversation logs", or "what did I work on" are missing, but it exceeds the 3 anchor's 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

The niche — reconstructing local coding-agent session logs — is distinct and anchored by named platforms (Codex, Claude, OpenCode, OMO/Senpi), giving minimal overlap with other skills. It is not a 4 because no meaningful conflict risk with closely related skills is identifiable.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

code-yeongyu/lazycodex

Path

plugins/omo/skills/coding-agent-sessions/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.