skills.rest
Ar9av
Ar9avCOMMUNITY
Explore all skills by this author →
Website𝕏@_ar9avGitHub

codex-history-ingest

Parse Codex CLI session logs and generate Obsidian wiki pages with redaction.

3.2k|320|Updated Apr 6, 2026
Search Tags:#codex#privacy#transcripts#data-redaction#knowledge-distillation#history-ingest#wiki-ingestion
One-click install
npx skills add https://github.com/Ar9av/obsidian-wiki --skill codex-history-ingest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-history-ingest
Source: https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/codex-history-ingest
Command: npx skills add https://github.com/Ar9av/obsidian-wiki --skill codex-history-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ingest Codex CLI conversation history into the Obsidian wiki to distill scattered transcripts into durable knowledge and actionable insights, while protecting sensitive data.

Core Features & Use Cases

  • Ingest Codex history from the local ~/.codex folder, building a canonical inventory from session_index.jsonl and session rollout logs.
  • Distill cross-session patterns into wiki pages with provenance and privacy safeguards.
  • Automatically route insights into project-, concept-, and knowledge-synthesis pages for long-term knowledge management.

Quick Start

Instruct your agent to ingest Codex history using the wiki-history-ingest router.

Frequently Asked Questions about codex-history-ingest

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import Codex CLI conversation history into an Obsidian wiki?▼

To import Codex CLI history into an Obsidian wiki, you parse session_index.jsonl and rollout logs from the local ~/.codex folder to generate wiki-ready pages with provenance and redacted sensitive data.

What's the best way to distill insights from past Codex sessions?▼

Distilling insights from past Codex sessions involves mining cross-session patterns from transcripts and routing them into project, concept, or knowledge-synthesis pages for long-term management.

Does ingesting Codex history logs protect sensitive data in my transcripts?▼

Yes, ingesting Codex history logs protects sensitive data by applying data-redaction safeguards during the parsing of session rollout logs, ensuring privacy before producing wiki-ready pages.

Can I convert scattered Codex transcripts into durable knowledge automatically?▼

You can convert scattered Codex transcripts into durable knowledge by instructing your agent to ingest the history, which builds a canonical inventory and distills actionable insights into structured wiki pages.

What files do I need to parse to build a canonical inventory of Codex sessions?▼

To build a canonical inventory of Codex sessions, you need to parse the session_index.jsonl file alongside the session rollout jsonl logs stored in your local Codex history folder.

Are there limitations when routing distilled Codex insights into project pages?▼

Routing distilled Codex insights into project pages depends on the structure of your Obsidian wiki; the ingestion process automatically categorizes insights into project, concept, and knowledge-synthesis pages while maintaining provenance.

Related Skills

Explore More Software Engineering Skills→
ChrisWilesChrisWiles

codex-history-ingest

Ingest Codex CLI session logs into an Obsidian wiki with delta computation.

Community
Advanced
NirajkashyapNirajkashyap

llm-wiki

Maintain a persistent Obsidian wiki with frontmatter metadata and cross-linking.

Community
Advanced
zjykzkzjykzk

openclaw-history-ingest

Ingest OpenClaw agent history into Obsidian wiki pages with provenance metadata.

Community
Advanced
broomvabroomva
3

braindump

Organize unstructured text and transcripts into Obsidian-compatible knowledge structures.

Community
Intermediate