CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-thread-reader

Locate and read a Codex thread by a codex thread link, thread id, or rollout path across all local CODEX_HOME directories (~/.codex, ~/.codex-gpt, ...). Use when the user pastes a codex:// link, asks to understand the 前因后果 of a Codex session, wants a timeline of what a long-running main thread did, or needs to search / export a past Codex conversation.

77

Quality

96%

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

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.

The body is a strong example of a script-backed skill: a copy-paste-ready Quick Start, a clearly sequenced 5-step reading workflow with confirmation and re-check feedback, real privacy guardrails, and a Troubleshooting section keyed to actual failure modes. The only weakness is mild over-density in the 'Where threads live' section, where the record-type taxonomy could be trimmed into the script's own documentation.

DimensionReasoningScore

Conciseness

The body is dense with genuinely non-obvious, machine-specific facts (CODEX_HOME layout, rollout path format, sqlite index, script commands) and avoids explaining anything Claude already knows. However, minor instances could be trimmed — e.g., the full rollout record-type taxonomy and details like "Real user prompts are `item_completed` → `UserMessage`" duplicate what the script already handles and would fit its own help text. This sits between the level-4 anchor ("minor instances of over-explanation that could be trimmed") and level-5 ("every token earns its place"), noticeably above the midpoint.

4 / 5

Actionability

The Quick Start is fully executable, copy-paste ready command lines covering every subcommand (locate, summary, turns, messages, search, tools, export) with realistic flag combinations, plus notes on uuid-prefix matching and expected performance ("a 420 MB rollout takes ~1–3 s"). The referenced script `{baseDir}/scripts/codex_thread.py` exists in the bundle, so the commands are real.

5 / 5

Workflow Clarity

The 5-step "Recommended reading workflow" is clearly sequenced with the specific command for each step, starts with a confirmation checkpoint ("locate + summary: confirm the right home/file"), and includes a feedback loop in Troubleshooting ("turn indices are recomputed on every call, so re-run `turns` before citing a number"). The operations are read-only with privacy guardrails, so the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is a single-script skill with well-organized sections (Use when, Where threads live, Quick start, Workflow, Privacy, Troubleshooting) and one clearly signaled, real bundle file (`{baseDir}/scripts/codex_thread.py`). No references are buried and nothing that clearly belongs in a separate file is inlined at harmful length, satisfying the simple-skill exception for a well-organized single-purpose skill.

5 / 5

Total

19

/

20

Passed

Description

100%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 exemplary: it states concrete capabilities in third-person imperative voice, names the exact input forms (link, thread id, rollout path) and scope (all CODEX_HOME directories), and provides an explicit 'Use when' clause with natural trigger phrases including colloquial Chinese terms a user would actually say. Conflict risk is minimal because the vocabulary is tightly Codex-specific.

DimensionReasoningScore

Specificity

Multiple concrete actions are listed — "Locate and read a Codex thread", "search / export a past Codex conversation" — with specific input forms ("codex thread link, thread id, or rollout path") and the concrete scope "across all local CODEX_HOME directories (~/.codex, ~/.codex-gpt, ...)". Coverage of the skill's capabilities is comprehensive, matching the level-5 anchor rather than the level-4 anchor's "minor gaps".

5 / 5

Completeness

It explicitly answers "what" (locate, read, search, export Codex threads across CODEX_HOME directories) and "when" via a concrete "Use when the user pastes a codex:// link, asks to understand 前因后果..., wants a timeline..., or needs to search / export" clause. Both halves are explicit with concrete trigger phrases, matching the level-5 anchor exactly.

5 / 5

Trigger Term Quality

Natural trigger terms cover the full variation space: "codex:// link", "thread id", "rollout path", "前因后果 of a Codex session", "timeline", "search", "export", "conversation". It includes both the link format users paste and colloquial synonyms, matching the comprehensive level-5 anchor including extensions/formats.

5 / 5

Distinctiveness Conflict Risk

The niche is highly specific (Codex threads identified by codex:// links, thread ids, and rollout paths under CODEX_HOME directories) with distinct triggers unlikely to fire for any other skill. No overlap risk with generic conversation- or file-reading skills given the Codex-specific vocabulary.

5 / 5

Total

20

/

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
huangruiteng/CS-Notes
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.