Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
clean-branches
Clean up git branches by analyzing merged/unmerged status, archiving completed work,
and organizing active branches. This skill should be used when the user wants to clean
up branches, organize their git repository, or review branch status.
Triggered by "/clean-branches", "/branches", "clean branches", "check branches", "check branch", or "branches".
majiayu000/claude-skill-registry 163
-
scala-conventions-enforcer
This skill should be used proactively before writing any Scala code for the first time in a session. It ensures all Scala code adheres to project-specific coding standards, formatting rules, naming conventions, and architectural patterns defined in the comprehensive style guide. Trigger this skill when about to write Scala classes, traits, objects, or modify existing Scala files.
majiayu000/claude-skill-registry 163
-
agent-o-rama
Layer 4 Learning and Pattern Extraction for Cognitive Surrogate Systems
majiayu000/claude-skill-registry 163
-
check-service-status
서비스 상태 확인. Use when (1) "현황 알려줘", (2) "서비스 상태 확인",
(3) "cm-* 상태 체크". GitHub 레포 상태 및 최근 배포 정보 조회.
majiayu000/claude-skill-registry 163
-
format-processor
majiayu000/claude-skill-registry 163
-
skill-creation-guide
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
majiayu000/claude-skill-registry 163
-
glsl-shader
Create audio-reactive GLSL visualizers for Bice-Box. Provides templates, audio uniforms (iRMSOutput, iRMSInput, iAudioTexture), coordinate patterns, and common shader functions.
majiayu000/claude-skill-registry 163
-
fix-line-endings
majiayu000/claude-skill-registry 163
-
openrouter-streaming-setup
Implement streaming responses with OpenRouter. Use when building real-time chat interfaces or reducing time-to-first-token. Trigger with phrases like 'openrouter streaming', 'openrouter sse', 'stream response', 'real-time openrouter'.
majiayu000/claude-skill-registry 163
-
playwright-browser-file-upload
To upload files through a file input, provide one or more file paths for a page file chooser.
majiayu000/claude-skill-registry 163
-
feasibility-analysis
Technical, economic, operational, and schedule feasibility evaluation for proposed initiatives
majiayu000/claude-skill-registry 163
-
fundamental-coding-principles
Apply SOLID, DRY, KISS, YAGNI, and SSOT principles when writing, reviewing, or refactoring code to ensure maintainability and quality.
majiayu000/claude-skill-registry 163
-
detect-empty-catch
Detect empty catch blocks and exception swallowing anti-patterns. Finds catch blocks that silently ignore errors without logging or rethrowing. Works across all languages. Use when user asks about error handling issues.
majiayu000/claude-skill-registry 163
-
conda-multi-account-hipergator
Set up conda with multiple group storage locations on HiPerGator
majiayu000/claude-skill-registry 163
-
github-issue-workflow
Issue-first GitHub development workflow. Use when working on any GitHub repository task, feature, or bug fix. Enforces a disciplined workflow that starts with a GitHub issue, creates a linked feature branch, iterates until validated, then cleans up. Triggers on requests to fix bugs, add features, refactor code, or any development work in a git repository.
majiayu000/claude-skill-registry 163
-
go-kubernetes
Kubernetes operators and client-go development
majiayu000/claude-skill-registry 163
-
cc-devflow-orchestrator
CC-DevFlow workflow router and agent recommender. Use when starting requirements, running flow commands, or asking about devflow processes.
majiayu000/claude-skill-registry 163
-
unknown-majiayu000-claude-skill-registr-2
majiayu000/claude-skill-registry 163
-
coderabbit-request
Use after completing file changes - strongest for source code (AST-aware linting, security, tests), lighter support for markdown/config. Dispatches CodeRabbit reviewer subagent. ALWAYS request review before considering work complete.
majiayu000/claude-skill-registry 163
-
webhook-development
Implement webhook systems for event-driven integration with retry logic, signature verification, and delivery guarantees. Use when creating event notification systems, integrating with external services, or building event-driven architectures.
majiayu000/claude-skill-registry 163
-
openrouter-rate-limits
Handle OpenRouter rate limits with proper backoff strategies. Use when experiencing 429 errors or building high-throughput systems. Trigger with phrases like 'openrouter rate limit', 'openrouter 429', 'openrouter throttle', 'openrouter backoff'.
majiayu000/claude-skill-registry 163
-
block-collection-and-party
The Block Collection and Block Party are repositories for existing AEM blocks, build tools, code snippets, integration patterns, plugins, and more. Use this skill anytime you are developing something and want to find a reference to use as a starting point.
majiayu000/claude-skill-registry 163
-
packmol
This skill should be used when the user asks to "create a packmol input", "pack molecules with packmol", "solvate a protein", "build an initial configuration", "setup molecular dynamics", or discusses molecular packing, solvation, or building simulation starting structures.
majiayu000/claude-skill-registry 163
-
ghe-status
READ-ONLY quick overview of GitHub Elements workflow state. Shows active threads, phase distribution, and workflow health at a glance.
USE THIS SKILL WHEN:
- User asks "what's the status" or "show me the status"
- User asks "what threads are active" or "what am I working on"
- User asks "show me the workflow state" or "what's happening"
- User wants a quick overview before starting work
- Starting a session and need context
DO NOT USE THIS SKILL WHEN:
- User wants to CLAIM an issue (use ghe-claim)
- User wants to POST a checkpoint (use ghe-checkpoint)
- User wants to TRANSITION phases (use ghe-transition)
- User wants DETAILED metrics/health reports (use ghe-report)
EXAMPLES:
<example>
Context: User starting a session wants to see current state
user: "What's the github elements status?"
assistant: "I'll use ghe-status to show you the current workflow state"
</example>
<example>
Context: User wants to know what work is available
user: "Show me what threads are active"
assistant: "I'll use ghe-status to display active and available threads"
</example>
<example>
Context: Quick check before doing work
user: "What am I currently working on?"
assistant: "I'll use ghe-status to find your in-progress threads"
</example>
majiayu000/claude-skill-registry 163