Curated collection of Claude Code plugins for everyday development.
Skills, agents, and hooks that make Claude Code smarter about your workflow — from coding standards to git automation.
omcc-statusline — Claude Code statusline with git indicators (branch, CI, PRs, msgs), API usage and vibe pacing.
# Add marketplace
/plugin marketplace add j2h4u/oh-my-claude-plugins
# Install what you need
/plugin install coding-standards@oh-my-claude-pluginsOr browse interactively: /plugin → Browse and install plugins → oh-my-claude-plugins
oh-my-claude-plugins/
├── .claude-plugin/
│ ├── marketplace.json # Marketplace metadata
│ └── plugin.json # Plugin registry
├── agents/ # Custom agents
│ ├── plugin.json
│ ├── python-code-reviewer/
│ ├── python-quick-fixer/
│ └── quick-worker/
├── claude-code-meta/ # Claude Code tooling
│ ├── plugin.json
│ └── skills/
│ ├── claude-md-redirect/
│ ├── claude-md-writer/
│ ├── cli-skill-creator/
│ ├── mcp-builder/
│ └── opencode-config/
├── coding-standards/ # Code quality plugins
│ ├── plugin.json
│ └── skills/
│ ├── dignified-bash/
│ ├── dignified-python/
│ ├── kaizen/
│ └── software-architecture/
├── databases/ # Database tools
│ ├── plugin.json
│ └── skills/
│ ├── metabase-swiss-knife/
│ └── postgres-patterns/
├── devops/ # System administration
│ ├── plugin.json
│ └── skills/
│ └── linux-sysadmin/
├── docs/ # Documentation (plugin + official guides)
│ ├── plugin.json
│ ├── skills/ # Documentation creation skills
│ │ ├── doc-coauthoring/
│ │ ├── mermaid-best-practices/
│ │ └── readme-generator/
│ ├── plugins.md # Official Claude Code documentation
│ ├── hooks.md
│ └── plugin-development/
├── git-tools/ # Git workflow plugins
│ ├── plugin.json
│ └── skills/
│ ├── changelog-generator/
│ ├── gh/
│ └── git-workflow-manager/
├── productivity/ # Analysis tools
│ ├── plugin.json
│ └── skills/
│ └── meeting-insights-analyzer/
├── statusline/ # Utility: custom statusline
│ └── agents/
│ └── statusline-setup/
└── web-dev/ # Frontend development
├── plugin.json
└── skills/
├── vercel-react-best-practices/
├── web-artifacts-builder/
└── web-design-guidelines/
Each plugin directory contains:
plugin.json— Plugin manifestskills/— Skill directories with SKILL.mdagents/— Agent directories (where applicable)references/,examples/— Supporting content (in skill dirs)
Code quality and development philosophy.
| Skill | Description | Quality |
|---|---|---|
| dignified-bash | Strict mode, shellcheck, defensive patterns | ⭐⭐⭐⭐ |
| dignified-python | LBYL philosophy, version-aware (3.10-3.13), Click CLI | ⭐⭐⭐⭐⭐ |
| kaizen | Continuous improvement, poka-yoke, YAGNI | ⭐⭐⭐⭐⭐ |
| software-architecture | Clean Architecture & DDD principles | ⭐⭐ |
Git workflows and GitHub integration.
| Skill | Description | Quality |
|---|---|---|
| changelog-generator | Transform commits into user-friendly changelogs | ⭐⭐⭐ |
| gh | PR management, GraphQL API, Projects V2 | ⭐⭐⭐⭐⭐ |
| git-workflow-manager | Conventional commits, semantic versioning | ⭐⭐⭐ |
Frontend development.
| Skill | Description | Quality |
|---|---|---|
| vercel-react-best-practices | 45 performance rules: waterfalls, bundles, SSR | ⭐⭐⭐⭐ |
| web-artifacts-builder | Build React artifacts for Claude.ai | ⭐⭐ |
| web-design-guidelines | Vercel Web Interface Guidelines | ⭐⭐ |
Documentation creation.
| Skill | Description | Quality |
|---|---|---|
| doc-coauthoring | Collaborative workflow: gathering, refinement, reader testing | ⭐⭐⭐⭐ |
| mermaid-best-practices | Mermaid diagrams: syntax, quoting, shapes, rendering pitfalls | ⭐⭐⭐ |
| readme-generator | README best practices by project type | ⭐⭐⭐ |
System administration.
| Skill | Description | Quality |
|---|---|---|
| linux-sysadmin | Debian/Ubuntu: systemd, permissions, packages | ⭐⭐⭐⭐ |
Database tools and management.
| Skill | Description | Quality |
|---|---|---|
| metabase-swiss-knife | CLI for Metabase: inspect, diag, backup/restore, cards, dashboards | ⭐⭐⭐⭐ |
| postgres-patterns | Idiomatic PostgreSQL: LATERAL as variables, CTEs, window functions, indexes | ⭐⭐⭐ |
Claude Code tooling and meta-skills.
| Skill | Description | Quality |
|---|---|---|
| cli-skill-creator | Meta-skill for creating CLI tool skills | ⭐⭐⭐⭐⭐ |
| mcp-builder | MCP server development: Python, Node.js | ⭐⭐⭐⭐⭐ |
| claude-md-redirect | Redirect to AGENTS.md with PostToolUse hook | ⭐⭐⭐ |
| claude-md-writer | CLAUDE.md best practices: size limits, 3-tier docs | ⭐⭐⭐⭐ |
| opencode-config | Custom providers, model selection | ⭐⭐⭐ |
Utility: statusline — Custom statusline showing costs & context usage. Install via @"statusline-setup" agent.
Analysis tools.
| Skill | Description | Quality |
|---|---|---|
| meeting-insights-analyzer | Communication patterns, speaking ratios | ⭐⭐⭐⭐ |
Custom agents for code tasks.
| Agent | Triggers | Description |
|---|---|---|
| python-code-reviewer | "review Python code" | READ-ONLY analysis, creates issue report |
| python-quick-fixer | "fix Python issues" | Batch fixes from issue list |
| quick-worker | "do this task" | Fast executor for mechanical tasks |
Quick overview grouped by rating to identify improvement priorities:
Deep insights + original approaches, comprehensive content:
| Skill | Category | What makes it exemplary |
|---|---|---|
| gh | git-tools | Deep mental model, original workflow patterns, exemplary progressive disclosure |
| mcp-builder | claude-code-meta | Deep best practices, includes working evaluation tools |
| cli-skill-creator | claude-code-meta | Highly original meta-skill, systematic CLI introspection approach |
| dignified-python | coding-standards | Deep LBYL philosophy, original error-handling approach |
| kaizen | coding-standards | Deep principles with original adaptation to code |
Good depth, well-structured, production ready:
| Skill | Category | Notes |
|---|---|---|
| dignified-bash | coding-standards | Well-structured but standard bash practices |
| linux-sysadmin | devops | Useful practices, standard content |
| metabase-swiss-knife | databases | Full CLI with backup/restore, zero dependencies |
| doc-coauthoring | docs | Good workflow but not particularly deep |
| claude-md-writer | claude-code-meta | Good compilation of best practices |
| meeting-insights-analyzer | productivity | Original approach to meeting analysis |
| vercel-react-best-practices | web-dev | Great structure but just packages Vercel rules |
| Skill | Category | Why shallow/standard | Replacement strategy |
|---|---|---|---|
| changelog-generator | git-tools | Just a workflow, not deep | Find deeper changelog philosophy/patterns |
| git-workflow-manager | git-tools | Basic conventional commits reference | Find advanced git workflow patterns |
| opencode-config | claude-code-meta | Just config reference, shallow | Find deeper OpenCode configuration insights |
| claude-md-redirect | claude-code-meta | Utility, very shallow | Consider removing or expanding |
| readme-generator | docs | Just process, shallow content | Find README philosophy/patterns beyond basics |
🚨 Priority for improvement — Functional but missing critical content:
| Skill | Category | What's missing | Search for |
|---|---|---|---|
| software-architecture | coding-standards | Needs examples, library guide | Code pattern examples, library-first guides |
| web-artifacts-builder | web-dev | Needs troubleshooting guide, component patterns, examples | React artifact patterns, debugging guides |
| web-design-guidelines | web-dev | Needs expansion (176→1500 words), sample output examples | UI/UX guidelines, review examples |
Quality is rated on four dimensions:
- Structure — Progressive disclosure, references/, examples/, clear organization
- Completeness — All sections present, no missing content
- Depth — Insights beyond surface level, practical patterns, deep understanding
- Originality — Unique approach or just packaging existing docs/tools
| Stars | Meaning | Examples |
|---|---|---|
| ⭐⭐⭐⭐⭐ | Exemplary — deep + original + comprehensive | gh (mental model), mcp-builder (evaluation tools), kaizen (code adaptation) |
| ⭐⭐⭐⭐ | High quality — good depth + well-structured | dignified-bash, linux-sysadmin, meeting-insights-analyzer |
| ⭐⭐⭐ | Solid — complete but shallow/standard | changelog-generator (just workflow), opencode-config (config reference) |
| ⭐⭐ | Incomplete — needs expansion or examples | software-architecture, web-artifacts-builder, web-design-guidelines |
Why downgraded from 5→3 stars?
- Just a workflow without deep insights (changelog-generator)
- Simple reference/config guide (git-workflow-manager, opencode-config)
- Packaging existing docs without original approach (vercel-react-best-practices)
- Utility skill without depth (claude-md-redirect)
Check Notes column for specifics. See SKILLS-REVIEW-REPORT.md for detailed improvement roadmap.
Some Claude Code versions silently skip installed plugins if they are not explicitly listed in the enabledPlugins map in ~/.claude/settings.json. Older versions loaded all installed plugins automatically, but newer versions may require this explicit flag. When affected, skills and agents simply don't appear in the session — no error, no warning.
Symptoms: You install a plugin, but its skills don't show up in /skills. The plugin is listed in ~/.claude/plugins/installed_plugins.json but missing from enabledPlugins in ~/.claude/settings.json.
Fix: Run the included utility that syncs the two files:
python3 meta/utils/fix-enabled-plugins/fix-enabled-plugins.pyIt shows diagnostics (installed vs enabled count), a diff of what's missing, creates a backup, and applies the fix. Safe to run multiple times. See fix-enabled-plugins README for details.
Use as local plugin directory (development mode):
claude --plugin-dir /path/to/oh-my-claude-pluginsComprehensive documentation for Claude Code plugin development:
| Guide | Description |
|---|---|
| Plugins | Plugin development quickstart |
| Plugins Reference | Technical specifications and schemas |
| Plugin Marketplaces | Marketplace creation and management |
| Hooks | Event-driven automation (27KB reference) |
| Skills | Agent skills development |
| Sub-Agents | Specialized AI assistants |
| Slash Commands | Command system reference |
| Settings | Configuration guide (46KB) |
Advanced guides for plugin developers:
| Resource | Description |
|---|---|
| Schemas | Complete schemas for plugin.json, hooks, marketplace (1,479 lines) |
| Best Practices | Organization, naming conventions, common mistakes (1,156 lines) |
| Templates | Ready-to-use templates for all plugin components |
| Examples | Complete plugin walkthrough and testing workflow |
Quality indicators are shown in the skill tables above. For detailed analysis including:
- Specific issues and recommended fixes
- Missing content (examples, troubleshooting guides)
- Word count analysis and expansion needs
- Priority-ordered improvement roadmap
See SKILLS-REVIEW-REPORT.md — comprehensive review of all 19 skills with actionable improvement suggestions.
- Claude Code CLI
- Git (for version control features)
Plugin validation runs automatically on every push via GitHub Actions. To validate locally:
# Check JSON syntax
jq empty .claude-plugin/marketplace.json
# Validate plugin structure
bash .github/workflows/validate-plugins.ymlInspired by Claude Code Plugin Template by Ivan Magda. Plugin development documentation (schemas, best practices, templates) adapted from the template's plugin-authoring skill.
Some skills are based on or derived from external sources:
| Skill | Source | How it's used |
|---|---|---|
| web-design-guidelines | vercel-labs/web-interface-guidelines | Thin wrapper that fetches upstream command.md at runtime — always up to date |
| vercel-react-best-practices | Vercel Engineering blog | Compiled from multiple Vercel blog posts into 45 structured rules with examples |
| postgres-patterns | Telegram post on CROSS JOIN LATERAL | LATERAL-as-variables pattern; other patterns from PostgreSQL documentation |
Individual items may have their own licenses. Check each directory.