feature-smoke-test
针对 Kimi Code CLI 的新增或变更功能，规划并执行可重复的端到端冒烟测试。从 git diff 推断功能边界，读取相关文档和代码，设计测试 prompt，以 --print 非交互模式运行本地 CLI，检查进程退出码和 session 产物，总结预期与实际行为之间的差异。发现问题时自动启动多路并行探查以定位根因。
worktree-status
Audit all git worktrees in the current project. Use when the user asks about worktree status, which branches are merged, which have uncommitted changes, or which worktrees can be safely cleaned up.
sample-plugin
Sample plugin demonstrating the Skills + Tools model. Includes a Python tool (greeting) and a TypeScript tool (calculator).
codex-worker
Spawn and manage multiple Codex CLI agents via tmux to work on tasks in parallel. Use whenever a task can be decomposed into independent subtasks (e.g. batch triage, parallel fixes, multi-file refactors). When codex and tmux are available, prefer this over the built-in Task tool for parallelism.
ui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
grow-sustainably
Evaluate business decisions through the lens of sustainable, profitable growth. Use when someone is making decisions about spending, hiring, fundraising, or scaling their business.
github-pr-inline-reply
Reply to inline PR review comments on GitHub pull requests using the GitHub API. Use this skill when you need to respond to individual review comments on a PR, acknowledge feedback, or mark comments as resolved by posting direct replies to comment threads.
playwright-testing
Guide for writing, updating, and maintaining Playwright end-to-end tests for Podman Desktop using the project's Electron runner, custom fixtures, and Page Object Model hierarchy. Use when creating new E2E spec files, building or modifying page objects, updating the test framework or utilities, debugging test failures, adding smoke tests, or when the user asks about Playwright tests, test automation, spec files, page models, or the E2E test structure.
investigate-gh-run
Deep investigation of CI/CD test failures - identifies root causes by analyzing logs, artifacts, git history, and source code
playwright-trace-analysis
Analyzes Playwright trace archives (`trace.zip`) to diagnose test failures, flaky behavior, and unexpected UI states using trace steps, console output, network activity, and screenshots. Use when the user provides a trace path or trace artifact, asks why a Playwright or E2E test failed, wants root-cause analysis from CI artifacts, mentions the trace viewer, or asks whether a failure is flaky or an application bug.
