extract-transcripts

Extract readable transcripts from Claude Code and Codex CLI session JSONL files

11.87x

Quality

67%

Does it follow best practices?

Impact

95%

11.87x

Average score across 3 eval scenarios

Securityby

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/extract-transcripts/SKILL.md

Quality

Discovery

54%

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 clear, distinctive niche with good natural trigger terms specific to Claude Code and Codex CLI workflows. However, it lacks a 'Use when...' clause and only describes a single action, limiting its completeness and specificity. Adding explicit trigger guidance and expanding the list of concrete capabilities would significantly improve it.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to read, review, or share a Claude Code or Codex CLI session, or when working with .jsonl session log files.'

List additional concrete actions beyond extraction, e.g., 'Extract readable transcripts, format conversation turns, summarize session activity from Claude Code and Codex CLI session JSONL files.'

Dimension	Reasoning	Score
Specificity	Names the domain (transcript extraction) and the specific input formats (JSONL files from Claude Code and Codex CLI), but only describes one action ('extract readable transcripts') rather than listing multiple concrete capabilities.	2 / 3
Completeness	Answers 'what' (extract readable transcripts from JSONL files) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'when' is only weakly implied, pushing it to 1.	1 / 3
Trigger Term Quality	Includes highly specific natural keywords users would say: 'transcripts', 'Claude Code', 'Codex CLI', 'session', 'JSONL'. These are precise terms a user would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Very clear niche targeting specifically Claude Code and Codex CLI session JSONL files. This is unlikely to conflict with other skills due to the highly specific tool names and file format mentioned.	3 / 3
	Total	9 / 12 Passed

Implementation

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 well-crafted reference skill that excels at conciseness and actionability — every command is concrete and copy-paste ready with clear option descriptions. The main weaknesses are minor: workflow sequencing between the index/search/show steps could be more explicit, and the content could benefit from slightly better progressive disclosure for the DuckDB section. Overall, it's a strong skill that efficiently communicates how to use the transcript extraction tools.

Suggestions

Consider adding a brief workflow example for the DuckDB indexer showing the typical sequence: index first, then search/list, then show a specific session.

The DuckDB section is substantial enough to warrant its own referenced file (e.g., INDEXER.md) with a brief summary in the main skill.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It assumes Claude knows what JSONL files, transcripts, and CLI tools are. Every section provides concrete commands without unnecessary explanation. No padding or concept definitions.	3 / 3
Actionability	Fully concrete and copy-paste ready. Every feature is demonstrated with exact CLI commands, specific file paths, and clear flag descriptions. No pseudocode or vague instructions.	3 / 3
Workflow Clarity	The skill presents commands clearly but lacks explicit workflow sequencing. For the DuckDB indexer, there's an implicit workflow (index → search/recent → show) but no explicit sequence or validation steps. The individual commands are clear but the overall process flow could be more explicit.	2 / 3
Progressive Disclosure	Content is well-organized with clear sections, but everything is inline in a single file. The options reference, output format details, and DuckDB indexer documentation could potentially be split into separate files. However, the content length is moderate enough that this is a minor issue.	2 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Commit: e437c3c

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.