讀取、搜尋與匯出本機 Claude Code 對話歷史，無需恢復工作階段。涵蓋近期工作階段盤點、精確時間線、逐字人類輸入、關鍵字搜尋、混合回憶、終端狀態分類與已刪除檔案復原。
此技能提供開發者在不重新啟動 Claude Code 工作階段的情況下，完整存取、搜尋與匯出本機對話歷史記錄的能力。支援的功能包括列出最近工作階段、檢視每個工作階段的完整時間線、取得人類輸入的逐字內容（包含佇列中的中途提示）、基於全事件的關鍵字搜尋、當原始措辭改變時仍能進行混合回憶、工作階段終端狀態的任務分類，以及從對話記錄中復原被刪除的檔案。它可作用於多個活躍的 Claude 主目錄與已註冊的歷史檔案庫。此外，這是唯一提供 Kimi CLI 界面的技能，能透過 Kimi 盤點與搜尋旗標來操作。對於 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 或原始上下文、隱約記得先前工作、需要從對話記錄中取得舊檔案、或必須在繼續工作前證明該工作階段的內容時，皆可使用此技能。此外，這是唯一提供 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".