reviewing-pull-requests
Pull request workflow and review expertise. Auto-invokes when PRs, code review, merge, or pull request operations are mentioned. Integrates with self-improvement plugin for quality validation.
managing-branches
Git branching strategy expertise with flow-aware automation. Auto-invokes when branching strategies (gitflow, github flow, trunk-based), branch creation, branch naming, merging workflows, release branches, hotfixes, environment branches, or worktrees are mentioned. Integrates with existing commit, issue, and PR workflows.
managing-commits
Git commit quality and conventional commits expertise with automatic issue tracking integration. Auto-invokes when the user explicitly asks about commit message format, commit quality, conventional commits, commit history analysis, issue references in commits, or requests help writing commit messages. Integrates with the issue cache for automatic issue references.
managing-projects
GitHub Projects v2 expertise for creating and managing project boards, fields, views, and items. Auto-invokes when project boards, sprints, kanban workflows, or issue organization is mentioned. Uses GraphQL for advanced project operations.
managing-relationships
Expert at managing GitHub issue relationships including parent/sub-issues, blocking dependencies, and tracking links using the GraphQL API. Auto-invokes when creating issue hierarchies, setting parent-child relationships, managing dependencies, or linking related issues.
managing-worktrees
Git worktree management expertise for parallel development. Auto-invokes when worktrees, parallel development, multiple branches simultaneously, or isolated development environments are mentioned. Handles worktree creation, listing, and cleanup.
Skill Development
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Plugin Structure
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.
Plugin Settings
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
MCP Integration
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
Hook Development
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
Command Development
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
suggesting-improvements
Expert at suggesting specific, actionable improvements to Claude's responses and work. Use when Claude's output needs enhancement, when quality issues are identified, or when iterating on solutions.
improving-components
Expert at automatically applying improvements to Claude Code components based on quality analysis. Enhances descriptions, optimizes tool permissions, strengthens security, and improves usability. Works in conjunction with analyzing-component-quality skill.
creating-feedback-loops
Expert at creating continuous improvement feedback loops for Claude's responses. Use when establishing self-improvement processes, tracking progress over time, or implementing iterative refinement workflows.
analyzing-response-quality
Expert at analyzing the quality of Claude's responses and outputs. Use when evaluating response completeness, accuracy, clarity, or effectiveness. Auto-invokes during self-reflection or when quality assessment is needed.
analyzing-component-quality
Expert at analyzing the quality and effectiveness of Claude Code components (agents, skills, commands, hooks). Assumes component is already technically valid. Evaluates description clarity, tool permissions, auto-invoke triggers, security, and usability to provide quality scores and improvement suggestions.
researching-best-practices
Automatically activated when user asks "what's the best way to...", "how should I...", "what are best practices for...", or requests recommendations, industry standards, or proven approaches for implementing features
investigating-codebases
Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y work?", or "explain the Z component"
analyzing-patterns
Automatically activated when user asks to "find patterns in...", "identify repeated code...", "analyze the architecture...", "what design patterns are used...", or needs to understand code organization, recurring structures, or architectural decisions
planning-sprints
Automatically activated when user mentions sprint planning, backlog refinement, iteration planning, sprint goals, capacity planning, velocity tracking, or asks to plan/start/close a sprint. Provides comprehensive sprint planning expertise using agile best practices.
coordinating-projects
Automatically activated when user mentions multi-project coordination, cross-project dependencies, portfolio management, roadmap planning, resource allocation across projects, or asks to coordinate/manage multiple projects simultaneously. Provides strategic project coordination expertise.
triaging-issues
GitHub issue triage and management expertise. Auto-invokes when issue triage, duplicate detection, issue relationships, or issue management are mentioned. Integrates with existing github-issues skill.
organizing-with-labels
GitHub label and milestone management expertise. Auto-invokes when labels, milestones, taxonomies, issue organization, sprint planning, or phase tracking are mentioned. Handles label CRUD, bulk operations, milestone creation/tracking/progress, and issue grouping for releases and sprints.
building-logseq-plugins
>
building-hooks
Expert at creating Claude Code event hooks for automation and policy enforcement. Auto-invokes when creating/updating hooks, modifying hooks.json, designing event-driven automation, or writing hook configurations.
building-commands
Expert at creating and modifying Claude Code slash commands. Auto-invokes when creating/updating commands, modifying command frontmatter (model, allowed-tools, argument-hint), designing workflows, or writing to */commands/*.md files.
building-agents
Expert at creating and modifying Claude Code agents. Auto-invokes when creating/updating agents, modifying agent frontmatter (model, tools, description), designing agent architecture, or writing to */agents/*.md files.
reading-logseq-data
>
querying-logseq-data
>
understanding-db-schema
>
writing-to-logseq
>
migrating-to-db
>
connecting-to-logseq
>
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
book-writer
You MUST read this skill completely before writing ANY content for theological books. Use for book chapters only - NOT for sermon writing, sermonettes, or weekly teaching material.
theological-sparring-partner
You MUST use this when users want to explore theological ideas, test apologetic arguments, defend biblical viewpoints, or develop doctrinal positions through rigorous dialogue. Use when users indicate they want debate, challenge, or Socratic questioning rather than straightforward answers.
sermon-writer
You MUST use this when users ask you to write, create, or generate sermon content - sermons, sermonettes, or split sermons for United Church of God worship services. Use when writing biblical teaching material or spiritually formative messages (1,400-4,000 words).
grammar
Use when users explicitly request grammar checking, spelling correction, proofreading, or style editing of ANY written content - sermons, sermonettes, devotionals, blogs, academic papers, or book chapters. Specializes in US English and theological writing styles.
biblical-accuracy
You MUST use this when writing or reviewing ANY biblical content - sermons, teachings, devotionals, blog posts containing Scripture references. Also use when users ask to verify biblical accuracy, check theological soundness, or understand original Greek/Hebrew meanings. Ensures alignment with United Church of God doctrine.
critical-biblical-listener
You MUST use this when reviewing completed sermons, Bible teachings, or theological content. Use when users ask you to evaluate, critique, or assess biblical faithfulness of teaching material. Acts as a skeptical reviewer testing claims against Scripture.
llm-orchestrator
Multi-LLM orchestration utilities for discovering available CLI tools, assessing change complexity, and building structured prompts. Used by reviewer sub-agents and multi-model commands.
claude-code-config
Use this skill when helping manage Claude Code configuration, including settings, MCP servers, LSP servers, skills, hooks, permissions, plugins, or per-device overrides. Also use when the user asks about Claude Code features, marketplace skills, or wants to modify their setup.
converge
Harden an already-decided plan into a self-terminating autonomous-goal spec — a checklist with machine-checkable exit criteria, a non-gameable Definition-of-Done "convergence gate", and a gate-first /goal (or /loop) driver prompt that memoryless, multi-session drivers converge on and HALT. Use when the user wants to hand an autonomous driver a "true definition of done" — e.g. "draft a goal I can run with /goal until it's done", "define exit criteria and stop when complete", "make it converge". NOT for deciding WHAT the work is (use /opsx or the spec skill for interactive, human-in-the-loop planning); this hardens a plan you already have into something a driver can finish on its own.
spec
Spec-driven workflow wrapper — how planning, implementation, and verification compose on this system. Load when starting any non-trivial feature or change (multi-file, needs design decisions, or the user asks for a plan/proposal/spec). Routes planning to OpenSpec (/opsx), execution to the delegation skill, and quality gates to the discipline skills.
delegation
Tiered-model orchestration — a strong model plans, decomposes, and reviews while weak-model workers implement. Load before dispatching implementation work when acting as the orchestrator (see the "Orchestrate, Don't Implement" policy in global context).
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
d20-combat
This skill should be used when the GM needs to handle combat situations, including starting combat, rolling initiative, resolving attack rolls, managing combat encounters, rolling damage, tracking hit points, applying conditions, or running d20-style tactical combat. Provides combat flow, turn structure, attack resolution, and condition references.
ap-adversaries
This skill should be used when the GM needs to create Apocrypha adversaries, build adversary keyword blocks, design Fear abilities, determine stress thresholds, set adversary tier and difficulty, track adversary stress during encounters, or reference adversary templates and examples for minor, standard, and major tier adversaries.
Page 1297 of 1708 · 85390 results
