浏览和安装 Killer-Skills 目录中的数千个 AI Agent 技能。支持 Claude Code、Windsurf、Cursor 等。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claudes capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claudes capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claudes capabilities with specialized knowledge, workflows, or tool integrations.
Full pre-merge workflow for a GitHub issue — rebase, /verify, acceptance criteria audit, /code-review, /create-pr, and post-merge cleanup. Run after /human-test passes. Triggers on ready to merge, prepare the PR, merge this, or finalize #N.
End-to-end workflow for HookCode preview DOM highlighting check/start/stop previews, install dependencies, send highlight commands, and verify preview bridge readiness via PAT-authenticated APIs. Use when debugging cross-origin preview iframes, validating bridge integration, or scripting highlight requests against task-group previews.
Database, API, and integration conventions for Red Cliff Record. Use when working with Drizzle ORM, tRPC routers, database migrations, integration syncs, or media alt-text workflows in this project. Triggers on database queries, API routes, Drizzle v2, tRPC, Zod validation, integration work, or `rcr media` commands.
Create single-file commands with dynamic content injection (@path and !command). Use when building commands that need filesystem access, git state, runtime context, or argument handling with $1 placeholders. Includes @file injection, !shell execution, <injected_content> wrappers, and single-file structure patterns. Not for skills (use skill-development) or audit workflows.
Follow project structure standards, environment variable management, Content Collections setup, version control practices, and build/deployment conventions. Use this skill when setting up project structure, managing configuration files, organizing dependencies, or establishing development workflows. When working on project directory structure and organization, environment variable files (.env, .env.local, .env.production), Content Collections configuration (src/content/config.ts), package.json and dependency management, git commit messages and branching strategy, configuration files (astro.config.mjs, tsconfig.json), build and deployment setups, or documentation files (README.md, ADRs).
Sets up RabbitMQ event publishers and consumers following ModuleImplementationGuide.md Section 9. RabbitMQ only (no Azure Service Bus). Creates publishers with DomainEvent (tenantId only; no organizationId), consumers with handlers, naming {domain}.{entity}.{action}, required fields (id, type, version, timestamp, tenantId, source, data). Use when adding event-driven communication, async workflows, or integrating via events.
Convert a ticket markdown file from tickets/ into a GitHub Issue, preserving all content and metadata. Accepts bare number (0039a), full name (0039a_energy_tracking_diagnostic_infrastructure), or with .md extension. Creates labels, resolves cross-references, updates parent issues, and closes completed tickets. For work tickets, creates workflow phase sub-issues (Design, Math, Prototype, Implementation). For investigation/debug tickets, creates debug phase sub-issues (Investigate, Diagnose, Fix, Verify).
Scaffold production-ready FastAPI endpoints for any client workflow. Use this skill ANY TIME the user wants to create a new API, add an endpoint, build a server, set up a webhook receiver, or start a new Python backend project. Also use when they mention FastAPI, uvicorn, REST API, route, endpoint, or say things like I need something that listens for requests or how do I expose this as an API. Use even when the request isnt explicitly about QuickBooks or ShipStation — this skill covers all FastAPI scaffolding for the 5 Cypress tech stack.
Portable tmux-based workflow to drive one or multiple long-running Codex CLI “workers” from another process (e.g. Claude CLI) by (1) starting/reusing a tmux session running `codex`, (2) injecting prompts into the Codex pane via `tmux send-keys`/buffer paste, and (3) polling the worker’s Codex JSONL session logs to extract the next assistant reply. Each worker runs with an isolated `CODEX_HOME` (default `~/.codex-workers/<worker_id>`) to prevent log cross-talk when multiple Codex workers run concurrently. Use when you need to submit/wait/read Codex replies in tmux, manage multiple Codex workers, or troubleshoot the tmux worker and log binding.