← 开源
daymade

claude-code-skills

Professional Claude Code skills marketplace featuring production-ready skills for enhanced development workflows.

AI EngineeringGive agent toolsBuild agent workflow (SDK)Python
在 GitHub 打开
增长势头
+124 小时新增 Star+0.1%
1.44k
Star
222
Fork
+10
本周
11
贡献者
创建于 2025-10-22 · 更新于 2026-10-05 · 今日第 4211 名
主要开发者
README

Claude Code Skills Marketplace

English 简体中文

License: MIT Claude Code PRs Welcome Maintenance

Professional Claude Code skills marketplace featuring production-ready skills for enhanced development workflows.

📑 Table of Contents


🌟 Essential Skill: skill-creator

⭐ Start here if you want to create your own skills!

The skill-creator is the meta-skill that enables you to build, validate, and package your own Claude Code skills. It's the most important tool in this marketplace because it empowers you to extend Claude Code with your own specialized workflows.

Why This skill-creator?

This is a production-hardened fork of Anthropic's official skill-creator, born from building real skills and hitting every wall the official version doesn't warn you about.

The official skill-creator tells you what to build. Ours also tells you what not to try — and why.

You're trying to... Official This Fork
Research before building "Check available MCPs" Ordered search protocol with decision matrix: Adopt / Extend / Build
Create a skill interactively Prose-based instructions Structured AskUserQuestion checkpoints — user never loses context
Avoid common mistakes No guidance Cache edit warnings, prerequisite checks, security scan gate
Know the architecture options Not mentioned Inline vs Fork decision guide with examples (choosing wrong silently breaks your skill)
Validate before shipping Basic YAML check Expanded structural validator plus provenance-checked old-vs-new capability audit; packaging re-verifies the completed review instead of trusting a marker
Match validation cost to risk One full create-test-review loop Risk tier and evaluation spend are separate: targeted checks first; paired benchmarks require explicit authorization or a decision-bearing evidence plan plus opt-in
Catch security issues No tooling security_scan.py with gitleaks integration — hard gate before packaging
Learn from real failures No failure cases Battle-tested methodology with documented failure patterns and gotchas
Distill past conversations safely Not covered Explicit local manifest, message-level time window, redaction, opaque source IDs, ignored .enrich/ staging, and manual promotion into references/scripts
Turn approved artifacts into skill behavior Not covered Artifact-corpus distillation workflow: script-measured pattern extraction (≥3-artifact threshold), cataloging≠distillation gate, invariant-vs-register boundary, independent completeness audit
Survive concurrent sessions on one skill repo Not covered git-ref baselines, re-read-before-write, HEAD check before commit, own-paths-only staging, one-bump-per-outcome versioning
Ground knowledge skills in evidence General advice Authority ladder from real calls and machine-readable specs through production code, plus executable-example smoke checks and evidence-boundary rules
Have both installed at once Coin flip — the two descriptions are near-identical Detects the clash on trigger and offers a one-command, reversible SessionStart routing hook (only ever installed when both coexist); the official plugin stays usable by explicit request
Your own skill collides with an installed plugin Not covered generate_supersede_kit.py stamps the same conditional routing kit into your skill, plus a measured precedence decision guide (rename → description tiebreaker → hook → disable)

Full methodology: skill-creator/references/skill-development-methodology.md

Quick Install

In Claude Code (in-app):

/plugin marketplace add daymade/claude-code-skills

Then:

  1. Select Browse and install plugins
  2. Select daymade/claude-code-skills
  3. Select skill-creator
  4. Select Install now

From your terminal (CLI):

claude plugin marketplace add https://github.com/daymade/claude-code-skills
# Marketplace name: daymade-skills (from marketplace.json)
claude plugin install daymade-skill@daymade-skills

What You Can Do

After installing skill-creator, simply ask Claude Code:

"Create a new skill called my-awesome-skill in ~/my-skills"

"Validate my skill at ~/my-skills/my-awesome-skill"

"Package my skill at ~/my-skills/my-awesome-skill for distribution"

Claude Code, with skill-creator loaded, will guide you through the entire skill creation process - from understanding your requirements to packaging the final skill.

📚 Full documentation: daymade-skill/skill-creator/SKILL.md

Live Demos

📝 Initialize New Skill

Initialize Skill Demo

✅ Validate Skill Structure

Validate Skill Demo

📦 Package Skill for Distribution

Package Skill Demo


🚀 Quick Installation

Install Inside Claude Code (In-App)

/plugin marketplace add daymade/claude-code-skills

Then:

  1. Select Browse and install plugins
  2. Select daymade/claude-code-skills
  3. Select the plugin you want
  4. Select Install now

Automated Installation (Recommended)

macOS/Linux:

curl -fsSL https://raw.githubusercontent.com/daymade/claude-code-skills/main/scripts/install.sh | bash

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/daymade/claude-code-skills/main/scripts/install.ps1 | iex

Manual Installation

Add the marketplace:

claude plugin marketplace add https://github.com/daymade/claude-code-skills

Marketplace name is daymade-skills (from marketplace.json). Use @daymade-skills when installing plugins. Do not use the repo path as a marketplace name (e.g. @daymade/claude-code-skills will fail). In Claude Code, use /plugin ... slash commands. In your terminal, use claude plugin ....

Essential Skill (recommended first install):

# skill-creator ships inside the daymade-skill suite
claude plugin install daymade-skill@daymade-skills

Documentation Suite (shared namespace for document workflows):

claude plugin install daymade-docs@daymade-skills

This suite exposes related skills under one namespace, including:

/daymade-docs:docs-router
/daymade-docs:doc-to-markdown
/daymade-docs:mermaid-tools
/daymade-docs:pdf-creator
/daymade-docs:ppt-creator
/daymade-docs:docs-cleaner
/daymade-docs:excel-automation
/daymade-docs:read-docx-review

These skills ship as a bundle — there are no separate single-skill plugins. All documentation skills live under daymade-docs/ and install together from the suite. The router handles automatic selection. The specialist commands remain available for manual use; ppt-creator is manual-only. New presentation creation uses deck-creator when installed.

Apple Platform Suite (shared namespace for macOS and iOS development/operations):

claude plugin install daymade-macos@daymade-skills
/daymade-macos:capture-screen
/daymade-macos:developing-ios-apps
/daymade-macos:macos-cleaner
/daymade-macos:macos-permissions
/daymade-macos:macos-watchdog

These skills are bundle-only under daymade-macos.

Codex Suite (shared namespace for Codex workstation setup, assisted coding, and visual exploration):

claude plugin install daymade-codex@daymade-skills

Codex CLI and Desktop users can install the same suite through Codex's plugin marketplace:

codex plugin marketplace add daymade/claude-code-skills
codex plugin add daymade-codex@daymade-skills
/daymade-codex:codex-image-gallery
/daymade-codex:local-codex
/daymade-codex:design-style-picker
/daymade-codex:interaction-design-board
/daymade-codex:codex-1m-context-window-setup

These skills are bundle-only under daymade-codex.

Claude Code Operations Suite (shared namespace for Claude Code power-user workflows):

claude plugin install daymade-claude-code@daymade-skills

This suite bundles the skills that extend Claude Code itself — cross-project prior-work retrieval across code, docs, Skills, meetings, WeChat archives, and conversation history; fast local conversation discovery across Claude Code and Codex; session recovery; CLAUDE.md tuning; version-synced Lark CLI routing; troubleshooting; statusline configuration; export repair; marketplace development and suite consolidation; terminal screenshot rendering; usage analysis; and multi-provider model switching:

/daymade-claude-code:claude-code-ops-router
/daymade-claude-code:local-conversation-history
/daymade-claude-code:read-claude-code-history
/daymade-claude-code:read-codex-history
/daymade-claude-code:continue-claude-code-work
/daymade-claude-code:continue-codex-work
/daymade-claude-code:claude-skills-troubleshooting
/daymade-claude-code:claude-md-progressive-disclosurer
/daymade-claude-code:statusline-generator
/daymade-claude-code:fixing-claude-export-conversations
/daymade-claude-code:marketplace-dev
/daymade-claude-code:terminal-screenshot
/daymade-claude-code:claude-usage-analyst
/daymade-claude-code:claude-switch-models-setup
/daymade-claude-code:read-claude-web-conversation
/daymade-claude-code:claude-migrate-memory-to-doc
/daymade-claude-code:claude-code-hooks
/daymade-claude-code:prior-work-retrieval
/daymade-claude-code:lark-cli-router
/daymade-claude-code:claude-code-ping-start-5h-quota
/daymade-claude-code:agent-web-search-setup
/daymade-claude-code:tech-selection

Installed names render as daymade-claude-code: under a single shared namespace. These skills are bundle-only — install the suite to get all members.

Financial Data Suite (shared namespace for investment-research and financial data workflows):

claude plugin install daymade-financial@daymade-skills

This suite bundles the skills that fetch and analyze financial data — Bigdata.com (RavenPack) structured financials and sentiment, US equity fundamentals via yfinance, Gangtise (岗底斯) OpenAPI research suite orchestration, A-share news and policy aggregation, A-share pharmaceutical sector daily reporting, structured devil's-advocate pressure-testing of investment theses, and adversarial due diligence on inflated benchmark claims:

/daymade-financial:financial-router
/daymade-financial:bigdata-skill
/daymade-financial:financial-data-collector
/daymade-financial:gangtise-copilot
/daymade-financial:ashare-news-fetcher
/daymade-financial:daymade-sector-research
/daymade-financial:pharma-daily-report
/daymade-financial:devils-advocate
/daymade-financial:benchmark-due-diligence

Installed names render as daymade-financial: under a single shared namespace. These skills are bundle-only — install the suite to get all members.

Install Other Skills:

# GitHub operations
claude plugin install github-ops@daymade-skills

# Teams communication
claude plugin install teams-channel-post-writer@daymade-skills

# Local Claude/Codex agent messaging
claude plugin install peer-message@daymade-skills

# Ghostty terminal session snapshot/restore
claude plugin install ghostty-use@daymade-skills

# Repomix extraction
claude plugin install repomix-unmixer@daymade-skills

# AI/LLM icons
claude plugin install llm-icon-finder@daymade-skills

# CLI demo generation
claude plugin install cli-demo-generator@daymade-skills

# Cloudflare diagnostics
claude plugin install cloudflare-troubleshooting@daymade-skills

# UI design system extraction
claude plugin install ui-designer@daymade-skills

# YouTube video/audio downloading
claude plugin install youtube-downloader@daymade-skills

# Secure repomix packaging
claude plugin install repomix-safe-mixer@daymade-skills

# Full audio suite (ASR + transcript correction + meeting minutes + TTS)
claude plugin install daymade-audio@daymade-skills


# Video comparison and quality analysis
claude plugin install video-comparer@daymade-skills

# QA testing infrastructure with autonomous execution
claude plugin install qa-expert@daymade-skills

# Prompt optimization using EARS methodology
claude plugin install prompt-optimizer@daymade-skills

# CCPM skill registry search and management
claude plugin install daymade-skill@daymade-skills

# Promptfoo LLM evaluation framework
claude plugin install promptfoo-evaluation@daymade-skills

# Twitter/X content fetching
claude plugin install twitter-reader@daymade-skills

# Skill quality review and improvement
claude plugin install daymade-skill@daymade-skills

# GitHub contribution strategy
claude plugin install github-contributor@daymade-skills

# Windows Remote Desktop / AVD connection diagnosis
claude plugin install windows-remote-desktop-connection-doctor@daymade-skills

# Product analysis and optimization
claude plugin install product-analysis@daymade-skills

# Scrapling CLI extraction and troubleshooting
claude plugin install scrapling-skill@daymade-skills

# Tencent IMA knowledge base companion and installer
claude plugin install ima-copilot@daymade-skills

# Export Douban (豆瓣) book/movie/music/game collections to CSV
claude plugin install douban-skill@daymade-skills

# Terraform operational traps and multi-environment reliability patterns
claude plugin install terraform-skill@daymade-skills

# Evaluate any LLM endpoint across speed, concurrency, protocol, and quality
claude plugin install llm-eval-harness@daymade-skills

# Video/GIF memes with motion-tracked image overlays
claude plugin install meme-creator@daymade-skills

Standalone plugins can be installed independently; suite members install together with their suite.


🇨🇳 Chinese User Guide

For Chinese users: We highly recommend using CC-Switch to manage Claude Code API provider configurations.

CC-Switch enables you to:

  • ✅ Quickly switch between different API providers (DeepSeek, Qwen, GLM, etc.)
  • ✅ Test endpoint response times to find the fastest provider
  • ✅ Manage MCP server configurations
  • ✅ Auto-backup and import/export settings
  • ✅ Cross-platform support (Windows, macOS, Linux)

Setup: Download from Releases, install, add your API configs, and switch via UI or system tray.

Complete Chinese Documentation

For full documentation in Chinese, see README.zh-CN.md.


📦 Other Available Skills

github-ops - GitHub Operations Suite

GitHub operations through gh CLI and GitHub APIs, with explicit targets, impact previews, and independent state verification.

When to use:

  • Creating, viewing, or managing pull requests
  • Managing issues and repository settings
  • Managing collaborators, teams, organization permissions, and 2FA enforcement
  • Querying GitHub API endpoints
  • Working with GitHub Actions workflows
  • Automating GitHub operations

Key features:

  • Verified mutation workflow for PRs, issues, repositories, and Actions
  • Parallel and superseded PR convergence
  • Organization access, member privileges, and 2FA preflight
  • REST, GraphQL, and documented UI-path selection
  • Enterprise GitHub support

🎬 Live Demo

GitHub Ops Demo


docs-router - Daymade Document Routing

Install: claude plugin install daymade-docs@daymade-skills (suite-only — invoked as daymade-docs:docs-router)

Selects the bundled specialist for document conversion, Word and PDF production, Mermaid images, macOS Excel automation, scanned PDFs, DOCX review extraction, or documentation cleanup. It reads the selected specialist's full instructions and required references. Specialist slash commands remain available for manual use. New presentation creation uses deck-creator when installed; ppt-creator is manual-only.


doc-to-markdown - Document Conversion Suite

Install: claude plugin install daymade-docs@daymade-skills (suite-only — invoked as daymade-docs:doc-to-markdown)

Converts documents to markdown with Windows/WSL path handling and PDF image extraction.

When to use:

  • Converting .doc/.docx/PDF/PPTX to markdown
  • Converting saved HTML/HTM with source-link checks and explicit heading offsets
  • Extracting images from PDF files
  • Processing Confluence exports
  • Handling Windows/WSL path conversions

Key features:

  • Multi-format document conversion
  • PDF image extraction using PyMuPDF
  • Windows/WSL path automation
  • Confluence export processing
  • Helper scripts for path conversion and image extraction

🎬 Live Demo

Markdown Tools Demo


mermaid-tools - Diagram Generation

Install: claude plugin install daymade-docs@daymade-skills (suite-only — invoked as daymade-docs:mermaid-tools)

Extracts Mermaid diagrams from markdown and generates high-quality PNG images.

When to use:

  • Converting Mermaid diagrams to PNG
  • Extracting diagrams from markdown files
  • Processing documentation with embedded diagrams
  • Creating presentation-ready visuals

Key features:

  • Automatic diagram extraction
  • High-resolution PNG generation
  • Smart sizing based on diagram type
  • Customizable dimensions and scaling
  • WSL2 Chrome/Puppeteer support

🎬 Live Demo

Mermaid Tools Demo


claude-code-ops-router - Claude Code Setup Router

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:claude-code-ops-router)

Routes plugin and Skill repair, marketplace work, statusline, model profiles and source sync, 1M context-window repair, usage and quota timers, memory migration, and exported .txt repair to one bundled specialist. The selected Skill's full instructions are read at use time; its original slash command remains available for manual use.


statusline-generator - Statusline Customization

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:statusline-generator)

Configures Claude Code statuslines with multi-line layouts and cost tracking.

When to use:

  • Customizing Claude Code statusline
  • Adding cost tracking (session/daily)
  • Displaying git status
  • Multi-line layouts for narrow screens
  • Color customization

Key features:

  • Multi-line statusline layouts
  • ccusage cost integration
  • Git branch status indicators
  • Customizable colors
  • Portrait screen optimization

🎬 Live Demo

Statusline Generator Demo


teams-channel-post-writer - Teams Communication

Creates educational Teams channel posts for internal knowledge sharing.

When to use:

  • Writing Teams posts about features
  • Sharing Claude Code best practices
  • Documenting lessons learned
  • Creating internal announcements
  • Teaching effective prompting patterns

Key features:

  • Post templates with proven structure
  • Writing guidelines for quality content
  • "Normal vs Better" example patterns
  • Emphasis on underlying principles
  • Ready-to-use markdown templates

🎬 Live Demo

Teams Channel Post Writer Demo


peer-message - Local Claude/Codex Agent Communication

An experimental paired-network route adds invitations and cited answers from owner-selected documents through existing Claude/Codex hosts. It requires an operator-provided relay; the public hosted network and user-adoption claims are not part of this preview.

Install: claude plugin install peer-message@daymade-skills

Bridge local Claude Code and Codex sessions when the current host's native tools do not cover the target. Use native discovery, messaging, replies, and waiting directly whenever available; load this skill for transport gaps or coordination evidence that needs verification.

When to use:

  • Sending a dependency, pause, handoff, or completion notice to an independently identified target outside the current native tools' scope
  • Finding replies to a specific coordination message without manually inspecting local message stores
  • Reaching a Claude inbox from a script or another product when native tools do not cover it; a third-party provider alone is not a reason to use the fallback
  • Unblocking messages held for per-message manual approval on an unattended endpoint (crossSessionInbound)
  • An inbound peer message asserting facts about your session or shared state, or asking you to pause/release — verify the premise against its own authority before acting
  • Another session's uncommitted edits, lock, or branch is in your way on a shared checkout — verify it is live, then ask the owner before waiting or working around it
  • Broadcasting one explicit coordination message to a reviewed target list

📚 Documentation and commands: peer-message/SKILL.md owns routing, stable runtime prerequisites, and the peer-cannot-authorize boundary; peer-message/scripts/peer.py --help owns CLI syntax; protocol-and-discovery.md owns addressing, envelopes, and delivery evidence; official-feature.md owns volatile product-specific requirements and mechanics; coordination-and-learning-loop.md owns reply addressing, payload and delivery-status language, what to do when you find another session's in-flight work on a shared resource, what an inbound peer assertion and a set of peer denials are each worth, and the evidence-gated improvement loop.


repomix-unmixer - Repository Extraction

Extracts files from repomix-packed repositories and restores directory structures.

When to use:

  • Unmixing repomix output files
  • Extracting packed repositories
  • Restoring file structures
  • Reviewing repomix content
  • Converting repomix to usable files

Key features:

  • Multi-format support (XML, Markdown, JSON)
  • Auto-format detection
  • Directory structure preservation
  • UTF-8 encoding support
  • Comprehensive validation workflows

🎬 Live Demo

Repomix Unmixer Demo


llm-icon-finder - AI/LLM Brand Icon Finder

Access 100+ AI model and LLM provider brand icons from lobe-icons library.

When to use:

  • Finding brand icons for AI models/providers
  • Downloading logos for Claude, GPT, Gemini, etc.
  • Getting icons in multiple formats (SVG/PNG/WEBP)
  • Building AI tool documentation
  • Creating presentations about LLMs

Key features:

  • 100+ AI/LLM model icons
  • Multiple format support (SVG, PNG, WEBP)
  • URL generation for direct access
  • Local download capabilities
  • Searchable icon catalog

🎬 Live Demo

LLM Icon Finder Demo


cli-demo-generator - CLI Demo Generation

Generate professional animated CLI demos and terminal recordings with VHS automation.

When to use:

  • Creating demos for documentation
  • Recording terminal workflows as GIFs
  • Generating animated tutorials
  • Batch-generating multiple demos
  • Showcasing CLI tools

Key features:

  • Automated demo generation from command lists
  • Batch processing with YAML/JSON configs
  • Interactive recording with asciinema
  • Smart timing based on command complexity
  • Multiple output formats (GIF, MP4, WebM)
  • VHS tape file templates

🎬 Live Demo

CLI Demo Generator Demo


cloudflare-troubleshooting - Cloudflare Diagnostics

Investigate and resolve Cloudflare configuration issues using API-driven evidence gathering.

When to use:

  • Site shows ERR_TOO_MANY_REDIRECTS
  • SSL/TLS configuration errors
  • DNS resolution problems
  • Email Routing aliases, destination verification and forwarding delivery
  • Cloudflare-related issues

Key features:

  • Evidence-based investigation methodology
  • Comprehensive Cloudflare API reference
  • SSL/TLS mode troubleshooting (Flexible, Full, Strict)
  • DNS, cache, and firewall diagnostics
  • Agentic approach with optional helper scripts

🎬 Live Demo

Cloudflare Troubleshooting Demo


ui-designer - UI Design System Extractor

Extract design systems from reference UI images and generate implementation-ready design prompts.

When to use:

  • Have UI screenshots/mockups to analyze
  • Need to extract color palettes, typography, spacing
  • Building MVP UI matching reference aesthetics
  • Creating consistent design systems
  • Generating multiple UI variations

Key features:

  • Systematic design system extraction from images
  • Color palette, typography, component analysis
  • Interactive MVP PRD generation
  • Template-driven workflow (design system → PRD → implementation prompt)
  • Multi-variation UI generation (3 mobile, 2 web)
  • React + Tailwind CSS + Lucide icons

🎬 Live Demo

UI Designer Demo


ppt-creator - Professional Presentation Creation

Install: claude plugin install daymade-docs@daymade-skills (suite-only — invoked as daymade-docs:ppt-creator)

Create persuasive, audience-ready slide decks from topics or documents with data-driven charts and dual-format PPTX output.

When to use:

  • Creating presentations, pitch decks, or keynotes
  • Need structured content with professional storytelling
  • Require data visualization and charts
  • Want complete PPTX files with speaker notes
  • Building business reviews or product pitches

Key features:

  • Pyramid Principle structure (conclusion → reasons → evidence)
  • Assertion-evidence slide framework
  • Automatic data synthesis and chart generation (matplotlib)
  • Dual-path PPTX creation (Marp CLI + document-skills:pptx)
  • Complete orchestration: content → data → charts → PPTX with charts
  • 45-60 second speaker notes per slide
  • Quality scoring with auto-refinement (target: 75/100)

🎬 Live Demo

PPT Creator Demo


youtube-downloader - YouTube Video & Audio Downloader

Download YouTube videos and audio using yt-dlp with robust error handling and automatic workarounds for common issues.

When to use:

  • Downloading YouTube videos or playlists
  • Extracting audio from YouTube videos as MP3
  • Experiencing yt-dlp download failures or nsig extraction errors
  • Need help with format selection or quality options
  • Working with YouTube content in regions with access restrictions

Key features:

  • Auto PO Token provider (Docker-first, browser fallback) for high-quality access
  • Browser-cookie verification for “not a bot” prompts (privacy-friendly)
  • Audio-only download with MP3 conversion
  • Format listing and custom format selection
  • Output directory customization
  • Proxy-aware downloads for restricted environments

🎬 Live Demo

YouTube Downloader Demo


repomix-safe-mixer - Secure Repomix Packaging

Safely package codebases with repomix by automatically detecting and removing hardcoded credentials before packing.

When to use:

  • Packaging code with repomix for distribution or sharing
  • Creating reference packages from proprietary codebases
  • Security concerns about accidentally exposing credentials
  • Pre-commit security checks for hardcoded secrets
  • Auditing codebases for credential exposure

Key features:

  • Detects 20+ credential patterns (AWS, Supabase, Stripe, OpenAI, etc.)
  • Scan → Report → Pack workflow with automatic blocking
  • Standalone security scanner for pre-commit hooks
  • Environment variable replacement guidance
  • JSON output for CI/CD integration
  • Exclude patterns for false positive handling

🎬 Live Demo

Coming soon


transcript-fixer - ASR Transcription Correction

Install: claude plugin install daymade-audio@daymade-skills (suite-only — invoked as daymade-audio:transcript-fixer)

Correct speech-to-text (ASR/STT) errors with a Stage 1 dictionary pre-filter, a required Native AI whole-transcript pass, and an audio-backed human gate for unresolved wording, names, numbers, and entities.

When to use:

  • Correcting meeting notes, lecture recordings, or interview transcripts
  • Fixing Chinese/English homophone errors and technical terminology
  • Reviewing one exact transcript with its original audio instead of searching a global queue
  • Improving future transcripts without turning one-off fixes into broad dictionary rules
  • Collaborating with teams on shared correction knowledge bases

Key features:

  • Stage 1 + Native AI correction pipeline; Stage 1 alone is never completion
  • Frozen review packets and checked file/segment coverage for split or resumed Native reviews; malformed results stay unready and valid work can be reused
  • Exact-file review queue, deep-linked dashboard, timestamped audio playback, and machine-readable zero-pending readback
  • Conservative pattern learning: file-only, dictionary, roster, and context have separate admission rules
  • Domain-specific dictionaries (general, embodied_ai, finance, medical)
  • SQLite-based correction repository
  • Team collaboration with import/export
  • GLM API integration for AI corrections
  • Cost optimization through dictionary promotion

Example workflow:

# Initialize and add corrections
uv run scripts/fix_transcription.py --init
uv run scripts/fix_transcription.py --add "错误词" "正确词" --domain general

# Run full correction pipeline
uv run scripts/fix_transcription.py --input meeting.md --stage 3

# Open only this transcript's unresolved items and listen before deciding
uv run scripts/review-dashboard/server.py --file "/absolute/meeting.md"

# Read the human verdicts back; pending_total must be 0 before final delivery
uv run scripts/fix_transcription.py \
  --list-review --review-file "/absolute/meeting.md" \
  --review-status all --json

📚 Documentation: See daymade-audio/transcript-fixer/references/ for workflow guides, SQL queries, troubleshooting, best practices, team collaboration, and API setup.

Requirements: Python 3.10+ and uv. Native AI correction uses the active agent; an external API key is needed only for the optional agent-less API route.


video-comparer - Video Comparison and Quality Analysis

Compare two videos and generate interactive HTML reports with quality metrics and frame-by-frame visual comparisons.

When to use:

  • Comparing original and compressed videos
  • Analyzing video compression quality and efficiency
  • Evaluating codec performance or bitrate reduction impact
  • Assessing before/after compression results
  • Quality analysis for video encoding workflows

Key features:

  • Quality metrics calculation (PSNR, SSIM)
  • Frame-by-frame visual comparison with three viewing modes:
    • Slider mode: Drag to reveal differences
    • Side-by-side mode: Simultaneous display
    • Grid mode: Compact 2-column layout
  • Video metadata extraction (codec, resolution, bitrate, duration, file size)
  • Self-contained HTML reports (no server required, works offline)
  • Security features (path validation, resource limits, timeout controls)
  • Multi-platform FFmpeg support (macOS, Linux, Windows)

Example usage:

# Basic comparison
python3 scripts/compare.py original.mp4 compressed.mp4

# Custom output and frame interval
python3 scripts/compare.py original.mp4 compressed.mp4 -o report.html --interval 10

# Batch processing
for original in originals/*.mp4; do
    compressed="compressed/$(basename "$original")"
    output="reports/$(basename "$original" .mp4).html"
    python3 scripts/compare.py "$original" "$compressed" -o "$output"
done

🎬 Live Demo

Coming soon

📚 Documentation: See video-comparer/references/ for quality metrics interpretation, FFmpeg commands, and configuration options.

Requirements: Python 3.8+, FFmpeg/FFprobe (install via brew install ffmpeg, apt install ffmpeg, or winget install ffmpeg)


qa-expert - Comprehensive QA Testing Infrastructure

Establish world-class QA testing processes with autonomous LLM execution, Google Testing Standards, and OWASP security best practices.

When to use:

  • Setting up QA infrastructure for new or existing projects
  • Writing standardized test cases following Google Testing Standards (AAA pattern)
  • Implementing security testing (OWASP Top 10 coverage)
  • Executing comprehensive test plans with automatic progress tracking
  • Filing bugs with proper P0-P4 severity classification
  • Calculating quality metrics and enforcing quality gates
  • Enabling autonomous LLM-driven test execution (100x speedup)
  • Preparing QA documentation for third-party team handoffs

Key features:

  • One-command initialization: Complete QA infrastructure with templates, CSVs, and documentation
  • Autonomous execution: Master prompt enables LLM to auto-execute all tests, auto-track results, auto-file bugs
  • Google Testing Standards: AAA pattern compliance, 90% coverage targets, fail-fast validation
  • OWASP security testing: 90% Top 10 coverage with specific attack vectors
  • Quality gates enforcement: 100% execution, ≥80% pass rate, 0 P0 bugs, ≥80% code coverage
  • Ground Truth Principle: Prevents doc/CSV sync issues (test docs = authoritative source)
  • Bug tracking: P0-P4 classification with detailed repro steps and environment info
  • Day 1 onboarding: 5-hour guide for new QA engineers
  • 30+ LLM prompts: Ready-to-use prompts for specific QA tasks
  • Metrics dashboard: Test execution progress, pass rate, bug analysis, quality gates status

Example usage:

# Initialize QA project (creates full infrastructure)
python3 scripts/init_qa_project.py my-app ./

# Calculate quality metrics and gates status
python3 scripts/calculate_metrics.py tests/TEST-EXECUTION-TRACKING.csv

# For autonomous execution, copy master prompt from:
# references/master_qa_prompt.md → paste to LLM → auto-executes 342 tests over 5 weeks

🎬 Live Demo

Coming soon

📚 Documentation: See qa-expert/references/ for:

  • master_qa_prompt.md - Single command for autonomous execution (100x speedup)
  • google_testing_standards.md - AAA pattern, coverage thresholds, OWASP testing
  • day1_onboarding.md - 5-hour onboarding timeline for new QA engineers
  • ground_truth_principle.md - Preventing doc/CSV sync issues
  • llm_prompts_library.md - 30+ ready-to-use QA prompts

Requirements: Python 3.8+

💡 Innovation: The autonomous execution capability (via master prompt) enables LLM to execute entire test suites 100x faster than manual execution, with zero human error in tracking. Perfect for third-party QA handoffs - just provide the master prompt and they can start testing immediately.


prompt-optimizer - Prompt Engineering with EARS Methodology

Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) - a methodology created by Rolls-Royce for converting natural language into testable requirements.

Methodology inspired by: 阿星AI工作室 (A-Xing AI Studio), which pioneered combining EARS with domain theory grounding for practical prompt enhancement.

When to use:

  • Converting loose requirements into structured specifications
  • Optimizing prompts for AI code generation or content creation
  • Breaking down vague feature requests into atomic, testable statements
  • Adding domain theory grounding to technical requirements
  • Transforming "build X" requests into detailed implementation specs
  • Learning prompt engineering best practices with proven frameworks

Key features:

  • EARS transformation: 5 sentence patterns (ubiquitous, event-driven, state-driven, conditional, unwanted behavior)
  • 6-step optimization workflow: Analyze → Transform → Identify theories → Extract examples → Enhance → Present
  • Domain theory catalog: 40+ frameworks mapped to 10 domains (productivity, UX, gamification, learning, e-commerce, security)
  • Structured prompt framework: Role/Skills/Workflows/Examples/Formats template
  • Advanced techniques: Multi-stakeholder requirements, non-functional specs, complex conditional logic
  • Complete examples: Procrastination app, e-commerce product page, learning dashboard, password reset
  • Theory grounding: GTD, BJ Fogg Behavior Model, Gestalt Principles, AIDA, Zero Trust, and more
  • Progressive disclosure: Bundled references (ears_syntax.md, domain_theories.md, examples.md)

Example usage:

# Before (vague)
"Build me a password reset feature"

# After EARS transformation (7 atomic requirements)
1. When user clicks "Forgot Password", the system shall display email input field
2. When user submits valid email, the system shall send password reset link valid for 1 hour
3. When user clicks reset link, the system shall verify token has not expired
4. When token is valid, the system shall display password creation form requiring minimum 12 characters, 1 uppercase, 1 number, 1 special character
5. When user submits new password meeting requirements, the system shall hash password with bcrypt and invalidate reset token
6. When user attempts password reset more than 3 times in 1 hour, the system shall block further attempts for 1 hour
7. If reset token has expired, the system shall display error message and option to request new link

# Enhanced with domain theories
- Zero Trust Architecture (verify at each step)
- Defense in Depth (rate limiting + token expiration + password complexity)
- Progressive Disclosure (multi-step UX flow)

# Full prompt includes Role, Skills, Workflows, Examples, Formats

🎬 Live Demo

Coming soon

📚 Documentation: See prompt-optimizer/references/ for:

  • ears_syntax.md - Complete EARS patterns and transformation rules
  • domain_theories.md - 40+ theories mapped to domains with selection guidance
  • examples.md - Full transformation examples with before/after comparisons

💡 Innovation: EARS methodology eliminates ambiguity by forcing explicit conditions, triggers, and measurable criteria. Combined with domain theory grounding (GTD, BJ Fogg, Gestalt, etc.), it transforms "build a todo app" into a complete specification with behavioral psychology principles, UX best practices, and concrete test cases - enabling test-driven development from day one.


local-conversation-history - Cross-Provider History Entry Point

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:local-conversation-history)

The entry point above the four provider-and-action-specific history skills. It routes a request to whichever one 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.

When to use:

  • The provider is unknown or plural — "our history", "what have I been working on"
  • Listing Kimi CLI sessions, which has no dedicated skill of its own
  • It is unclear whether the need is evidence or resumption
  • You remember this entry point by name

When not to use: the platform and the action are both already clear. Load that executor skill directly instead — this router adds a hop, not information.

Design: a thin routing layer. It carries no parsing, no provider-specific flags beyond --source, and no copies of the executors' commands, so it cannot drift into teaching a stale invocation.


read-claude-code-history - Read Local Claude Code History

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:read-claude-code-history)

Read, search, and export Claude Code history across all active config homes and the long-term archives registered in ~/.claude/history-sources.json, without resuming or modifying the old task.

When to use:

  • Recovering deleted or lost files from previous Claude Code sessions
  • Reconstructing one known Session as a chronological user/assistant handoff
  • Listing what the human actually typed, including queued mid-turn corrections
  • Searching for specific code across conversation history
  • Tracking file modifications across multiple sessions
  • Finding sessions containing specific keywords or implementations
  • Finding which session ran a given command or tool call in a known time window, or when hook runs happened (outcome, duration, exit code)
  • Verifying date-bounded topics after a machine migration without trusting mtime

Key features:

  • Complete source set: Search active homes and registered archives by default
  • Provider boundary: Claude-only by default; Codex requests route to read-codex-history
  • Cross-project sweep: --all-projects searches every Claude project when the project is unknown; --exclude-session skips self-matches
  • Copy-safe union: Search distinct records from every copy of a session ID without double-counting identical records
  • Internal-time search: Filter matching records by JSONL timestamps, never file mtime
  • Structured search: Cover messages, thinking, tools, results, queues, attachments, summaries, and original file-history paths
  • Exact checkpoint recovery: Union same-session copies and companion roots, then restore captured bytes after Write/Edit/shell changes, including binaries and pre-deletion checkpoints
  • Fail-visible fidelity: Label Write-only checkpoints as lower fidelity and abort when exact metadata points to missing bytes instead of silently guessing
  • Statistics analysis: Message counts, tool usage breakdown, file operations
  • Batch operations: Process multiple sessions with keyword filtering
  • Streaming processing: Handle large session files (>100MB) efficiently
  • Read/continue separation: Produces an evidence receipt and never resumes work itself

Example usage:

# List recent sessions for a project
python3 scripts/analyze_sessions.py list /path/to/project

# Read one Session chronologically, preserving queued human input
python3 scripts/read_claude_session.py --session  --project /path/to/project --full

# Export recent human wording grouped by Session
python3 scripts/extract_user_messages.py ./user-words --days 7 --group-by session

# Search sessions for keywords
python3 scripts/analyze_sessions.py search /path/to/project \
  "ComponentName" "featureX" --from-date 2026-03-01 --to-date 2026-04-30

# Recover deleted files from the exact path printed by search
python3 scripts/recover_content.py  -k DeletedComponent -o ./recovered/

# Search every project for multiple vanished job artifacts
python3 scripts/analyze_sessions.py search --all-projects \
  artifact-a.html artifact-b.html \
  --exclude-session 

# Get session statistics
python3 scripts/analyze_sessions.py stats /path/to/session.jsonl --show-files

🎬 Live Demo

Coming soon

📚 Documentation: See daymade-claude-code/read-claude-code-history/references/ for:

  • session_file_format.md - JSONL structure and extraction patterns
  • workflow_examples.md - Detailed recovery and analysis workflows

docs-cleaner - Documentation Consolidation

Install: claude plugin install daymade-docs@daymade-skills (suite-only — invoked as daymade-docs:docs-cleaner)

Consolidate redundant documentation while preserving all valuable content.

When to use:

  • Cleaning up documentation bloat across projects
  • Merging redundant docs covering the same topics
  • Reducing documentation sprawl after rapid development
  • Consolidating multiple files into authoritative sources

Key features:

  • Content preservation: Never lose valuable information during cleanup
  • Redundancy detection: Identify overlapping documentation
  • Smart merging: Combine related docs while maintaining structure
  • Validation: Ensure consolidated docs are complete and accurate

🎬 Live Demo

Coming soon


skills-search - CCPM Skill Registry Search

Search, discover, install, and manage Claude Code skills from the CCPM (Claude Code Plugin Manager) registry.

When to use:

  • Finding skills for specific tasks (e.g., "find PDF skills")
  • Installing skills by name
  • Listing currently installed skills
  • Getting detailed information about a skill
  • Managing your Claude Code skill collection

Key features:

  • Registry search: Search CCPM registry with ccpm search
  • Skill installation: Install skills with ccpm install
  • Version support: Install specific versions with @version syntax
  • Bundle installation: Install pre-configured skill bundles (web-dev, content-creation, developer-tools)
  • Multiple formats: Supports registry names, GitHub owner/repo, and full URLs
  • Skill info: Get detailed skill information with ccpm info

Example usage:

# Search for skills
ccpm search pdf              # Find PDF-related skills
ccpm search "code review"    # Find code review skills

# Install skills
ccpm install skill-creator                # From registry
ccpm install daymade/skill-creator        # From GitHub
ccpm install [email protected]          # Specific version

# List and manage
ccpm list                    # List installed skills
ccpm info skill-creator      # Get skill details
ccpm uninstall pdf-processor # Remove a skill

# Install bundles
ccpm install-bundle web-dev  # Install web development skills bundle

🎬 Live Demo

Coming soon

📚 Documentation: See daymade-skill/skills-search/SKILL.md for complete command reference

Requirements: CCPM CLI (npm install -g @daymade/ccpm)


pdf-creator - PDF Creation with Chinese Font Support

Install: claude plugin install daymade-docs@daymade-skills (suite-only — invoked as daymade-docs:pdf-creator)

Create professional PDF documents from markdown with proper Chinese typography using WeasyPrint.

When to use:

  • Converting markdown to PDF for sharing or printing
  • Generating formal documents (legal filings, reports)
  • Ensuring correct Chinese font rendering

Key features:

  • pandoc + WeasyPrint conversion pipeline (dual backend: WeasyPrint or headless Chrome)
  • Built-in Chinese/Japanese/Korean (CJK) font fallbacks with auto CJK code-block rendering
  • Theme system (default for formal docs, cjk-auto for content-driven tables, warm-terra for training materials, mobile for phone reading)
  • A4 layout defaults with print-friendly margins
  • Batch conversion scripts

Example usage:

uv run --with weasyprint scripts/md_to_pdf.py input.md output.pdf

🎬 Live Demo

Coming soon

📚 Documentation: See daymade-docs/pdf-creator/SKILL.md for setup and workflow details.

Requirements: Python 3.8+, pandoc (system install), weasyprint (or Chrome as fallback backend)


claude-md-progressive-disclosurer - CLAUDE.md Optimization

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:claude-md-progressive-disclosurer)

Optimize user CLAUDE.md files using progressive disclosure to reduce context bloat while preserving critical rules.

When to use:

  • CLAUDE.md is too long or repetitive
  • Need to move detailed procedures into references
  • Want to extract reusable workflows into skills

Key features:

  • Section classification (keep/move/extract/remove)
  • Before/after line-count reporting
  • Reference file and pointer formats
  • Best-practice optimization workflow

Example usage:

"Optimize my ~/.claude/CLAUDE.md using progressive disclosure and propose a plan."

🎬 Live Demo

Coming soon

📚 Documentation: See claude-md-progressive-disclosurer/SKILL.md.


promptfoo-evaluation - Promptfoo LLM Evaluation

Configure and run LLM evaluations with Promptfoo for prompt testing and model comparisons.

When to use:

  • Setting up prompt tests and eval configs
  • Comparing LLM outputs across providers
  • Adding custom assertions or LLM-as-judge grading

Key features:

  • promptfooconfig.yaml templates
  • Python custom assertions
  • llm-rubric scoring guidance
  • Built-in preview (echo provider) workflows

Example usage:

npx promptfoo@latest init
npx promptfoo@latest eval
npx promptfoo@latest view

🎬 Live Demo

Coming soon

📚 Documentation: See promptfoo-evaluation/references/promptfoo_api.md.

Requirements: Node.js (Promptfoo via npx promptfoo@latest)


developing-ios-apps - iOS App Development

Install: claude plugin install daymade-macos@daymade-skills (suite-only — invoked as daymade-macos:developing-ios-apps)

Build, configure, and debug iOS apps with XcodeGen, SwiftUI, and Swift Package Manager.

When to use:

  • Setting up XcodeGen project.yml
  • Fixing SPM dependency or embed issues
  • Handling code signing and device deployment errors
  • Debugging camera/AVFoundation problems

Key features:

  • XcodeGen project templates
  • SPM dynamic framework embedding fixes
  • Code signing and provisioning guidance
  • Device deployment and troubleshooting checklists

Example usage:

xcodegen generate
xcodebuild -destination 'platform=iOS Simulator,name=iPhone 17' build

🎬 Live Demo

Coming soon

📚 Documentation: See developing-ios-apps/references/xcodegen-full.md.

Requirements: macOS + Xcode, XcodeGen


twitter-reader - Twitter/X Content Fetching

Fetch Twitter/X post and article content. Single-post text goes through the fxtwitter mirror API (login-free, key-free, full long-form body); X Articles with images go through fetch_article.py; the Jina API path remains as a fallback with a known intermittent-ban risk.

When to use:

  • Retrieving tweet content for analysis or documentation
  • Fetching X Articles (long-form) with all images downloaded locally
  • Extracting images and media from posts
  • Batch downloading multiple tweets for reference

Key features:

  • Single posts: fxtwitter mirror — no key, no login, full tweet.text body including note_tweet long-form
  • No JavaScript rendering or browser automation needed
  • No Twitter authentication required
  • Returns markdown-formatted content with metadata
  • Supports both individual and batch fetching
  • Includes author, timestamp, post text, images, and replies
  • Environment variable configuration for secure API key management

Example usage:

# Single post text (preferred): fxtwitter mirror, no key needed
curl -sS "https://api.fxtwitter.com/USER/status/TWEET_ID" \
  | python3 -c "import json,sys; t=json.load(sys.stdin)['tweet']; print(t['text'])"

# X Article with images (full mode)
uv run --with pyyaml python scripts/fetch_article.py \
  "https://x.com/USER/status/TWEET_ID" ./Clippings

# Jina fallback (intermittent — see SKILL.md risk note)
export JINA_API_KEY="your_api_key_here"
curl "https://r.jina.ai/https://x.com/USER/status/TWEET_ID" \
  -H "Authorization: Bearer ${JINA_API_KEY}"

# Batch fetch multiple tweets
scripts/fetch_tweets.sh \
  "https://x.com/user/status/123" \
  "https://x.com/user/status/456"

# Fetch to file using Python script
python scripts/fetch_tweet.py https://x.com/user/status/123 output.md

🎬 Live Demo

Coming soon

📚 Documentation: See twitter-reader/SKILL.md for full details and URL format support.

Requirements:

  • curl (pre-installed on most systems) — single-post path needs nothing else
  • Python 3.6+ (for Python scripts)
  • Jina.ai API key (only for the Jina fallback; intermittent-ban risk, and the shared repo key is currently out of balance / 402)

macos-cleaner - Intelligent macOS Disk Space Recovery

Install: claude plugin install daymade-macos@daymade-skills (suite-only — invoked as daymade-macos:macos-cleaner)

The safest way to reclaim disk space on macOS. Start with targeted read-only diagnosis when a subsystem is already suspect—including Apple Content Caching—then analyze caches, application remnants, large files, and development environments only as needed.

Why macos-cleaner stands out:

  • Safety-First Philosophy: Never deletes without explicit user confirmation. Every operation includes risk assessment (🟢 Safe / 🟡 Caution / 🔴 Keep).
  • Intelligence Over Automation: Analyzes first, explains thoroughly, then lets you decide. Unlike one-click cleaners that blindly delete, we help you understand what you're removing and why.
  • Developer-Friendly: Deep analysis of Docker, Homebrew, npm, pip caches - tools that generic cleaners miss.
  • Transparent & Educational: Every recommendation includes an explanation of what the file is, why it's safe (or not), and what happens if you delete it.
  • Professional Quality: Built by developers who know the pain of accidentally deleting important files. Includes comprehensive safety checks and Time Machine backup recommendations.

Our design principles:

  1. User Control First: You make the decisions, we provide the insights
  2. Explain Everything: No mysterious deletions - full transparency on impact
  3. Conservative Defaults: When uncertain, we preserve rather than delete
  4. Developer Context: Understand development tool caches, not just system files
  5. Hybrid Approach: Combine script precision with visual tools (Mole integration)

When to use:

  • Your Mac is running out of disk space (>80% full)
  • You're a developer with Docker/npm/pip/Homebrew caches piling up
  • Apple Content Caching reports Caching needs more space, an unlimited cache, or unexpectedly high ActualCacheUsed
  • You want to understand what's consuming space, not just delete blindly
  • You need to clean up after uninstalled applications
  • You prefer understanding over automation

Key features:

  • Smart Cache Analysis: Categorizes system caches, app caches, logs by safety level
  • Apple Content Caching: Separates logical CacheUsed from physical ActualCacheUsed, verifies peers and protected services, and uses Apple's supported limit/deactivate/flush controls
  • Application Remnant Detection: Finds orphaned data from uninstalled apps with confidence scoring
  • Large & Duplicate File Discovery: Intelligent categorization plus optional read-only fdupes scans inside exact approved paths
  • Development Environment Cleanup: Docker images/containers/volumes, OrbStack, Homebrew, npm, and pip; Docker build cache is measured but prune-based deletion is out of scope
  • Interactive Safe Deletion: Batch confirmation, selective deletion, undo-friendly (uses Trash when possible)
  • Before/After Reports: Track space recovery with detailed breakdown
  • Mole Integration: Seamless workflow with visual cleanup tool for GUI preferences
  • Risk Categorization: Every item labeled with safety level and explanation
  • Time Machine Awareness: Recommends backups before large deletions (>10 GB)

What makes us different:

  • ✅ Trust Through Transparency: Other cleaners hide what they delete. We show everything and explain why.
  • ✅ Developer-Centric: We clean Docker, not just browser caches. We understand .git directories, node_modules, and build artifacts.
  • ✅ Safety Checks Built-In: Protection against deleting system files, user data, credentials, active databases, or files in use.
  • ✅ Educational: Learn what's safe to delete and why, so you can maintain your Mac confidently.
  • ❌ Not a One-Click Solution: Nothing changes until you approve a scoped command plan. When you ask Claude to execute it, only those confirmed actions run, followed by before/after verification.

Example usage:

# Install the Apple platform suite
claude plugin install daymade-macos@daymade-skills

# Ask Claude Code to analyze your Mac
"My Mac is running out of space, help me analyze what's using storage"

# Claude will:
# 1. Route a named suspect to targeted read-only diagnosis; scan broadly only if the source is unknown
# 2. Present categorized findings with safety levels
# 3. Explain each category (caches, remnants, large files, dev tools)
# 4. Recommend cleanup approach
# 5. Execute ONLY what you confirm

# Example analysis output:
📊 Disk Space Analysis
━━━━━━━━━━━━━━━━━━━━━━━━
Total:     500 GB
Used:      450 GB (90%)
Available:  50 GB (10%)

🟢 Safe to Clean (95 GB):
  - System caches:     45 GB (apps regenerate automatically)
  - Homebrew cache:     5 GB (reinstalls when needed)
  - npm cache:          3 GB (safe to clear)
  - Old logs:           8 GB (diagnostic data only)
  - Trash:             34 GB (already marked for deletion)

🟡 Review Recommended (62 GB):
  - Large downloads:   38 GB (may contain important files)
  - App remnants:       8 GB (verify apps are truly uninstalled)
  - Docker images:     12 GB (may be in use)
  - Old .git repos:     4 GB (verify project is archived)

🔴 Keep Unless Certain (0 GB):
  - No high-risk items detected

Recommendation: Start with 🟢 Safe items (95 GB), then review 🟡 items together.

🎬 Live Demo

Coming soon

📚 Documentation: See macos-cleaner/references/ for:

  • apple_content_caching.md - Targeted Apple Content Caching diagnosis and supported repair
  • cleanup_targets.md - Detailed explanations of every cleanup target
  • mole_integration.md - How to combine scripts with Mole visual tool
  • safety_rules.md - Comprehensive safety guidelines and what to never delete

Requirements:

  • Python 3.6+ (pre-installed on macOS)
  • macOS (tested on macOS 10.15+)
  • Optional: Mole for visual cleanup interface

fact-checker - Document Fact-Checking

Verify factual claims in documents using web search and official sources, then propose corrections with user confirmation.

When to use:

  • Fact-checking documents for accuracy
  • Verifying AI model specifications and technical documentation
  • Updating outdated information in documents
  • Validating statistical claims and benchmarks
  • Checking API capabilities and version numbers

Key features:

  • Web search integration with authoritative sources
  • AI model specification verification
  • Technical documentation accuracy checks
  • Statistical data validation
  • Automated correction reports with user confirmation
  • Supports general factual statements and technical claims

Example usage:

# Install the skill
claude plugin install fact-checker@daymade-skills

# Fact-check a document
"Please fact-check this section about AI model capabilities"

# Verify technical specs
"Check if these Claude model specifications are still accurate"

# Update outdated info
"Verify and update the version numbers in this documentation"

🎬 Live Demo

Coming soon

📚 Documentation: See fact-checker/SKILL.md for full workflow and claim types.

Requirements:

  • Web search access (via Claude Code)

skill-reviewer - Skill Quality Review & Improvement

Review and improve Claude Code skills against official best practices with three powerful modes.

When to use:

  • Validating your own skills before publishing
  • Evaluating others' skill repositories
  • Contributing improvements to open-source skills via auto-PR
  • Ensuring skills follow marketplace standards

Key features:

  • Self-review mode: Run the bundled reviewer backed by canonical skill-creator validation
  • External review mode: Clone, analyze, and generate improvement reports
  • Auto-PR mode: Fork → improve → submit PR with additive-only changes
  • Evaluation checklist: Frontmatter, instructions, resources verification
  • Additive-only principle: Never delete files when contributing to others
  • PR guidelines: Tone recommendations and professional templates
  • Reliable automation: Distinguishes review findings from invocation/runtime failures with structured JSON output
  • Evidence-based design review: Score six dimensions with exact source citations; keep documented design quality separate from measured task benefit
  • Read-only batch review: Inventory collections against declared host contracts, prepare complete selected-source packets, and export JSON/CSV/Markdown with explicit coverage and invalid decisions quarantined

Example usage:

# Install the skill
claude plugin install daymade-skill@daymade-skills

# Self-review your skill
"Validate my skill at ~/my-skills/my-awesome-skill"

# Review external skill repository
"Review the skills at https://github.com/user/skill-repo"

# Auto-PR improvements
"Fork, improve, and submit PR for https://github.com/user/skill-repo"

🎬 Live Demo

Coming soon

📚 Documentation: See daymade-skill/skill-reviewer/references/ for:

  • evaluation_checklist.md - Complete skill evaluation criteria
  • pr_template.md - Professional PR description template

github-contributor - GitHub Contribution Strategy

Strategic guide for becoming an effective GitHub contributor and building your open-source reputation.

When to use:

  • Looking for projects to contribute to
  • Learning contribution best practices
  • Building your GitHub presence and reputation
  • Understanding how to write high-quality PRs

Key features:

  • Four contribution types: Documentation, Code Quality, Bug Fixes, Features
  • Project selection criteria: What makes a good first project vs red flags
  • PR excellence workflow: Before → During → After submission checklist
  • Reputation building ladder: Documentation → Bug Fixes → Features → Maintainer
  • GitHub CLI commands: Quick reference for fork, PR, issue operations
  • Conventional commit format: Type, scope, description structure
  • Common mistakes: What to avoid and best practices

Contribution types explained:

Level 1: Documentation fixes (lowest barrier, high impact)
    ↓ (build familiarity)
Level 2: Code quality (medium effort, demonstrates skill)
    ↓ (understand codebase)
Level 3: Bug fixes (high impact, builds trust)
    ↓ (trusted contributor)
Level 4: Feature additions (highest visibility)
    ↓ (potential maintainer)

Example usage:

# Install the skill
claude plugin install github-contributor@daymade-skills

# Find good first issues
"Help me find projects with good first issues in Python"

# Write a high-quality PR
"Guide me through creating a PR for this bug fix"

# Build contribution strategy
"Help me plan a contribution strategy for building my GitHub profile"

🎬 Live Demo

Coming soon

📚 Documentation: See github-contributor/references/ for:

  • pr_checklist.md - Complete PR quality checklist
  • project_evaluation.md - How to evaluate projects for contribution
  • communication_templates.md - Issue and PR communication templates

i18n-expert - Internationalization & Localization

Complete internationalization/localization setup and auditing for UI codebases. Configure i18n frameworks, replace hard-coded strings with translation keys, ensure locale parity between en-US and zh-CN, and validate pluralization and formatting.

When to use:

  • Setting up i18n for new React/Next.js/Vue applications
  • Auditing existing i18n implementations for key parity and completeness
  • Replacing hard-coded strings with translation keys
  • Ensuring proper error code mapping to localized messages
  • Validating pluralization, date/time/number formatting across locales
  • Implementing language switching and SEO metadata localization

Key features:

  • Library selection and setup (react-i18next, next-intl, vue-i18n)
  • Key architecture and locale file organization (JSON, YAML, PO, XLIFF)
  • Translation generation strategy (AI, professional, manual)
  • Routing and language detection/switching
  • SEO and metadata localization
  • RTL support for applicable locales
  • Key parity validation between en-US and zh-CN
  • Pluralization and formatting validation
  • Error code mapping to localized messages
  • Bundled i18n_audit.py script for key usage extraction

Example usage:

# Install the skill
claude plugin install i18n-expert@daymade-skills

# Setup i18n for a new project
"Set up i18n for my React app with English and Chinese support"

# Audit existing i18n implementation
"Audit the i18n setup and find missing translation keys"

# Replace hard-coded strings
"Replace all hard-coded strings in this component with i18n keys"

🎬 Live Demo

Coming soon

📚 Documentation: See i18n-expert/SKILL.md for complete workflow and architecture guidance.

Requirements:

  • Python 3.6+ (for audit script)
  • React/Next.js/Vue (framework-specific i18n library)

claude-skills-troubleshooting - Plugin & Skill Troubleshooting

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:claude-skills-troubleshooting)

Diagnose and resolve Claude Code plugin and skill configuration issues. Debug plugin installation, enablement, and activation problems with systematic workflows.

When to use:

  • Plugins installed but not showing in available skills list
  • Skills not activating as expected despite installation
  • Troubleshooting enabledPlugins configuration in settings.json
  • Debugging "plugin not working" or "skill not showing" issues
  • Understanding plugin state architecture and lifecycle

Key features:

  • Quick diagnosis via diagnostic script (detects installed vs enabled mismatch)
  • Plugin state architecture documentation (installed_plugins.json vs settings.json)
  • Marketplace cache freshness detection and update guidance
  • Known GitHub issues tracking (#17832, #19696, #17089, #13543, #16260)
  • Batch enable script for missing plugins from a marketplace
  • Skills vs Commands architecture explanation
  • Comprehensive diagnostic commands reference

Example usage:

# Run diagnostic
python3 scripts/diagnose_plugins.py

# Batch enable missing plugins
python3 scripts/enable_all_plugins.py daymade-skills

🎬 Live Demo

Coming soon

📚 Documentation: See claude-skills-troubleshooting/SKILL.md for complete troubleshooting workflow and architecture guidance.

Requirements: None (uses Claude Code built-in Python)


audio-router - StepFun Speech and Meeting-Minutes Routing

Install: claude plugin install daymade-audio@daymade-skills (suite-only — invoked as daymade-audio:audio-router)

Selects the installed StepFun ASR, StepFun TTS, or transcript-to-minutes specialist and reads its full instructions at use time. Their original slash commands remain available manually. General audio transcription and transcript correction retain direct automatic entries.


meeting-minutes-taker - Meeting Minutes Generator

Install: claude plugin install daymade-audio@daymade-skills (suite-only — invoked as daymade-audio:meeting-minutes-taker)

Transform meeting transcripts into high-fidelity, structured meeting minutes with iterative human review.

When to use:

  • Meeting transcript provided and minutes/notes/summaries requested
  • Multiple versions of meeting minutes need merging without content loss
  • Existing minutes need review against original transcript for missing items

Key features:

  • Multi-pass parallel generation with UNION merge strategy
  • Evidence-based recording with speaker quotes
  • Mermaid diagrams for architecture discussions
  • Iterative human-in-the-loop refinement workflow
  • Cross-AI comparison for bias reduction
  • Completeness checklist for systematic review

Example usage:

# Install the full audio suite (includes meeting-minutes-taker)
claude plugin install daymade-audio@daymade-skills

# Then provide a meeting transcript and request minutes

🎬 Live Demo

Coming soon

📚 Documentation: See daymade-audio/meeting-minutes-taker/SKILL.md for complete workflow and template guidance.

Requirements: None


deep-research - Research Reports and Provider Runs

Generate research reports from a durable study record: original sources, claim-level citations, rejected leads, and prior studies remain available for the next question. When several AI products or modes investigate one decision, coordinate their existing Skills and agents in parallel, preserve original outputs, and synthesize against the underlying sources and business question.

When to use:

  • Need a structured research report, literature review, or market/industry analysis
  • Require strict section formatting or a template to be enforced
  • Need evidence mapping, citations, and source quality review
  • Want multi-pass synthesis to avoid missing key findings

Key features:

  • Report spec and format contract workflow
  • Evidence table with source quality rubric
  • Multi-pass complete drafting with UNION merge
  • Citation verification and conflict handling
  • Project-local source and claim records for single-route and multi-route studies, with a searchable catalog for reuse
  • Exact seed-document handoff, persistent session aliases, and verified-source-first catalog search
  • Local provider × mode task and artifact ledger with provenance and hash checks
  • Read-only parallel dispatch board that separates shared app control, active tasks, completed reports and held routes; actual provider calls follow their own Skills and authorization rules
  • Ready-to-use report template and formatting rules

Example usage:

# Install the skill
claude plugin install deep-research@daymade-skills

# Then provide a report spec or template and request a deep research report

🎬 Live Demo

Coming soon

📚 Documentation: See deep-research/SKILL.md, research-asset-contract.md, and research_report_template.md.

Requirements: None


competitors-analysis - Evidence-Based Competitor Intelligence

Discover, clone, update, and analyze competitor repositories with evidence-based competitive intelligence. Repository-backed findings must come from local cloned code; market-landscape claims must cite their source and volatility.

When to use:

  • Track and analyze competitor products or technologies
  • Discover GitHub competitors for a product or market
  • Create evidence-based competitor profiles
  • Generate competitive landscape and opportunity reports
  • Check whether competitor code has changed
  • Need to document technical decisions with cited sources

Key features:

  • Durable competitor workspace convention using $HOME/workspace/competitors/{product}/
  • GitHub discovery workflow for shortlisting relevant repositories
  • Repository ingest/update flow with remote + commit recording
  • Required source citation format for repository facts (file:line_number)
  • Landscape synthesis for positioning, strengths, weaknesses, opportunities, and risks
  • Tech stack analysis guides for Node.js, Python, Rust projects
  • Bundled templates: profile template, analysis checklist
  • Management script for discover/clone-url/clone/pull/status operations

Example usage:

# Install the skill
claude plugin install competitors-analysis@daymade-skills

# Then ask Claude to analyze a competitor
"分析竞品 https://github.com/org/repo"
"添加竞品到 flowzero 产品的竞品列表"
"看看 claude-flow-viewer 这个方向最近有哪些竞品更新"

🎬 Live Demo

Coming soon

📚 Documentation: See competitors-analysis/SKILL.md and competitors-analysis/references/ for templates.

Requirements: Git (for cloning repositories)


tunnel-doctor - Tailscale + Proxy/VPN Conflict Fixer

Diagnose and fix conflicts when using Tailscale alongside proxy/VPN tools (Shadowrocket, Clash, Surge) on macOS. Covers four independent conflict layers with specific guidance for SSH access to WSL instances.

When to use:

  • Tailscale ping works but SSH/TCP connections time out
  • Proxy tools hijack the Tailscale CGNAT range (100.64.0.0/10)
  • Browser returns HTTP 503 but curl and SSH work
  • git push/pull fails with "failed to begin relaying via HTTP"
  • Setting up Tailscale SSH to WSL and encountering operation not permitted
  • Need to make Tailscale and Shadowrocket/Clash/Surge coexist on macOS

Key features:

  • Four-layer diagnostic model: route hijacking, HTTP env vars, system proxy bypass, SSH ProxyCommand double tunneling
  • Per-tool fix guides for Shadowrocket, Clash, and Surge
  • SSH ProxyCommand double tunnel detection and fix (git push/pull failures)
  • Tailscale SSH ACL configuration (check vs accept)
  • WSL snap vs apt Tailscale installation (snap sandbox breaks SSH)
  • Remote development SOP with proxy-safe Makefile patterns

Example usage:

# Install the skill
claude plugin install tunnel-doctor@daymade-skills

# Then ask Claude to diagnose
"Tailscale ping works but SSH times out"
"Fix Tailscale and Shadowrocket route conflict on macOS"
"git push fails with failed to begin relaying via HTTP"
"Set up Tailscale SSH to my WSL instance"

🎬 Live Demo

Coming soon

📚 Documentation: See tunnel-doctor/references/proxy_conflict_reference.md for per-tool configuration and conflict architecture.


windows-remote-desktop-connection-doctor - AVD/W365 Connection Quality Diagnostician

Diagnose Windows App (Microsoft Remote Desktop / Azure Virtual Desktop / W365) connection quality issues on macOS, with focus on transport protocol optimization (UDP Shortpath vs WebSocket fallback).

When to use:

  • VDI connection is slow with high RTT (>100ms)
  • Transport Protocol shows WebSocket instead of UDP
  • RDP Shortpath fails to establish
  • Connection quality degraded after changing network location
  • Need to identify VPN/proxy interference with STUN/TURN

Key features:

  • 5-step diagnostic workflow from connection info collection to fix verification
  • Transport protocol analysis (UDP Shortpath > TCP > WebSocket hierarchy)
  • VPN/proxy interference detection (ShadowRocket TUN mode, Tailscale exit node)
  • Windows App log parsing for health check failures, certificate errors, FetchClientOptions timeouts
  • ISP UDP restriction testing with STUN connectivity checks
  • Chinese ISP-specific guidance for UDP throttling issues
  • Working vs broken log comparison methodology

Example usage:

# Install the skill
claude plugin install windows-remote-desktop-connection-doctor@daymade-skills

# Then ask Claude to diagnose
"My VDI connection shows WebSocket instead of UDP, RTT is 165ms"
"Diagnose why RDP Shortpath is not working"
"Windows App transport protocol stuck on WebSocket"

🎬 Live Demo

Coming soon

📚 Documentation: See windows-remote-desktop-connection-doctor/references/ for log analysis patterns and AVD transport protocol details.


product-analysis - Multi-Path Product Analysis & Optimization

Run a scalable, evidence-driven product audit using parallel Claude Code agents and optional Codex CLI parallelization. Covers UX, API, architecture, and competitive benchmark workflows with quantified findings and priority recommendations.

When to use:

  • Product launch readiness reviews
  • Multi-perspective codebase and UX audits before release
  • API quality checks with endpoint and consumption consistency reviews
  • Competitive benchmarking against selected competitor repos

Key features:

  • Auto-detects tool context (project stack + optional codex availability)
  • Parallel analysis across dimensions: full, ux, api, arch, compare
  • Multi-agent synthesis with quantified findings and P0/P1/P2 recommendations
  • Built-in comparison hooks with competitors-analysis
  • Cross-validation workflow to reduce overfitting from a single model perspective

Example usage:

# Install the skill
claude plugin install product-analysis@daymade-skills

# Then ask Claude for analysis
"Run product-analysis in full mode for launch audit"
"Do a UX audit and report quantified navigation findings"
"Run API audit and identify unused endpoints"
"Compare this product with our top competitors"

🎬 Live Demo

Coming soon

📚 Documentation: See product-analysis/SKILL.md and product-analysis/references/analysis_dimensions.md for dimension definitions and workflow guidance.

Requirements: Optional codex CLI (for multi-model parallel mode). Skill runs with Claude only if codex is not installed.


financial-data-collector - Financial Data Collection for US Equities

Install: claude plugin install daymade-financial@daymade-skills (suite-only — invoked as daymade-financial:financial-data-collector)

Collect real financial data for any US publicly traded company from free public sources (yfinance). Output structured JSON with market data, historical financials (income statement, cash flow, balance sheet), WACC inputs, and analyst estimates - ready for downstream DCF modeling, comps analysis, or earnings review.

When to use:

  • Collecting structured financial data before building DCF or valuation models
  • Pulling market data (price, shares, beta, market cap) for any US equity ticker
  • Gathering historical income statement, cash flow, and balance sheet data
  • Getting risk-free rate (10Y Treasury) and analyst consensus estimates

Key features:

  • Robust yfinance field mapping with alias chains (handles API instability across versions)
  • NaN year detection and transparent reporting (never fills with estimates)
  • 9-check validation: field completeness, market cap cross-check, CapEx sign convention, net debt consistency
  • NO FALLBACK principle: missing data returns null with _source attribution, never default values
  • FCF definition mismatch flagging (yfinance FCF ≠ investment bank FCF due to SBC)

Example usage:

# Install the suite
claude plugin install daymade-financial@daymade-skills

# Then ask Claude to collect data
"Collect financial data for META"
"Get financials for AAPL --years 3"
"Pull DCF inputs for NVDA"

🎬 Live Demo

Coming soon

📚 Documentation: See financial-data-collector/SKILL.md, output-schema.md, and yfinance-pitfalls.md.

Requirements: Python 3.11+, yfinance, pandas (auto-installed via uv inline dependencies).


excel-automation - Excel Creation, Parsing, and macOS Control

Install: claude plugin install daymade-docs@daymade-skills (suite-only — invoked as daymade-docs:excel-automation)

Create professionally formatted Excel files, parse complex .xlsm models with stdlib XML/ZIP workflows, and control Microsoft Excel windows on macOS via AppleScript.

When to use:

  • Building finance-ready spreadsheets with consistent formatting rules
  • Parsing complex bank/broker .xlsm files that fail in openpyxl
  • Extracting targeted sheet/cell data without loading huge workbooks
  • Automating Excel window operations (zoom, scroll, select) on macOS

Key features:

  • Production template for formatted workbook generation via openpyxl
  • Complex workbook parser using zipfile + xml.etree (no heavy dependencies)
  • Corrupted definedNames repair workflow for problematic files
  • Verified AppleScript command patterns with timeout safeguards
  • Bundled formatting reference for colors, number formats, and table patterns

Example usage:

# Install the documentation suite
claude plugin install daymade-docs@daymade-skills

# Then ask Claude to automate Excel workflows
"Create a formatted valuation template workbook"
"Parse this .xlsm and extract the DCF sheet"
"Generate an AppleScript sequence to zoom and scroll Excel before screenshot"

🎬 Live Demo

Coming soon

📚 Documentation: See excel-automation/SKILL.md and formatting-reference.md.

Requirements: Python 3.8+, uv, openpyxl (auto via uv run --with openpyxl), macOS for AppleScript window control.


capture-screen - Programmatic macOS Screenshot Capture

Install: claude plugin install daymade-macos@daymade-skills (suite-only — invoked as daymade-macos:capture-screen)

Capture application windows by CGWindowID with a reliable three-step workflow: discover window IDs via Swift, control app state via AppleScript, and capture outputs with screencapture.

When to use:

  • Automating repeatable screenshot workflows for documentation
  • Capturing specific app windows instead of full-screen screenshots
  • Producing multi-shot sequences after scripted scroll/zoom changes
  • Building visual evidence capture pipelines on macOS

Key features:

  • Bundled Swift script to resolve accurate window IDs (CGWindowListCopyWindowInfo)
  • Verified AppleScript patterns for app activation and window preparation
  • Window-scoped capture commands with silent mode, delays, and format control
  • Multi-shot workflow pattern for section-by-section capture
  • Clear anti-pattern notes for methods that fail on macOS

Example usage:

# Install the Apple platform suite
claude plugin install daymade-macos@daymade-skills

# Then ask Claude to capture windows programmatically
"Find the Excel window ID and capture it silently"
"Create a multi-shot capture workflow for this workbook"
"Capture Chrome window sections with scripted scrolling"

🎬 Live Demo

Coming soon

📚 Documentation: See capture-screen/SKILL.md.

macos-permissions - Diagnose and Repair macOS Privacy Permissions

Install: claude plugin install daymade-macos@daymade-skills (suite-only — invoked as daymade-macos:macos-permissions)

Use for repeated TCC prompts, silent denials, and background jobs that cannot read protected files. It identifies the actual requester, checks for a usable existing grant, and verifies the repair through the real job. The Skill contains the diagnostic and Full Disk Access repair procedure.

📚 Documentation: See macos-permissions/SKILL.md.

Requirements: macOS. Reading TCC.db also requires Full Disk Access for the process doing the read.


continue-claude-code-work - Resume Interrupted Claude Work

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:continue-claude-code-work)

Continue a verified Claude Code Session without reopening the old interactive session. The continuation layer first consumes read-claude-code-history, then reconstructs the original business outcome, unfulfilled requests, corrections, proven prior assets, and one next action that directly advances the goal.

When to use:

  • A user provides a Claude session ID and wants the task continued
  • You need to inspect local .claude JSONL files instead of running claude --resume
  • A previous session was interrupted and the next concrete step must be reconstructed
  • A multi-agent workflow was interrupted and you need to know which subagents completed

Key features:

  • Requires a chronological read receipt rather than separate user/assistant tail lists
  • Restores original outcome, remaining work, rejected routes, and successful assets
  • Verifies current files, git state, external writes, and background work before duplicating anything
  • Makes the business result—not parser success, review completion, or subprocess exit—the completion unit

Example usage:

# Then ask Claude to resume from local artifacts
"continue work from session 123e4567-e89b-12d3-a456-426614174000"
"don't resume, just read the .claude files and continue"
"check what I was working on in the last session and keep going"

📚 Documentation: See continue-claude-code-work/SKILL.md.

Requirements: Python 3.8+, git for workspace reconciliation.


scrapling-skill - Reliable Scrapling CLI Workflows

Install, troubleshoot, and use Scrapling CLI with a verified static-first workflow for extracting HTML, Markdown, or text from webpages. Includes a diagnostic script for broken extras installs, Playwright browser runtime checks, and smoke tests against real URLs.

When to use:

  • Users mention Scrapling, uv tool install scrapling, or scrapling extract
  • You need to choose between static and browser-backed fetching
  • You need to extract article bodies from WeChat public pages (mp.weixin.qq.com)
  • A Scrapling install works partially but fails on missing extras, browser runtime, or TLS verification

Key features:

  • Bundled diagnose_scrapling.py script for CLI, browser runtime, and live URL smoke tests
  • Verified default path: start with extract get, escalate to extract fetch only when needed
  • WeChat extraction pattern using #js_content for clean article Markdown
  • Troubleshooting guidance for missing click, Playwright runtime setup, and curl: (60) trust-store failures
  • Output validation workflow using file size and content checks instead of exit-code assumptions

Example usage:

# Install the skill
claude plugin install scrapling-skill@daymade-skills

# Then ask Claude to work through Scrapling for you
"Install Scrapling CLI and verify the setup"
"Extract this WeChat article into Markdown with Scrapling"
"Decide whether this page needs static or browser-backed fetching"

🎬 Live Demo

Coming soon

📚 Documentation: See scrapling-skill/SKILL.md and scrapling-skill/references/troubleshooting.md.

Requirements: Python 3.6+, uv, Scrapling CLI, and Playwright browser runtime for browser-backed fetches.


ima-copilot - Tencent IMA Companion & Installer

One-stop wrapper for the official Tencent IMA skill (ima.qq.com). Installs upstream ima-skill to Claude Code, Codex, and OpenClaw via npx skills add, guides API key setup, detects and repairs known upstream issues under user consent, and implements a personalized fan-out search strategy that floats priority knowledge bases to the top.

When to use:

  • Users mention IMA, 腾讯 IMA, ima.qq.com, or need to install the official ima-skill
  • Users report Skipped loading skill(s) due to invalid SKILL.md warnings related to ima-skill
  • You need to search across IMA knowledge bases with KB-priority boosting
  • You need to configure or rotate IMA API credentials
  • Upstream ima-skill ships a known issue (e.g., missing YAML frontmatter in submodule files)

Key features:

  • Zero-config installation to Claude Code / Codex / OpenClaw via vercel-labs/skills with auto-detection and default symlink mode (fix or upgrade once, every agent sees it)
  • XDG-style credential management at ~/.config/ima/{client_id, api_key} with env-var fallback
  • scripts/diagnose.sh read-only health check (install presence, credential liveness, known issues)
  • scripts/search_fanout.py client-side cross-KB search with priority lists, subset-skip lists, and 100-hit silent-truncation detection
  • Wrapper-only architecture: never vendors upstream files, never forks — every repair is a runtime instruction executed with explicit consent and automatic timestamped backups
  • Two user-selectable repair strategies for the frontmatter issue (rename to MODULE.md or prepend minimal frontmatter)
  • Personalization via ~/.config/ima/copilot.json with illustrative-only template values

Example usage:

# Install the skill
claude plugin install ima-copilot@daymade-skills

# Then ask Claude to drive the flow
"Install ima-skill and configure my IMA API key"
"Run diagnose on my ima-skill and fix whatever is broken"
"Search my IMA knowledge bases for embedding model comparisons, priority to my curated KB"

🎬 Live Demo

Coming soon

📚 Documentation: See ima-copilot/SKILL.md and ima-copilot/references/known_issues.md.

Requirements: Node.js 18+ (for npx skills), curl, unzip, Python 3.6+. IMA OpenAPI credentials from https://ima.qq.com/agent-interface.


claude-export-txt-better - Fix Claude Code Export Formatting

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:fixing-claude-export-conversations)

Reconstruct broken line wrapping in Claude Code exported .txt conversation files. Rebuilds tables, paragraphs, paths, and tool calls that were hard-wrapped at fixed column widths, and ships with an automated 53-check validation suite (file-agnostic, catches over- and under-merging regressions).

When to use:

  • Users have a Claude Code export file where tables, paths, or tool output got mangled by line wrapping
  • Users mention "fix export", "fix conversation", "make export readable"
  • Users reference a file matching YYYY-MM-DD-HHMMSS-*.txt
  • Users want to post-process /export output before sharing or archiving it

Key features:

  • Deterministic Python script (fix-claude-export.py) with --stats mode for before/after metrics
  • 53-check automated validator (validate-claude-export-fix.py) that catches regressions
  • Evals directory with real fixture cases
  • No external dependencies beyond uv and Python 3.8+

Example usage:

# Fix and show stats
uv run daymade-claude-code/claude-export-txt-better/scripts/fix-claude-export.py broken.txt --stats

# Custom output path
uv run daymade-claude-code/claude-export-txt-better/scripts/fix-claude-export.py broken.txt -o fixed.txt

# Validate the fix
uv run daymade-claude-code/claude-export-txt-better/scripts/validate-claude-export-fix.py broken.txt fixed.txt

🎬 Live Demo

Coming soon

📚 Documentation: See claude-export-txt-better/SKILL.md and the bundled evals/ fixtures.

Requirements: Python 3.8+, uv package manager.


douban-skill - Douban Collection Export & Sync

Export and sync Douban (豆瓣) book / movie / music / game collections to local CSV files via the reverse-engineered Frodo API. Full export covers all history; RSS incremental sync keeps daily updates current. No login, no cookies, no browser — just a user ID and it works.

When to use:

  • Users want to back up their Douban reading/watching/listening/gaming history
  • Users mention 豆瓣, douban, 读书记录, 观影记录, 书影音
  • Users need incremental sync of recent Douban activity
  • Users want CSV output compatible with Excel (UTF-8 BOM)

Key features:

  • Full export of all 4 categories (books/movies/music/games) via Frodo API
  • RSS incremental sync for daily updates (last ~10 items per feed)
  • Pre-flight user-ID validation (fail-fast on wrong ID)
  • UTF-8 BOM CSV output, Excel-compatible, cross-platform
  • Bundled troubleshooting log documenting 7 tested scraping approaches and why each failed (Douban PoW challenges block every web-scraping approach — only Frodo API works)
  • .gitleaks.toml allowlist for the public Android APK credentials

Example usage:

# Full export of user's collections
uv run douban-skill/scripts/douban-frodo-export.py 

# Incremental RSS sync (last ~10 items per category)
uv run douban-skill/scripts/douban-rss-sync.py 

🎬 Live Demo

Coming soon

📚 Documentation: See douban-skill/SKILL.md and douban-skill/references/troubleshooting.md for the complete failure log of rejected approaches.

Requirements: Python 3.8+, uv package manager. No login or cookies required.


terraform-skill - Terraform Operational Traps

Designs and diagnoses safe Terraform releases as well as the provisioner traps learned from real incidents. It keeps staging and production on one required configuration schema, validates exact candidate bytes + the Compose-rendered environment + the immutable runtime before live mutation, and binds saved plans to staging evidence, source provenance, explicit production authorization, and independent readback.

When to use:

  • Writing null_resource provisioners or remote-exec blocks that SSH into fresh instances
  • Setting up multi-environment (prod/staging/dev) Terraform with shared modules
  • Debugging containers that are Restarting/unhealthy after terraform apply
  • Hitting "docker: not found" in remote-exec, rsync connection drops in local-exec, or TLS cert errors
  • Troubleshooting drift or provisioner failures during re-runs
  • Configuring Caddy/gateway resources with Cloudflare credentials
  • Reviewing a saved plan or broad deploy resource that may also mutate a shared gateway
  • Closing staging/production config drift, receipt, provenance, or production-approval gaps

Key features:

  • One required-key contract for every environment; values may differ, requiredness may not
  • Exact-bundle prevalidation for every normal and recovery writer before any live write/restart
  • Saved-plan, staging-receipt, remote-main provenance, production-approval, and live-readback gates
  • Corrected provider/provisioner patterns for cloud-init, Docker, DNS, TLS, snapshots, and fresh hosts

Example usage:

# Trigger the skill naturally during Terraform work
"I'm getting 'docker: not found' in my null_resource provisioner after apply"
"My rsync local-exec is failing with 'connection unexpectedly closed'"
"Help me write a multi-env Terraform setup without snapshot cross-contamination"
"Staging has this Caddy variable but production leaves it empty — how do I validate both safely?"

🎬 Live Demo

Coming soon

📚 Documentation: See terraform-skill/SKILL.md and the bundled references/ for detailed remediation patterns.

Requirements: None (Terraform-adjacent knowledge only; no runtime dependencies).


slides-creator - Narrative-First Slide Deck Creation

Guides users through structured narrative design (ABCDEFG model), then delegates visual generation to baoyu-slide-deck. Focuses on what machines can't do — narrative co-design with humans.

When to use:

  • Creating presentations, slide decks, or PPTs from user content
  • Turning articles, transcripts, or notes into visual slides
  • Designing narrative arcs for talks and workshops

Key features:

  • Phase 0: Source material collection (user's own words first)
  • Phase 1: Narrative structure discussion using ABCDEFG model
  • Phase 2: Content structuring for machine-readable input
  • Phase 3-5: Delegates visual generation to baoyu-slide-deck
  • Phase 6: Post-processing with directory reorganization and speaker notes extraction

Example usage:

# Trigger the skill naturally
"Help me turn my article into a slide deck"
"Create a presentation from my talk transcript"
"I need a 20-minute deck for a workshop"

Requirements: baoyu-slide-deck skill for visual generation.


excalidraw-use - Place Images onto an Excalidraw Board

Batch-place existing images onto an Excalidraw whiteboard, laid out on a generous grid so nobody has to drag them apart afterwards. Also turns a slide deck into clean per-slide images first, and inspects what is inside a .excalidraw file. The available Excalidraw MCP servers and skills cover element CRUD and export but document no image element type, no dataURL handling, and no files map — embedding your own pictures is the gap this fills.

When to use:

  • Putting screenshots, a picture library, or deck slides onto a whiteboard
  • Spacing many images out so they never need manual adjustment
  • Turning a Vite/React slide deck into images you can draw over
  • Inspecting a scene file: element mix, embedded payload size, occupied extent

Key features:

  • Content-hash dedupe and --exclude for images already on the board
  • --template-from copies the image-element field set out of your own board — Excalidraw's published schema stops before fileId/status/scale/crop
  • Write-back verification: fails on a missing file entry, a distorted aspect ratio, or any overlap
  • Deck capture hides presenter chrome, expands staged reveals, and reports fragments that never rendered
  • Documents the two silent destroyers: Open and drag-and-drop replace a scene (only the clipboard merges), and a stale build removes a source feature while innerText still reads hidden fragments as present

Example usage:

# Trigger the skill naturally
"Put these screenshots on my Excalidraw board"
"Add my old workshop images to the canvas, spaced out"
"Turn this deck into images I can draw on"

Note: Not for generating a diagram from a text description — that is a different job.


debugging-network-issues - Evidence-Driven Network Investigation

Falsification-first methodology for network, streaming, and protocol-layer bugs where the obvious cause is probably wrong. Built from a real 5-hour SSE incident where assumption-stacking wasted hours that a 10-minute layered experiment would have resolved.

When to use:

  • Connection resets (ECONNRESET, HTTP/2 RST_STREAM, INTERNAL_ERROR)
  • SSE / long-polling stalls or fixed-time drops (60s, 100s, 130s)
  • CDN / proxy / CGNAT idle-timeout incidents
  • Client-side proxy / VPN / TUN misrouting (e.g. ERR_CONNECTION_CLOSED, SSL_ERROR_SYSCALL, fake TUN DNS IPs, CNAME-based rule overrides)
  • Certificate-verification errors (UNKNOWN_CERTIFICATE_VERIFICATION_ERROR, wrong-site certificate)
  • Any "works sometimes / fails after N seconds" pattern
  • LAN-layer mysteries: unknown devices on the local network, devices silenced by a subnet change, hosts "dead" on one segment but alive on another
  • Multi-hop systems (client → CDN → LB → reverse proxy → app → upstream) where a symptom could plausibly come from several layers

Key features:

  • Layered isolation experiments: run the same logical request through three or more paths differing by exactly one hop
  • Env-gated runtime instrumentation patterns (no production-code mutation)
  • Counter-review four-question filter to challenge single-cause assumptions
  • Bundled probe scripts (layered-isolation-probe.sh, mock-idle-upstream.py)
  • Real case studies: SSE RST_STREAM at 130s caused by CGNAT idle timeout; proxy/TUN CNAME rule override causing ERR_CONNECTION_CLOSED

Requirements: None (methodology + portable shell/Python probes).


stepfun-tts - StepFun StepAudio 2.5 Contextual TTS

Install: claude plugin install daymade-audio@daymade-skills (suite-only — invoked as daymade-audio:stepfun-tts)

Generate Chinese / Japanese speech with stepaudio-2.5-tts. Captures the two non-obvious TTS pitfalls that cost hours otherwise: voice_label removal (replaced by natural-language instruction) and stricter 2.5-era censorship (死/消失/political terms).

When to use:

  • Chinese / Japanese TTS with emotional and prosody control (whisper, pause, stress, mid-sentence pivot)
  • Batch-generating game / app voice lines with per-line censorship_block fallback
  • Migration from step-tts-2 to stepaudio-2.5-tts (voice_label → instruction breaking change)
  • Hitting StepFun censorship blocks on previously-fine content

Key features:

  • stepaudio-2.5-tts with instruction (≤200 chars natural-language mood) + inline () prosody
  • Bundled tts_generate.py (with --batch ) and ab_compare.sh
  • API key resolution: $STEPFUN_API_KEY → ${CLAUDE_PLUGIN_DATA}/config.json fallback
  • Censorship rewrite playbook in references/migration_from_v2.md

Requirements: StepFun API key, "Normal" tier (https://platform.stepfun.com/). For ASR / transcription, use the sibling stepfun-asr skill below.


stepfun-asr - StepFun StepAudio 2.5 ASR (SSE Endpoint)

Install: claude plugin install daymade-audio@daymade-skills (suite-only — invoked as daymade-audio:stepfun-asr)

Transcribe Chinese / English audio with stepaudio-2.5-asr. Hides the #1 trap of the 2.5 ASR family: it does NOT live on /v1/audio/transcriptions — the wrong endpoint returns a misleading model stepaudio-2.5-asr not supported error that looks identical to a permission/whitelist failure.

When to use:

  • Long audio transcription (up to ~30 minutes single-call, 32K context, ~85-101× RTF — no client-side chunking)
  • Migration from step-asr / step-asr-1.1 (different endpoint, different body shape, SSE response)
  • Hitting the misleading model stepaudio-2.5-asr not supported error (= wrong endpoint, not permission)
  • Silent 4xx auth failures on audio endpoints (= using a "Plan" key instead of a "Normal" key)

Key features:

  • /v1/audio/asr/sse SSE streaming with base64 audio + nested JSON body (the script handles all four traps)
  • Bundled asr_transcribe.py — pure-stdlib CLI, auto-detects mp3/wav/ogg/opus/pcm by extension
  • Handles SSE error events (censorship can fire on ASR side too — rare but real)
  • API key resolution: $STEPFUN_API_KEY → ${CLAUDE_PLUGIN_DATA}/config.json fallback
  • Suggests transcript-fixer (ASR error correction) and meeting-minutes-taker (structured minutes) as natural downstream skills

Requirements: StepFun API key, "Normal" tier (https://platform.stepfun.com/). Plan keys cannot call audio endpoints.


auto-repo-setup - Automated Repository Setup & Environment Repair

Make a repository runnable and handoff-ready without guessing its stack or changing how collaborators normally work. The skill reads project authority first, repairs the verified gap, and treats startup instructions, lifecycle hooks, and Git mutation as different mechanisms with different safety boundaries.

When to use:

  • Someone says "跑不起来", "怎么启动", "环境怎么配", or "帮我设置代码库"
  • Setting up a new machine or creating a durable repository handoff
  • Adding routine startup sync for Claude Code/Codex without auto-stashing local work
  • Diagnosing repeated SessionStart output before changing hook configuration
  • Adding a lifecycle hook only when behavior must occur before the first prompt
  • Sanitizing git history after accidental secret/path leaks
  • Handling merge conflicts or git push failures with explicit safety gates

Key features:

  • Outcome router: separates environment repair, routine sync, handoff, hook diagnosis, and explicit pre-prompt automation
  • Stack-aware inventory: check_env.py infers only declared toolchains from manifests/lockfiles; it does not assume ffmpeg, uv, Python, or .env
  • Startup boundary: defaults stable behavior to AGENTS.md/CLAUDE.md or a normal Agent request; the Claude hook manager is guarded, dry-runnable, idempotent, and removable
  • Safety guardrails: Push Safety (visibility verification before any push), PII Guard (4-layer secret scanning), NO FALLBACK principle for env vars, Git Hook Bypass ban
  • Counter-review boundary: reserves multi-agent review for material shared-config/security/destructive changes, not ordinary setup checks
  • Bundled scripts: stack-aware inventory, guarded Claude startup-nudge manager, and read-only history candidate scan

Example usage:

# Install the skill
claude plugin install auto-repo-setup@daymade-skills

# Then ask Claude naturally
"我跑不起来这个仓库"
"帮我设置一下这个项目的环境"
"进入项目先同步远端;本地有改动不要自动 stash"
"为什么同一个 SessionStart 输出了三次?先查清来源"
"只有首条消息前必须注入动态提醒时,才帮我装 hook"
"git push 被拒了"

Requirements: The guidance itself has no runtime dependency. Bundled Python utilities require Python 3.10+; no external API key is required.


terminal-screenshot - See the Real Visual Result of Terminal Output

Render a terminal CLI program's colored output to a PNG so Claude can actually see the rendered result — color contrast, alignment, background blocks, highlighting — instead of only reading plain text and raw ANSI escape codes. Reading a hex value is guessing; seeing the rendered contrast on the real terminal background is verification.

When to use:

  • Right after changing any CLI color config (delta / bat / themes / lazygit pager) to visually confirm the result
  • Verifying git diff (delta) add/remove contrast, bat syntax highlighting, starship prompt, eza/ls colors, ripgrep matches
  • Any time you need to judge "does this color look right / is the contrast enough" instead of guessing from hex codes

Key features:

  • Capture-then-render discipline: captures full-fidelity ANSI in a normal shell first, then renders — never lets the renderer run complex CLIs (which degrade in a child pty and drop background blocks)
  • freeze-first, zero-dependency fallback: prefers charmbracelet/freeze for faithful rendering; falls back to a bundled stdlib ANSI→HTML converter + headless Chrome when freeze is unavailable
  • Real terminal background: renders on the actual terminal background color so dark themes are judged accurately
  • Per-CLI capture recipes: delta, git, bat, eza, ls, ripgrep, and a generic forced-color path
  • Bundled scripts: render_ansi.sh (freeze/Chrome auto-select), ansi2html.py (stdlib renderer)

Example usage:

# terminal-screenshot lives in the daymade-claude-code suite
claude plugin install daymade-claude-code@daymade-skills

# Then ask Claude naturally
"verify my delta diff colors"
"看一下这个终端配色的真实效果"
"is the add/remove contrast in git diff strong enough?"

Requirements: macOS. charmbracelet/freeze (preferred renderer) or Google Chrome (fallback). Python 3 for the fallback renderer.


pdf-to-html - Read a PDF as Faithful HTML (with Optional Translation)

Convert a PDF into one self-contained, readable HTML file that preserves images, charts and reading order — optionally translating it into another language while keeping every figure. A PDF is a layout, not just a text stream, so the workflow renders each page for you to see before building, and renders the HTML for visual verification before delivery.

When to use:

  • Reading a PDF as a clean web page or document (especially on a phone)
  • Turning a report or whitepaper PDF into styled HTML without losing its figures
  • Translating a PDF into another language while keeping its images, charts and tables in place

Key features:

  • Structured extraction (PyMuPDF): text blocks with font sizes + images, with decorative images (footer logos, rules) auto-detected and dropped
  • Data-driven build: heading levels inferred from font size, content images compressed and base64-inlined into one portable file
  • Optional parallel translation: a Dynamic Workflow translates pages concurrently, captions data charts, and reconciles terminology — with fidelity rules (never invent a translated name; copy numbers and proper nouns verbatim)
  • Mandatory visual verification: adaptive headless-Chrome screenshot sliced into readable segments (works around Chrome's ~16384px screenshot cap)
  • Bundled failure-cases reference: the real traps (verification, rendering limits, fidelity) so they are not re-discovered

Example usage:

# pdf-to-html lives in the daymade-docs suite
claude plugin install daymade-docs@daymade-skills

# Then ask Claude naturally
"把这个 PDF 转成中文网页版"
"make this report readable as HTML"
"translate this PDF to English but keep the charts"

Requirements: uv, Google Chrome or Chromium (visual verification). Python packages (PyMuPDF, Pillow, numpy) auto-install via uv run --with.


asr-transcribe-to-text - Audio/Video Transcription with Qwen3-ASR

Install: claude plugin install daymade-audio@daymade-skills (suite-only — invoked as daymade-audio:asr-transcribe-to-text)

Transcribe audio and video files to text using Qwen3-ASR via two interchangeable inference paths: local MLX on macOS Apple Silicon (no API key, 15-27x realtime) or a remote vLLM/OpenAI-compatible API for any platform. Auto-detects the platform and recommends the best path, persisting the choice in ${CLAUDE_PLUGIN_DATA}/config.json.

When to use:

  • Transcribing meeting recordings, lectures, interviews, podcasts, or screen recordings
  • Converting any audio/video file to text (speech-to-text)
  • Local, free transcription on an Apple Silicon Mac, or remote API when local is unavailable
  • The first stage of a transcribe → correct → minutes pipeline

Key features:

  • Dual inference paths — local MLX (15-27x realtime, free) and remote API, with automatic platform detection
  • Bundled transcribe_local_mlx.py loads the model once and processes files sequentially (no GPU contention)
  • Uses low-energy ~20-minute chunks with an 8192-token per-chunk bound, atomic checkpoints/resume, and full process-tree cleanup so one bad chunk cannot become an unbounded GPU job
  • Remote fallback overlap_merge_transcribe.py splits into 18-minute chunks with 2-minute overlap and fuzzy-merges
  • ffmpeg video→16kHz mono WAV extraction, truncation verification, and proxy-bypass handling
  • Proactively suggests transcript-fixer to clean ASR recognition errors on the output

Example usage:

# asr-transcribe-to-text lives in the daymade-audio suite
claude plugin install daymade-audio@daymade-skills

# Then ask Claude naturally
"transcribe this meeting recording to text"
"把这个录音转成文字"
"convert lecture.mp4 to a transcript"

Requirements: uv, ffmpeg/ffprobe. Local MLX path needs macOS Apple Silicon; remote path needs a reachable vLLM/OpenAI-compatible ASR endpoint. No API key for local mode.


marketplace-dev - Skills Repo → Plugin Marketplace

Install: claude plugin install daymade-claude-code@daymade-skills (suite-only — invoked as daymade-claude-code:marketplace-dev)

Create and maintain Claude Code plugin marketplaces: convert a repository, consolidate standalone skills into a new or existing suite, move skills between suites, validate real installation/cache boundaries, and ship the result through a PR.

When to use:

  • Making a skills repo installable via claude plugin install
  • Generating or fixing a marketplace.json (plugin distribution, one-click install, auto-update)
  • Adding a new plugin to an existing marketplace and bumping the right versions
  • Putting existing skills into a suite, moving a skill between suites, or making members suite-only
  • Debugging schema rejections like Unrecognized key: "$schema" or duplicate plugin names

Key features:

  • Evidence-intake phase that mines docs and local session history instead of guessing from a template
  • Encodes non-obvious schema rules: $schema is rejected, metadata has only 3 valid fields, strict: false semantics, single-skill vs suite source/skills patterns
  • Bundled check_marketplace.sh runs four checks (JSON syntax → claude plugin validate → source/skills resolution → reverse sync) and exits non-zero on failure
  • Installation, cache-footprint, and GitHub-install test recipes to confirm source produced the intended snapshot
  • Dedicated suite-consolidation workflow covering canonical moves, byte/mode preservation, repository-wide install/path drift, existing-user migration, isolated real installation, and immutable review
  • Two PostToolUse hooks (validate on marketplace.json edit; warn on un-bumped version when a SKILL.md changes) that auto-activate with the plugin

Example usage:

# marketplace-dev lives in the daymade-claude-code suite
claude plugin install daymade-claude-code@daymade-skills

# Then ask Claude naturally
"turn this skills repo into a plugin marketplace"
"generate a marketplace.json for this repo and validate it"
"add my new skill to the marketplace and open a PR"
"move these standalone skills into daymade-macos and make them suite-only"

Requirements: claude CLI (for claude plugin validate / install tests), jq. Git remotes configured if opening an upstream PR.


skill-creator - Create, Improve & Benchmark Skills

Install: claude plugin install daymade-skill@daymade-skills (suite-only — invoked as daymade-skill:skill-creator)

The essential meta-skill for building your own skills. It scales verification to the change: bounded fixes get targeted checks, narrow behavior changes get sampled replays, and broad/high-risk work becomes eligible for heavier evidence without automatically starting it. Paired baselines, graders, benchmarks, and viewers require explicit authorization or a decision-bearing evidence plan plus opt-in. It also supports explicit benchmarking and optimizes a skill's description for better triggering accuracy.

When to use:

  • Creating a skill from scratch, or editing/optimizing an existing one
  • Running evals to test a skill, or benchmarking performance with variance analysis
  • Improving a skill's description so Claude triggers it more reliably
  • Wrapping a third-party CLI tool you just got working into a reusable companion skill

Key features:

  • Prior-art research across the live conversation, explicitly approved prior history, local SOPs, installed plugins/MCPs, skills.sh, official plugins, npm/PyPI — to reuse infrastructure and encode only the user's unique methodology
  • The inline-vs-context: fork decision guide (subagents can't spawn subagents or call skills) and composable/orthogonal skill design
  • init_skill.py scaffolding, package_skill.py (auto-validates), and security_scan.py (gitleaks-based secret/PII detection)
  • Existing-skill migration gate: tool-attested snapshot or verified Git-commit baseline, runtime-reachability-aware capability audit, explicit dispositions, and package-time re-verification that a clean commit or hand-written marker cannot bypass
  • Risk-scaled verification router: Tier 1 targeted checks, Tier 2 sampled behavior replay, and Tier 3 broad/high-risk classification without automatic fan-out
  • Separately authorized full-eval harness: with-skill + baseline runs, assertions, grading, benchmark aggregation, and an HTML viewer after an explicit request, or after a decision-bearing evidence plan receives opt-in
  • Mandatory sanitization read-through for public skills — catches no-keyword leaks scanners miss
  • Description-optimization loop (60/40 train/test split, selects best description by held-out score)

Example usage:

# skill-creator lives in the daymade-skill suite
claude plugin install daymade-skill@daymade-skills

# Then ask Claude naturally
"create a skill that does X"
"improve this skill's description so it triggers more reliably"
"benchmark this skill against a no-skill baseline"

Requirements: Python 3, uv, PyYAML (validation/packaging), gitleaks (security scan). claude CLI only for agent evals and description-optimization runs.


feishu-doc-scraper - Feishu/Lark → Faithful Markdown + Source-First Archive

Extract Feishu (Lark) Docs, Wiki pages/collections, spreadsheets (including cell-attachment file download), and Minutes (妙记) transcripts into faithful local Markdown. The primary path uses the lark-cli API — it extracts the document body programmatically (no model paraphrasing), recursively follows a collection's reference graph, and reads permission boundaries from error codes; a browser-DOM path is the fallback only when lark-cli cannot reach the content.

When to use:

  • The source is a Feishu/Lark URL and fidelity matters (导出飞书文档/合集/妙记转写)
  • Converting a Feishu wiki/knowledge base to Markdown, or archiving a Feishu collection
  • Exporting a Feishu Minutes (妙记) transcript
  • Converting an owner-exported .docx into faithful Markdown with heading/highlight restoration

Key features:

  • Document comments and complete reply threads accompany the body, with quoted passages, source positions, author IDs, timestamps, solved scope, and explicit coverage gaps
  • lark-cli API extraction writes the body to disk via jq (never retyped by the model — the single most important fidelity rule)
  • Recursive reference-graph traversal (BFS) with feishu_extract_refs.py, plus a residual rich-media-tag acceptance gate so no referenced doc is silently missed
  • Native Minutes transcript export (never re-runs ASR on downloaded media)
  • Permission-denied path: owner-exported .docx → Markdown with font-size→heading and w:shd→highlight restoration, then visual verification
  • Source-first artifact manifest + fail-closed validator: structured/searchable derivatives go to Git, raw binaries remain on Feishu or an explicitly chosen object store, and local downloads stay optional caches instead of Git LFS payloads
  • LARK_CLI_NO_PROXY=1 discipline for *.feishu.cn (avoids credential leak/DNS hijack) and a U+FFFD encoding-corruption final check
  • Works with both Feishu (feishu.cn) and Lark (larkoffice.com)

Example usage:

# Install the skill
claude plugin install feishu-doc-scraper@daymade-skills

# Then ask Claude naturally
"把这个飞书合集导出成 markdown"
"export this Feishu Minutes transcript"
"save this Lark wiki page as Markdown"

Requirements: lark-cli binary (npm @larksuite/cli) authenticated to the target tenant; `j