读取、搜索和导出本地 Claude Code 历史记录，无需恢复工作。涵盖最近的会话清单、精确的会话时间线、逐字的人类输入（包括排队的中期提示）、完整事件的关键词搜索、措辞改变的混合回忆、最终状态分类以及跨活跃 Claude 主目录和已注册存档的已删除文件恢复。
此技能允许开发者在本地读取、搜索和导出 Claude Code 的历史会话记录，而无需实际恢复工作。它涵盖了多个方面：列出最近的会话清单、查看确切会话时间线、获取逐字的人类输入（包括在对话中间排队的提示）、基于完整事件进行关键词搜索、在措辞改变时进行混合回忆、分析最终状态以及恢复已删除的文件。该技能适用于多个平台，包括 Claude Code 和 Kimi CLI。总之，它为用户提供了一种强大的方式来回顾、审计和利用其本地 AI 聊天记录。对于 Codex 的历史记录，应使用 `read-codex-history`；当请求未指定平台或跨多个提供商时，应使用 `local-conversation-history`。
npx skills add https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/read-claude-code-history读取、搜索和导出本地 Claude Code 历史记录，无需恢复工作。涵盖最近的会话清单、精确的会话时间线、逐字的人类输入（包括排队的中期提示）、完整事件的关键词搜索、措辞改变的混合回忆、最终状态分类以及跨活跃 Claude 主目录和已注册存档的已删除文件恢复。每当用户询问他们或 Claude 说了什么、想要 Claude Code 会话 ID 或原始上下文、模糊地记得先前的工作、需要来自记录中的旧文件，或者在继续之前必须证明 Claude 会话包含什么内容时使用此技能。它还拥有唯一的 Kimi CLI 接口，通过其 Kimi 清单和搜索标志。对于 Codex 历史记录，请使用 read-codex-history；当请求未指定平台或跨多个提供商时，请从 local-conversation-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 OpenAI Codex history without continuing the old task. Lists recent Codex sessions, extracts exact prompt-ledger inputs by Session, locates a rollout by verified session_meta identity, reconstructs one chronological user/assistant timeline with fork and compaction lineage, and performs bounded keyword search across live and archived rollouts. Use whenever the user asks what they told Codex, wants recent original inputs, a Codex Session ID, full prior context, fork ancestry, or evidence of what a Codex run did. For Claude Code history use read-claude-code-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".