find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
gh-stack
|
cosense-memo
Claudeとの会話内容や記事の要約をCosense形式のメモに変換する。箇条書き・だである調・internal linkを用いた知識ネットワーク向けフォーマット。「Cosenseにメモして」「この内容をCosense形式で」「学んだことをまとめて」などのリクエストで使用。Cosenseは旧称ScrapboxのためユーザーがScrapboxと言ったときもこのスキルを使ってください。
gog
Google Workspace操作（Gmail, Calendar, Drive, Docs, Sheets, Chat, Tasks, Contacts）。ユーザーが「メール確認して」「予定を見せて」「ドライブで検索」「ドキュメント作成」「スプレッドシート読んで」「タスク追加」「連絡先検索」などと言ったときに使用。gog CLIを利用してGoogle Workspaceの各サービスを操作する。
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
writing-python
Idiomatic Python 3.14+ development. Use when writing Python code, CLI tools, scripts, or services. Emphasizes stdlib, type hints, uv/ruff toolchain, and minimal dependencies.
vendure
Assiste au développement avec le framework e-commerce Vendure pour Node.js. Gère le commerce headless, les APIs GraphQL, la gestion des commandes, les catalogues produits, l'intégration des paiements et le développement TypeScript e-commerce. Utiliser lors du travail sur des projets Vendure, la création de plugins, ou l'intégration de storefronts.
refactoring
[Code Quality] Use when you need restructure code without changing behavior using extract method, extract class, rename, move, and inline patterns.
plan-review
[Planning] Use when you need to auto-review a plan for validity, correctness, and best practices — recursive: review, validate findings with why-review, fix validated findings, full re-review until no findings.
plan-analysis
[Planning] Use when the user provides an implementation plan file and asks to analyze it, assess impact, update specifications, or verify planned changes.
pdf-to-markdown
[Document Processing] Use when you need to convert PDF files to Markdown with support for native text PDFs and scanned documents (OCR).
package-upgrade
[Code Quality] Use when the user asks to analyze package upgrades, check for outdated dependencies, plan npm/NuGet updates, or assess breaking changes in package updates.
memory-management
[Utilities] Use when saving or recovering task progress across sessions via file checkpoints — especially before context compaction.
markdown-to-pdf
[Document Processing] Use when you need to convert markdown files to PDF with syntax highlighting and custom CSS support.
markdown-to-docx
[Document Processing] Use when you need to convert markdown files to Microsoft Word ( DOCX) format with GFM support and math rendering.
research
[Planning] Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
release-notes
[Git] Use when creating release notes from git history.
plan-validate
[Planning] Use when you need to validate a plan with critical questions interview.
checkpoint
[Utilities] Use when you need to save analysis context to a checkpoint file for recovery (user-facing alias for memory-management Part 1 CHECKPOINT_CREATE).
ck-help
[Utilities] Use when you need claudeKit usage guide - just type naturally.
claude-code
[Utilities] Use when you need Claude Code CLI setup, configuration, troubleshooting, and feature guidance.
problem-solving
[Utilities] Use when applying structured problem-solving frameworks to complex, blocked, recurring, or uncertain decisions.
pr
[Git] Use when you need to create pull request with standard format.
product-owner
[Project Management] Use when you need to capture ideas, manage product backlogs, apply prioritization frameworks (RICE, MoSCoW), and facilitate stakeholder communication.
recover
[Utilities] Use when you need to restore workflow context from checkpoint after session loss.
project-manager
[Project Management] Use when you need to generate project status reports, track dependencies, manage risk registers, and facilitate team sync meetings.
plan
[Planning] Use when you need intelligent plan creation with prompt enhancement. Flag: --mode={ci|cro} (default none — standard planning); --mode=ci plans a fix from a GitHub Actions CI run/log, --mode=cro plans conversion-rate optimization (25-item CRO framework).
code-review
[Code Quality] Use when evaluating review feedback, requesting targeted code-quality review, or verifying completion claims.
code-simplifier
[Code Quality] Use when you need to simplify and refine code for clarity, consistency, and maintainability while preserving all functionality.
coding-level
[Utilities] Use when you need to set coding experience level for tailored explanations.
worktree
[Git] Use when you need to create isolated git worktree for parallel development.
commit
[Git] Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Flag: --push (a.k.a. "commit and push") stages + commits + pushes to remote in one shot.
compact
[Utilities] Use when you need to compress context to optimize token usage (user-facing alias for context-optimization Strategy #3 Compress).
context-optimization
[Utilities] Use when managing context window usage, compressing long sessions, or optimizing token usage.
context
[Utilities] Use when you need to load project context for current session.
learn
[Utilities] Use when you need to teach Claude lessons that persist across sessions.
lint
[Code Quality] Use when you need to run linters and fix issues for backend or frontend.
brainstorm
[Content] Use when you need to brainstorm as a PO/BA — structured ideation for problem-solving, new product creation, or feature enhancement.
business-analyst
[Project Management] Use when creating user stories, writing acceptance criteria, analyzing requirements, or mapping business processes.
ask
[Utilities] Use when you need to answer technical and architectural questions.
branch-comparison
[Git] Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed.
figma-design
[Frontend] Use when you need to extract design context from Figma URLs via MCP, REST API, or screenshot fallback.
documentation
[Code Quality] Use when the user asks to enhance documentation, add code comments, create API docs, improve technical documentation, document code, or update README files.
docx-to-markdown
[Document Processing] Use when you need to convert Microsoft Word ( DOCX) files to Markdown with GFM support (tables, images, code blocks).
watzup
[Utilities] Use when you need to review recent changes and wrap up the work.
ui-ux-pro-max
[Frontend] Use when designing beautiful or aesthetic interfaces with curated UI styles, palettes, fonts, charts, and stacks.
test
[Testing] Use when you need to run tests locally and analyze the summary report.
test-ui
[Testing] Use when you need full-site QA audit (accessibility, performance, security, SEO) with visual reports.
fix
[Implementation] Use when you need to analyze and fix issues [INTELLIGENT ROUTING]. Flag: --target={ci|issue|logs|test|types|ui} scopes the fix; --target=types resolves TypeScript errors inline.
Page 1204 of 1717 · 85837 results
