claude-code-skills

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

### 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

Install bundles

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

🎬 Live Demo

Coming soon

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

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

44. 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:

Core Workflow

Copy this checklist and track progress:

Meeting Minutes Progress:
- [ ] Step 0 (Optional): Pre-process transcript with transcript-fixer
- [ ] Step 1: Read and analyze transcript
- [ ] Step 1.5: Speaker identification (if transcript has "Speaker 1/2/3")
  - [ ] Analyze speaker features (word count, style, topic focus)
  - [ ] Match against context.md team directory (if provided)
  - [ ] Present speaker mapping to user for confirmation
- [ ] Step 1.6: Generate intelligent filename, confirm with user
- [ ] Step 1.7: Quality assessment (optional, affects processing depth)
- [ ] Step 2: Multi-turn generation (PARALLEL subagents with Task tool)
  - [ ] Create transcript-specific dir: <output_dir>/intermediate/<transcript-name>/
  - [ ] Launch 3 Task subagents IN PARALLEL (single message, 3 Task tool calls)
    - [ ] Subagent 1 → <output_dir>/intermediate/<transcript-name>/version1.md
    - [ ] Subagent 2 → <output_dir>/intermediate/<transcript-name>/version2.md
    - [ ] Subagent 3 → <output_dir>/intermediate/<transcript-name>/version3.md
  - [ ] Merge: UNION all versions, AGGRESSIVELY include ALL diagrams → draft_minutes.md
  - [ ] Final: Compare draft against transcript, add omissions
- [ ] Step 3: Self-review for completeness
- [ ] Step 4: Present draft to user for human review
- [ ] Step 5: Cross-AI comparison (if human provides external AI output)
- [ ] Step 6: Iterate on human feedback (expect multiple rounds)
- [ ] Step 7: Human approves final version

Note: <output_dir> = directory where final meeting minutes will be saved (e.g., project-docs/meeting-minutes/)

Key Rules

• Never assume - Ask user to confirm if unclear
• Quote controversial decisions verbatim
• Assign action items to specific people, not teams
• Preserve numerical values (ranges, counts, priorities)
• Always use multiple passes - Single turn is guaranteed to lose content
• Normalize equivalent terminology - Treat trivial variations (e.g., "backend architecture" vs "backend", "API endpoint" vs "endpoint") as equivalent; do NOT point out or highlight such differences between speakers
• Single source of truth - Place each piece of information in ONE location only; avoid duplicating tables, lists, or summaries across sections (e.g., API list belongs in Discussion OR Reference, not both)

1. Install markitdown (one-time)

uv tool install "markitdown[pdf]"

When to Use Diagrams:

• Data flow discussions → Sequence diagram
• Database schema discussions → ER diagram
• Process/workflow decisions → Flowchart
• State machine discussions → State diagram
• System architecture → Component diagram

Example: Version Switching (Workflow Diagram)

sequenceDiagram
    participant User
    participant System
    Note over System: Current: V2 Active
    User->>System: Create V3 (inactive)
    User->>System: Set V2 inactive
    User->>System: Set V3 active
    Note over System: New: V3 Active