Loading...
Loading...
Found 4,153 Skills
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
Install a rich Claude Code statusline into ~/.claude/hooks/ and ~/.claude/settings.json. Displays model, git context, token usage, effort level, 5h/7d usage limits, and active /loop count with next-fire time.
Use jj (Jujutsu) for local version control instead of git. Activate when: the repo has a .jj/ directory, the user or project config mentions jj, the user says 'use jj', or any version control operation is needed in a jj-managed repo. Also use this skill when the user asks to commit, branch, stash, rebase, or perform any git-like operation in a repo that uses jj. If unsure whether the repo uses jj, check for a .jj/ directory.
Restore session state from handoff artifacts and route to the next action. Priority cascade: HANDOFF.json (highest) > .continue-here.md > incomplete task_plan.md > git log. Presents a status dashboard, then executes the next action. Use for "resume", "continue", "pick up where I left off", "what was I doing", "continue work". Do NOT use for starting new tasks (use /do), reviewing past sessions (use /retro), or reading task plans (read task_plan.md directly).
Quick situational awareness for the current git branch. Summarizes what a feature branch is about by analyzing commits and changes against trunk. On trunk, highlights recent interesting activity. Use when user says "wtf", "what's going on", "what is this branch", "what changed", or "catch me up".
Analyze a GitHub issue, reproduce the bug, and produce a structured issue analysis artifact.
Turn git commits and diffs since an exact start date into a copy-pastable, non-technical client report grouped by feature. Use when the user wants a client update, accomplishment summary, weekly progress note, stakeholder recap, or high-level status report based on git history. Trigger on: client report from commits, summarize git diff since a date, weekly update from git log, non-technical accomplishments, stakeholder-ready changelog. Do NOT trigger for technical release notes, code review, or any request where the date is still ambiguous.
Interactive workflow to create Commerce B2B Stores and retrieve storefront metadata. Use when users want to: create B2B Commerce stores, build Commerce storefronts, set up B2B stores from Vibes, retrieve Commerce metadata, deploy Commerce experiences, work with DigitalExperienceBundle for Commerce.
This skill should be used when the user says "commit my changes", "commit this", "create a commit", "git commit", "save my work", or mentions committing code.
AI Radar Skill — Zero-API, Zero-Key, Zero-Server Chinese AI News Query. Data comes from public static JSON files hosted on GitHub Pages by AI News Radar (automatically updated daily via GitHub Actions). You can retrieve data with curl, no authentication, no UA requirements, no rate limits, and you can fork the entire data pipeline to create your own version. This Skill should be triggered when users ask any Chinese AI news-related questions such as "What's happening in the AI circle today?", "AI news in the past 24 hours", "AI daily briefing", "Any recent large model releases?", "AI product updates", "What's new in Agent tools?", "What have OpenAI/Anthropic/Google released recently?", "Hot topics in the AI circle", "Check AI Radar", "Which AI news sources are worth following?", etc. Even if users only say "AI circle", "AI news", or "What's new today", as long as the context is in the AI / large model / Agent / developer tools domain, this Skill should be triggered. **Do NOT undertrigger** — if users ask for AI news and you don't invoke this Skill, you're treating outdated training data as today's news, which is harmful to users. Do NOT use this Skill for maintaining the AI News Radar repository itself (adding news sources, modifying crawling logic, deploying Pages — use Bole Skill / ai-news-radar for that); do NOT use it for non-AI general news queries; do NOT use it for private information sources that require login status.
Search and discover Claude Code skills and MCP servers from marketplaces, GitHub repositories, and registries. Use when (1) user asks to find skills for a specific task, (2) looking for MCP servers to connect external tools, (3) user mentions "find skill", "search MCP", "discover tools", or "what skills exist for X", (4) before creating a custom skill to check if one already exists.
Claude Code Bash tool patterns with hooks, automation, git workflows. Use for PreToolUse hooks, command chaining, CLI orchestration, custom commands, or encountering bash permissions, command failures, security guards, hook configurations.