Loading...
Loading...
Found 2,963 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.
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".
Shepherd a GitHub pull request all the way to merge-ready by relentlessly polling status and only acting once all automatic reviewers have finished. NEVER merges without explicit human approval. Use when the user says things like "shepherd this PR", "babysit this PR", "get this PR merge-ready", "wait for Cubic", "wait for Bugbot", or asks to drive a PR through review.
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.
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
This skill should be used when the user asks to "track issues", "create beads issue", "show blockers", "what's ready to work on", "beads routing", "prefix routing", "cross-rig beads", "BEADS_DIR", "two-level beads", "town vs rig beads", "slingable beads", or needs guidance on git-based issue tracking with the bd CLI.
Complete CI/CD guide for Capacitor apps covering GitHub Actions, GitLab CI, build automation, app signing, and deployment pipelines. Use this skill when users need to automate their build and release process.
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
This skill should be used when parallelizing multi-issue sprints using git worktrees and parallel Claude agents. Use when tackling multiple GitHub issues simultaneously, when the user mentions "blitz", "parallel sprint", "worktree workflow", or when handling 3+ independent issues that could be worked on concurrently. Orchestrates the full workflow from issue triage through parallel agent delegation to sequential merge.
Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.