CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-history-ingest

Ingest Codex CLI conversation history into the Obsidian wiki. Use this skill when the user wants to mine their past Codex sessions for knowledge, import their ~/.codex folder, extract insights from previous coding sessions, or says things like "process my Codex history", "add my Codex conversations to the wiki", or "what have I discussed in Codex before". Also triggers when the user mentions .codex sessions, rollout files, session_index.jsonl, or Codex transcript logs.

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable procedural skill with a clear multi-step workflow and a real one-level reference file. The main weaknesses are mild redundancy (privacy guidance and data-layout both appear inline and in the reference) and only implicit feedback loops in the core parsing step.

Suggestions

Consolidate the privacy guidance into one section to remove the duplication between the Step 3 'Critical privacy filter' and the standalone 'Privacy and Compliance' block.

Trim the inline 'Codex Data Layout' tree/envelope detail and defer it to references/codex-data-format.md, keeping only what is needed to follow the workflow.

Add an explicit validate→fix→retry checkpoint after rollout parsing (e.g., verify extracted knowledge against the session index before writing wiki pages) to strengthen the batch-ingest feedback loop.

DimensionReasoningScore

Conciseness

The body is dense and operational with no basic-concept padding, but privacy guidance is duplicated across the 'Critical privacy filter' step and the 'Privacy and Compliance' section, and the inline data layout overlaps the reference file — minor trimming possible.

4 / 5

Actionability

Executable commands (qmd update/embed/ls/get), a concrete manifest JSON schema, and a rollout envelope structure give mostly copy-paste-ready guidance, though some clustering steps remain advisory by nature.

4 / 5

Workflow Clarity

A clear Step 1–6 sequence includes checkpoints (delta summary before parsing, New/Modified/Unchanged classification, status logging, QMD failure handling without rollback); explicit validate→fix→retry feedback loops for the core parse are only implicit.

4 / 5

Progressive Disclosure

Sections are well organized with a clearly signaled one-level reference (references/codex-data-format.md, confirmed present), but some inline data-layout detail duplicates content that lives in the reference, leaving minor organization gaps.

4 / 5

Total

16

/

20

Passed

Description

96%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, third-person description that clearly states both the skill's purpose and explicit natural-language triggers with good file-token coverage. Only slight overlap risk with sibling wiki-ingest skills keeps it from a perfect distinctiveness score.

DimensionReasoningScore

Specificity

Multiple concrete actions are named — 'Ingest Codex CLI conversation history into the Obsidian wiki', 'mine their past Codex sessions for knowledge', 'import their ~/.codex folder', 'extract insights' — giving comprehensive coverage rather than just a few actions.

5 / 5

Completeness

It explicitly answers both 'what' (ingest Codex history into the Obsidian wiki) and 'when' with concrete 'Use this skill when...' trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural user phrases ('process my Codex history', 'add my Codex conversations to the wiki', 'what have I discussed in Codex before') appear alongside file tokens like .codex, rollout files, session_index.jsonl, and transcript logs, covering synonyms and extensions.

5 / 5

Distinctiveness Conflict Risk

The Codex-specific niche and distinct triggers give minimal conflict risk, but the reference to a 'wiki-history-ingest' router implies sibling ingest skills for other sources, leaving minor overlap risk with closely related skills.

4 / 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Ar9av/obsidian-wiki
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.