codex-search

Run Codex CLI web research and save findings as timestamped Markdown, JSON, and text files.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/shoei05/codex-search --skill codex-search-shoei05
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-search
Source: https://github.com/shoei05/codex-search/tree/main
Command: npx skills add https://github.com/shoei05/codex-search --skill codex-search-shoei05

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codex, python3, and includes scripts (resource) components.

What problem does it solve?

This Skill removes the overhead of running web searches repeatedly by automatically collecting research results and saving them in multiple reusable formats with timestamps.

Core Features & Use Cases

  • Web research via Codex CLI: Uses codex exec with a structured research prompt to produce Markdown-formatted findings.
  • Automatic multi-format saving: Saves each run into three files (.md, .json, .txt) under ~/.claude/data/codex-search/ with a UTC timestamp.
  • Citation-focused literature support: For academic/literature queries, prompts Codex to extract DOIs when possible and explicitly mark when DOI is not found.

Quick Start

Ask the skill to search for the topic and store the results by saying: use /codex-search "Latest updates on TypeScript 5.8".

Frequently Asked Questions about codex-search

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

FAQPage Schema
How do I automate web search and save results to Markdown files with timestamps?

You can automate web research by running Codex CLI with a structured prompt to generate Markdown findings, then automatically save the output as timestamped .md, .json, and .txt files to a configurable directory.

What's the best way to extract DOIs from academic literature searches?

For academic literature queries, the research prompt instructs Codex to extract DOIs when available and explicitly mark when a DOI is not found, storing these results in structured Markdown and JSON files.

Do I need Python and Codex installed to run automated web research workflows?

Yes, executing automated web research requires both the codex CLI and python3 installed in your environment to process queries and handle the script-based saving mechanism.

Can I test a web search query without saving files to the output directory?

Yes, you can use the dry-run mode to execute the research prompt through Codex CLI without writing the generated .md, .json, or .txt artifacts to the output directory.

How does saving multiple file formats like Markdown and JSON help with research workflows?

Saving each run into .md, .json, and .txt formats provides reusable structured data for engineering, product, and literature searches, allowing downstream parsing or direct reading of the timestamped findings.

Are there limitations when using Codex CLI for academic literature searches?

The primary limitation is that DOI extraction depends on Codex finding the identifier within the source, meaning it will explicitly mark when a DOI is not found rather than inferring it from partial data.