Topic: claude-code
35,830 skills in this topic.
-
ask
Send via ask, end turn immediately; use when user explicitly delegates to any AI provider (gemini/codex/opencode/droid); NOT for questions about the providers themselves.
bfly123/claude_code_bridge 2,033
-
mounted
Report which CCB providers are mounted (session exists AND daemon is online). Outputs JSON.
bfly123/claude_code_bridge 2,033
-
pend
View latest reply from AI provider (gemini/codex/opencode/droid/claude).
bfly123/claude_code_bridge 2,033
-
ping
Test connectivity with AI provider (gemini/codex/opencode/droid/claude).
bfly123/claude_code_bridge 2,033
-
lesson-quiz
Interactive lesson-level quiz for Claude Code tutorials. Tests understanding of a specific lesson (01-10) with 8-10 questions mixing conceptual and practical knowledge. Use before a lesson to pre-test, during to check progress, or after to verify mastery. Use when asked to "quiz me on hooks", "test my knowledge of lesson 3", "lesson quiz", "practice quiz for MCP", or "do I understand skills".
luongnv89/claude-howto 16,343
-
self-assessment
Comprehensive Claude Code self-assessment and learning path advisor. Runs a multi-category quiz covering 10 feature areas, produces a detailed skill profile with per-topic scores, identifies specific gaps, and generates a personalized learning path with prioritized next steps. Use when asked to "assess my level", "take the quiz", "find my level", "where should I start", "what should I learn next", "check my skills", "skill check", or "level up".
luongnv89/claude-howto 16,343
-
blog-draft
Draft a blog post from ideas and resources. Use when users want to write a blog post, create content from research, or draft articles. Guides through research, brainstorming, outlining, and iterative drafting with version control.
luongnv89/claude-howto 16,343
-
brand-voice-consistency
Ensure all communication matches brand voice and tone guidelines. Use when creating marketing copy, customer communications, public-facing content, or when users mention brand voice, tone, or writing style.
luongnv89/claude-howto 16,343
-
claude-md
Create or update CLAUDE.md files following best practices for optimal AI agent onboarding
luongnv89/claude-howto 16,343
-
code-review-specialist
Comprehensive code review with security, performance, and quality analysis. Use when users ask to review code, analyze code quality, evaluate pull requests, or mention code review, security analysis, or performance optimization.
luongnv89/claude-howto 16,343
-
api-documentation-generator
Generate comprehensive, accurate API documentation from source code. Use when creating or updating API documentation, generating OpenAPI specs, or when users mention API docs, endpoints, or documentation.
luongnv89/claude-howto 16,343
-
code-refactor
Systematic code refactoring based on Martin Fowler's methodology. Use when users ask to refactor code, improve code structure, reduce technical debt, clean up legacy code, eliminate code smells, or improve code maintainability. This skill guides through a phased approach with research, planning, and safe incremental implementation.
luongnv89/claude-howto 16,343
-
clone
Clone the current conversation so the user can branch off and try a different approach.
ykdojo/claude-code-tips 7,060
-
gha
Analyze GitHub Actions failures and identify root causes
ykdojo/claude-code-tips 7,060
-
half-clone
Clone the later half of the current conversation, discarding earlier context to reduce token usage while preserving recent work.
ykdojo/claude-code-tips 7,060
-
handoff
Write or update a handoff document so the next agent with fresh context can continue this work.
ykdojo/claude-code-tips 7,060
-
reddit-fetch
Fetch content from Reddit using Gemini CLI or curl JSON API fallback. Use when accessing Reddit URLs, researching topics on Reddit, or when Reddit returns 403/blocked errors.
ykdojo/claude-code-tips 7,060
-
review-claudemd
Review recent conversations to find improvements for CLAUDE.md files.
ykdojo/claude-code-tips 7,060
-
debug
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures, ensuring root-cause understanding before implementation
udecode/dotai 1,141
-
dig
Look up documentation and source code for libraries and packages. Use when the user asks a question about a library, needs to understand a library's API, or when you need information about a library that you don't know about. Triggers on questions like "How do I use X library?", "What's the API for Y?", "Show me how Z library handles this", or when encountering unfamiliar library usage.
udecode/dotai 1,141
-
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
udecode/dotai 1,141
-
changelog
Use when updating CHANGELOG.md. Enforces consistent formatting with bolded item names, dash separators, and specific section ordering.
udecode/dotai 1,141
-
analyze-ci
Analyze failed GitHub Action jobs for a pull request.
EYH0602/skillshub 4
-
docs-review
Review documentation changes for compliance with the Metabase writing style guide. Use when reviewing pull requests, files, or diffs containing documentation markdown files.
EYH0602/skillshub 4