로컬 OpenAI Codex 기록을 읽고, 검색하고, 내보냅니다. 이전 작업을 계속하지 않고 최근 Codex 세션을 나열하고, 세션별 정확한 프롬프트 입력을 추출하며, 확인된 session_meta 신원을 기반으로 롤아웃을 찾고, 포크 및 압축 계보를 포함한 시간순 사용자/어시스턴트 타임라인을 재구성하며, 라이브 및 아카이브 롤아웃 전반에 걸쳐 키워드 검색을 수행합니다.
이 스킬은 로컬에 저장된 OpenAI Codex 세션 기록에 접근하여 분석할 수 있는 강력한 도구입니다. 개발자가 Codex에 이전에 무엇을 요청했는지, 어떤 입력을 사용했는지, 그리고 Codex가 어떻게 응답했는지에 대한 완전한 맥락을 얻고자 할 때 유용합니다. 주요 기능으로는 최근 Codex 세션 목록 조회, 특정 세션 ID를 통한 상세 프롬프트 입력 확인, 세션 메타데이터를 기반으로 한 롤아웃(rollout) 식별, 포크(fork) 및 압축(compaction) 이력을 포함한 전체 사용자-어시스턴트 대화 타임라인 재구성, 그리고 활성 및 보관된 롤아웃에 대한 키워드 검색이 포함됩니다. 이 스킬은 Claude Code의 기록을 다루는 'read-claude-code-history' 스킬과 구분되며, Codex 사용 이력을 분석해야 하는 모든 AI 에이전트 환경에서 활용될 수 있습니다.
npx skills add https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/read-codex-history로컬 OpenAI Codex 기록을 읽고, 검색하고, 내보내되 이전 작업을 계속하지 않습니다. 최근 Codex 세션을 나열하고, 세션별 정확한 프롬프트 원장 입력을 추출하며, 확인된 session_meta 신원을 기반으로 롤아웃을 찾고, 포크 및 압축 계보를 포함한 시간순 사용자/어시스턴트 타임라인을 재구성하며, 라이브 및 아카이브 롤아웃 전반에 걸쳐 제한된 키워드 검색을 수행합니다. 사용자가 Codex에 무엇을 말했는지, 최근 원래 입력을 원하는지, Codex 세션 ID, 전체 이전 컨텍스트, 포크 계보, 또는 Codex 실행이 무엇을 했는지에 대한 증거를 요청할 때 사용합니다. Claude Code 기록을 위해서는 read-claude-code-history를 사용하세요.
This repo contains 9 individual skills — each has its own dedicated page.
>- Generates Chinese/Japanese speech with StepFun's Contextual TTS — default stepaudio-2.5-tts, stepaudio-3-tts for whisper/inline-() prosody. Replaces step-tts-2's voice_label with natural-language instruction. Use for emotional/prosody-controlled synthesis, batch voice lines, migrating from step-tts-2, or cloned voices (2.5/step-tts-2, not v3). Triggers on 阶跃 TTS, 语音合成, 配音. Not for transcription (use stepfun-asr).
This skill should be used when comparing two videos to analyze compression results or quality differences. Generates interactive HTML reports with quality metrics (PSNR, SSIM) and frame-by-frame visual comparisons. Triggers when users mention "compare videos", "video quality", "compression analysis", "before/after compression", or request quality assessment of compressed videos.
Download YouTube videos and HLS streams (m3u8) from platforms like Mux, Vimeo, etc. using yt-dlp and ffmpeg. Use this skill when users request downloading videos, extracting audio, handling protected streams with authentication headers, or troubleshooting download issues like nsig extraction failures, 403 errors, or cookie extraction problems.
Entry point for local AI conversation history across providers. Routes a request to the one skill that owns it, by platform (Claude Code, OpenAI Codex, Kimi CLI) and action (read evidence vs continue interrupted work), and owns the one job none of them own alone: a single inventory spanning all three providers. Use when the provider is unknown or plural ("our history", "what have I been working on", "which chats did I have"), when the user wants Kimi CLI history at all, when it is unclear whether they need evidence or resumption, or when they ask for this skill by name. Vague recall that names no platform ("we discussed this once, when was it?") belongs here rather than to a single-provider reader, because a Claude-only answer to an unscoped question cannot support an absence claim. When the platform and the action are both already clear, load that executor skill directly instead — except Kimi CLI, which has no reader or continuation skill of its own and always routes through here.
Create professional slide decks from topics or documents. Generates structured content with data-driven charts, speaker notes, and complete PPTX files. Applies persuasive storytelling principles (Pyramid Principle, assertion-evidence). Supports multiple formats (Marp, PowerPoint). Use for presentations, pitches, slide decks, or keynotes.
Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) methodology. This skill should be used when users provide loose requirements, ambiguous feature descriptions, or need to enhance prompts for AI-generated code, products, or documents. Triggers include requests to "optimize my prompt", "improve this requirement", "make this more specific", or when raw requirements lack detail and structure.
This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports. Includes autonomous execution capability via master prompts and complete documentation templates for third-party QA team handoffs. Implements OWASP security testing and achieves 90% coverage targets.
Reads, searches, and exports local Claude Code history without resuming work. Covers recent session inventory, exact session timelines, verbatim human input including queued mid-turn prompts, full-event keyword search, hybrid recall when wording changed, end-state triage, and deleted-file recovery across active Claude homes plus registered archives. Use whenever the user asks what they or Claude said, wants a Claude Code session ID or original context, remembers prior work vaguely, needs an old file from a transcript, or must prove what a Claude session contained before continuing it. Also owns the only Kimi CLI surface, via its Kimi inventory and search flags. For Codex history use read-codex-history; when the request names no platform at all or spans providers, start at local-conversation-history.
Fetch Twitter/X post content including long-form Articles with full images and metadata. Use when Claude needs to retrieve tweet/article content, author info, engagement metrics, and embedded media. Supports individual posts and X Articles (long-form content). Automatically downloads all images to local attachments folder and generates complete Markdown with proper image references. Preferred over Jina for X Articles with images.
ElevenLabs text-to-speech with mac-style say UX.
Oracle CLI second-model review/debug/refactor/design with selected files, dry-run token checks, API or browser engine.
Capture and automate macOS UI with the Peekaboo CLI.
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Build a throwaway prototype to flesh out a design — a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".