Audit Claude Code skills, agents, hooks, plugins, configs, memory, and output styles for quality, compliance, security, and maintainability using specialized skills and read-only agents. Manage documentation lifecycle, monitor performance and API status, optimize contexts, troubleshoot issues, and delegate to official docs for guidance on development, permissions, and setups.
npx claudepluginhub melodic-software/claude-code-plugins --plugin claude-ecosystemPROACTIVELY use when creating, reviewing, or validating Claude Code subagents. Audits for quality, compliance, and maintainability - checks YAML frontmatter, name/description requirements, tool access, model selection, color, and permissions configuration. Used by /audit-agents for parallel auditing.
PROACTIVELY use when analyzing agents for consolidation opportunities. Compares agent configurations, identifies shared patterns, tracks component references, and assesses consolidation impact. Used by /audit-agent-consolidation for parallel analysis.
PROACTIVELY use to validate audit findings before presenting results. Cross-references findings against official docs, MCP servers, and development skills to filter false positives. Spawned by audit commands when validation is enabled (default).
PROACTIVELY use when troubleshooting Claude Code errors, checking for known issues, or finding workarounds. Searches anthropics/claude-code GitHub issues automatically. Use for error investigation, duplicate checking, and workaround discovery.
PROACTIVELY use when reviewing skills or memory files for docs-management delegation compliance. Detects hardcoded Claude Code data and verifies proper delegation patterns. Used by /audit-docs-delegation for parallel auditing.
PROACTIVELY use when researching Claude Code features, searching official documentation, resolving doc_ids, or finding canonical guidance on Claude Code topics (hooks, skills, memory, MCP, plugins, settings, subagents, SDK, etc.). Auto-loads docs-management skill for discovery.
PROACTIVELY use when creating, reviewing, or validating Claude Code hooks. Audits for quality, compliance, and maintainability - checks hooks.json configuration, hook script structure, matchers, environment variables, and decision control. Used by /audit-hooks for parallel auditing.
Classifies X/Twitter posts by category, scores relevance to Claude Code ecosystem, extracts actionable insights, and maps findings to affected plugin areas. Used by the social-intelligence skill after feed scanning.
PROACTIVELY use when reviewing or validating MCP server configurations. Audits for quality, compliance, and security - checks .mcp.json structure, server configurations, transport types, authentication setup, and scope verification. Used by /audit-mcp for parallel auditing.
PROACTIVELY use for research requiring multiple MCP servers. Coordinates queries across context7, ref, microsoft-learn, perplexity, and firecrawl, and whatever other MCP servers are enabled. Returns consolidated findings with citations.
PROACTIVELY use when reviewing or validating Claude Code CLAUDE.md memory files or rule files. Audits for quality, compliance, and organization - checks import syntax, hierarchy compliance, circular imports, size guidelines, progressive disclosure, YAML frontmatter, glob patterns, and content structure. Used by /audit-memory and /audit-rules for parallel auditing.
PROACTIVELY use when reviewing or validating Claude Code output styles. Audits for quality, compliance, and usability - checks markdown format, YAML frontmatter, name/description fields, and content structure. Used by /audit-output-styles for parallel auditing.
PROACTIVELY use when Claude Code is slow, unresponsive, laggy, or experiencing performance issues. Analyzes storage bloat, context window state, API status, and known GitHub issues to diagnose problems and recommend fixes.
PROACTIVELY use when creating, reviewing, or validating Claude Code plugins or LSP server configurations. Audits for quality, compliance, and maintainability - checks plugin.json manifests, component organization, namespace compliance, distribution readiness, .lsp.json structure, server commands, and language associations. Used by /audit-plugins and /audit-lsp for parallel auditing.
PROACTIVELY use when improving, optimizing, or refactoring prompts. Executes the 4-step prompt improvement workflow using Anthropic's best practices. Auto-loads prompt-improvement skill for keyword registries and workflow guidance.
PROACTIVELY use when reviewing or validating Claude Code settings.json files. Audits for quality, compliance, and correctness - checks settings schema, permission rules, sandbox configuration, and environment variables. Used by /audit-settings for parallel auditing.
PROACTIVELY use when creating, reviewing, or validating Claude Code skills. Audits for quality, compliance, and maintainability - checks YAML frontmatter, delegation patterns, keyword coverage, progressive disclosure, tool configuration, and content quality. Used by /audit-skills for parallel auditing.
PROACTIVELY use when reviewing or validating Claude Code status line configurations. Audits for quality, compliance, and functionality - checks script structure, JSON input handling, terminal color codes, and cross-platform compatibility. Used by /audit-statuslines for parallel auditing.
PROACTIVELY use when auditing Claude Code user configuration health, detecting structure drift, or validating ~/.claude/ against known patterns. Performs comprehensive health checks including JSON validity, orphaned files, security scan, and drift detection.
Browser automation specialist that uses claude-in-chrome MCP to navigate X/Twitter profiles, extract posts, and return structured post data. Used by the social-intelligence skill for feed scanning.
Central authority for Claude Agent SDK (TypeScript and Python SDKs). Covers SDK installation, authentication (Anthropic key, Bedrock, Vertex), sessions and resumption, forking sessions, streaming vs single mode, custom tools, permissions (allowedTools, disallowedTools, permissionMode), MCP integration, system prompts (CLAUDE.md, appendSystemPrompt, outputStyle), cost tracking, todo tracking, structured outputs, hosting patterns, plugins, and SDK branding guidelines. Assists with building custom agents, configuring SDK options, and troubleshooting SDK issues. Delegates 100% to docs-management skill for official documentation.
Analyze agents for consolidation opportunities. Groups agents by configuration, tracks references, and manages refactoring.
Audit Claude Code subagents for quality, compliance, and maintainability. Use after creating or modifying agents, before releases, or for periodic quality checks.
Audit skills and memory files for docs-management delegation compliance. Detects hardcoded Claude Code data and verifies proper delegation patterns.
Audit Claude Code hooks for quality, compliance, and maintainability. Use after creating hooks, before releases, or for periodic quality checks.
View audit log entries for all component types (skills, commands, agents, hooks, etc.) to monitor audit health and track coverage
Audit Claude Code LSP server configurations for quality and compliance. Use when creating or validating plugin LSP servers, or troubleshooting code intelligence issues.
Audit MCP server configurations for quality, compliance, and security. Use to validate .mcp.json files and server setups.
Audit Claude Code CLAUDE.md memory files for quality, compliance, and organization. Use to validate import syntax, detect circular imports, and check hierarchy compliance.
Audit Claude Code output styles for quality, compliance, and usability. Use when creating custom styles or validating existing ones.
Audit Claude Code plugins for quality, compliance, and distribution readiness. Use before releases or for periodic quality checks.
Audit Claude Code rule files for quality and compliance. Use when creating or validating .claude/rules/*.md files, or troubleshooting rule loading issues.
Audit Claude Code settings.json files for quality, compliance, and security. Use to validate configuration before deployment or check for exposed secrets.
Audit Claude Code skills for quality, compliance, delegation pattern, and maintainability. Use after creating skills, before releases, or for periodic quality checks.
Audit Claude Code status lines for quality and cross-platform compatibility. Use when creating or validating custom status line scripts, or troubleshooting terminal output issues.
Check Anthropic API status and recent incidents from status.anthropic.com
Analyze current context window usage and provide optimization recommendations
Central authority for Claude Desktop application - the native desktop app for running Claude Code sessions. Covers installation (macOS/Windows), Git worktrees for parallel sessions, .worktreeinclude file configuration, cloud session launch, environment configuration, MCP Desktop Extensions (.mcpb), and Desktop vs CLI comparison. Assists with Desktop setup, worktree configuration, cloud sessions, and troubleshooting. Delegates 100% to docs-management skill for official documentation.
Clear cached plugin copies (requires reinstall after)
Create new skill scaffold with required structure. Use when starting a new skill from scratch or need proper YAML frontmatter template.
Gets, checks, and verifies the current UTC date and time for unambiguous temporal reference. Use when starting tasks, verifying temporal context, ensuring date awareness before time-sensitive operations, or when incorrect date assumptions are detected.
Run comprehensive Claude Code performance diagnostics - analyzes storage, API status, and known issues
Single source of truth and librarian for ALL Claude official documentation. Manages local documentation storage, scraping, discovery, and resolution. Use when finding, locating, searching, or resolving Claude documentation; discovering docs by keywords, category, tags, or natural language queries; scraping from sitemaps or docs maps; managing index metadata (keywords, tags, aliases); or rebuilding index from filesystem. Run scripts to scrape, find, and resolve documentation. Handles doc_id resolution, keyword search, natural language queries, category/tag filtering, alias resolution, sitemap.xml parsing, docs map processing, markdown subsection extraction for internal use, hash-based drift detection, and comprehensive index maintenance.
Manage Claude Code documentation lifecycle. Actions: scrape, validate, refresh, rebuild-index, clear-cache.
Analyzes Claude Code ecosystem health by tracking all 27 extensibility components across 6 tiers - including plugin components, core configuration, environment/CLI, authentication, session features, and integrations. Use when checking if Claude Code components are up-to-date, orchestrating audits efficiently, tracking documentation coverage, applying updates from new Claude Code versions, or getting an overview of ecosystem component staleness.
Central authority for Claude Code enterprise security. Covers enterprise managed policies (managed-settings.json), settings precedence hierarchy, policy file locations (macOS, Linux, Windows), unoverridable organizational policies, cloud execution security (isolated VMs, network access controls, credential protection), IDE security (VS Code, JetBrains), devcontainer security, and security best practices for teams. Assists with configuring enterprise policies, understanding precedence, and implementing organizational security standards. Delegates 100% to docs-management skill for official documentation.
Export Claude Code's current system prompt to console or file
Central authority for Claude Code hooks management in this repository. Automates enforcement of critical repository rules through hooks. Use when adding hooks, managing hooks, configuring hooks, troubleshooting hooks, or understanding hook behavior. Delegates to docs-management skill for official hooks documentation. Provides organization-specific patterns, configuration management, and workflow guidance.
Improve and optimize prompts using Anthropic's 4-step prompt improvement workflow
List Claude Code components. Actions: env-vars, sessions, settings, skills, tools.
LSP server recommendations, .lsp.json configuration, installation guides, and troubleshooting for Language Server Protocol in Claude Code
Central authority for Claude Code Model Context Protocol (MCP) integration. Covers MCP server installation (HTTP, SSE, stdio transports), server management (add, list, remove), installation scopes (local, project, user), plugin-provided MCP servers, enterprise MCP configuration, MCP resources and @ mentions, MCP prompts as skills, OAuth authentication, environment variable expansion, Claude Code as MCP server, output limits, and MCP security. Assists with connecting external tools, configuring MCP servers, managing authentication, and troubleshooting MCP issues. Delegates 100% to docs-management skill for official documentation.
Meta-skill for Claude Code memory system (CLAUDE.md, static memory). Provides stable principles, keyword registry for documentation lookups, and navigation guidance. Use when working with CLAUDE.md files, memory hierarchy, import syntax, progressive disclosure patterns, memory organization, or best practices for static memory. Delegates to docs-management skill for current implementation details. Keywords: CLAUDE.md, static memory, memory hierarchy, import syntax, progressive disclosure, memory organization, enterprise project user memory.
Central authority for Claude Code output styles. Covers built-in output styles (Default, Explanatory, Learning), custom output styles, output style frontmatter (name, description, keep-coding-instructions), /output-style command, style switching, output style creation and customization, output style comparisons (vs CLAUDE.md, vs agents, vs slash commands), and output style settings. Assists with selecting appropriate output styles, creating custom styles, configuring output behavior, and understanding style differences. Delegates 100% to docs-management skill for official documentation.
Best practices for Claude Code performance optimization, context management, storage cleanup, and troubleshooting slowdowns
Central authority for Claude Code permissions. Covers permission system (tiered model, read-only, bash, file modification), permission rules (allow, ask, deny), rule precedence, permission modes (default, acceptEdits, plan, bypassPermissions), tool-specific permission rules (Bash patterns, Read/Edit patterns, WebFetch domains, MCP tools), /permissions command, and additionalDirectories. Assists with configuring permission rules, understanding permission modes, and troubleshooting permission issues. Delegates 100% to docs-management skill for official documentation.
Central authority for Claude Code plugins. Covers plugin creation, plugin structure (plugin.json, commands/, agents/, skills/, hooks/), plugin manifest configuration, plugin installation and management (/plugin command), plugin marketplaces (marketplace.json, adding marketplaces), team plugin workflows, plugin development and testing, plugin debugging, plugin sharing and distribution, MCP servers in plugins, and plugin settings. Assists with creating plugins, installing from marketplaces, configuring team plugins, and troubleshooting plugin issues. Delegates 100% to docs-management skill for official documentation.
Meta-skill for improving and optimizing prompts using Anthropic's prompt engineering best practices. Provides the 4-step improvement workflow (example identification, initial draft, chain of thought refinement, example enhancement), keyword registries for documentation lookup, and decision trees for improvement strategies. Use when improving prompts, optimizing for accuracy, adding chain of thought reasoning, structuring with XML tags, enhancing examples, or iterating on prompt quality. Delegates to docs-management skill for official prompt engineering documentation.
Central authority for Claude Code sandboxing and isolation. Covers sandboxed bash tool, /sandbox command, filesystem isolation (blocked access, custom paths), network isolation (domain restrictions, proxy support), OS-level enforcement (bubblewrap on Linux, Seatbelt on macOS), sandbox configuration options, escape hatches (dangerouslyDisableSandbox, allowUnsandboxedCommands), and sandbox security limitations. Assists with configuring sandbox settings, understanding isolation mechanisms, and troubleshooting sandbox issues. Delegates 100% to docs-management skill for official documentation.
Search Claude Code GitHub issues for troubleshooting. Shortcut for searching anthropics/claude-code.
Central authority for Claude Code configuration and settings. Covers settings.json files (user, project, enterprise), available settings, permission settings, sandbox settings, settings precedence, plugin configuration, environment variables, and tools available to Claude. Assists with configuring Claude Code behavior, managing permissions, setting up enterprise policies, and troubleshooting configuration issues. Delegates 100% to docs-management skill for official documentation.
Set up LSP servers for the current project - auto-detects languages, researches recommendations, configures .lsp.json
Comprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
TODO: [What it does]. Use when [specific triggers]. Example: "Analyzes Excel spreadsheets and generates charts. Use when working with Excel files, .xlsx, spreadsheet analysis, or data visualization." REQUIRED: Include "Use when..." with trigger keywords (file types, domains, tasks). Third person. Max 1024 chars.
Migrate legacy .claude/commands/ to .claude/skills/ directory structure. Actions: discover, analyze, migrate, audit, validate, fix.
Twitter/X social intelligence monitoring for the Claude Code ecosystem. Scans feeds from Anthropic/Claude Code team members, extracts actionable insights, tracks state, and produces reports. Uses claude-in-chrome MCP for browser automation.
Central authority for Claude Code status line configuration. Covers custom status line creation, /statusline command, status line settings (statusLine in settings.json), JSON input structure (model, workspace, cost, session info), status line scripts (Bash, Python, Node.js), terminal color codes, git-aware status lines, helper functions, and status line troubleshooting. Supports creating custom status lines, configuring status line behavior, and displaying contextual session information. Delegates 100% to docs-management skill for official documentation.
Central authority for Claude Code subagents (sub-agents). Covers agent file format, YAML frontmatter, tool access configuration, model selection (inherit, sonnet, haiku, opus), automatic delegation, agent lifecycle, resumption, command-line usage (/agents), Agent SDK programmatic agents, priority resolution, and built-in agents (Plan subagent). Assists with creating agents, configuring agent tools, understanding agent behavior, and troubleshooting agent issues. Delegates 100% to docs-management skill for official documentation.
Add missing environment variable defaults to settings.json or settings.local.json
Comprehensive MCP server management. Discovers, updates, and helps set up MCP servers with dependency detection and best practice guidance.
Update the custom Claude Code settings JSON schema with changelog-discovered and web-verified settings.
Central authority for managing Claude Code user configuration directories (~/.claude/ and ~/.claude.json). Covers storage cleanup, backup/restore, reset workflows, MCP server preservation, history management, plan management, session statistics, and configuration health auditing. Delegates to docs-management skill for official documentation. Use when managing user config, cleaning up storage, backing up settings, resetting Claude Code, or auditing configuration health.
Manage Claude Code user configuration (~/.claude/). Actions: audit, backup, cleanup-agents, cleanup-debug, cleanup-hook-logs, cleanup-sessions, compaction-review, costs, file-versions, global, history, mcp, plans, prompt-extract, prune, reset, reset-plugins, restore, retrospective, session-stats, status, storage, transcript-search.
Modifies files
Hook triggers on file write and edit operations
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimTactical Agentic Coding course content by @IndyDevDan - Master agentic coding tactics to scale engineering and build self-operating codebases
Claude Code workflow patterns: prompting, CLAUDE.md maintenance, multi-agent orchestration
Automatic documentation-as-code engine. Maintains project documentation as a side effect of development — no manual invocation needed.
Use this agent when you need to analyze a service or codebase component and create comprehensive documentation in CLAUDE.md files. This agent should be invoked after implementing new services, major refactoring, or when documentation needs updating to reflect the current codebase structure. Examples: <example>Context: The user has just implemented a new authentication service and wants to document it properly. user: 'I just finished implementing the auth service, can you document how it works?' assistant: 'I'll use the codebase-documenter agent to analyze the authentication service and create detailed documentation in CLAUDE.md' <commentary>Since the user has completed a service implementation and needs documentation, use the Task tool to launch the codebase-documenter agent to create comprehensive CLAUDE.md documentation.</commentary></example> <example>Context: The user wants to ensure a newly added API module is properly documented for the team. user: 'We need documentation for the new payment processing API I just added' assistant: 'Let me use the codebase-documenter agent to analyze the payment processing API and create proper documentation' <commentary>The user needs documentation for a new API module, so use the codebase-documenter agent to create CLAUDE.md files with setup instructions and architectural notes.</commentary></example>
Code documentation with automated doc generation, code explanation, and tutorial engineering
Agents specialized in technical documentation and knowledge management. Focuses on documentation architecture and user-focused writing.
Uses power tools
Uses Bash, Write, or Edit tools
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Plugins for Claude Code: documentation management, code quality, and ecosystem support.
fnm (Fast Node Manager) is the recommended Node.js version manager for this project. It:
Install fnm:
# Windows (PowerShell as Admin)
winget install Schniz.fnm
# macOS/Linux
curl -fsSL https://fnm.vercel.app/install | bash
Configure for Git Bash (add to ~/.bashrc):
eval "$(fnm env --use-on-cd --shell bash)"
Or source the setup script which includes fnm initialization:
source "/path/to/claude-code-plugins/setup/bashrc-claude.sh"
Install Node:
fnm install 24
fnm default 24
npm install
npm run lint:md # Check for errors
npm run lint:md:fix # Auto-fix errors
Markdown linting runs automatically on PRs via GitHub Actions. The same rules apply locally and in CI.
/plugin install claude-ecosystem@claude-code-plugins
/plugin install code-quality@claude-code-plugins
/plugin install google-ecosystem@claude-code-plugins
This repo expects Codex CLI configuration to live in user scope under ~/.codex.
See .codex/README.md for the canonical locations.
| Plugin | Purpose |
|---|---|
| atlassian | Atlassian MCP server: Jira, Confluence, Compass integration |
| browser-automation | Browser automation MCP servers: Chrome DevTools, Playwright |
| business-analysis | BABOK techniques: capability mapping, stakeholder analysis, value streams, journey mapping |
| ci-cd | CI/CD pipelines: GitHub Actions, deployment automation, release management |
| claude-code-observability | Event logging, metrics, session diagnostics |
| claude-ecosystem | Claude Code docs, meta-skills, hooks, observability, auditors |
| code-quality | Code review, markdown linting, debugging, CI/CD templates |
| compliance-planning | Regulatory compliance: GDPR, HIPAA, PCI-DSS, AI governance, ISO 27001 |
| content-management-system | Headless CMS architecture: content modeling, taxonomies, media, theming |
| cursor-ecosystem | Cursor IDE docs, CLI, agent, keyword-based search |
| documentation-standards | Technical docs: arc42, C4 model, ADRs, RFC process, docs-as-code |
| dotnet | .NET 10+ automation: build, clean, SDK/tool install, version upgrades, Aspire MCP |
| duende-ecosystem | Duende IdentityServer, BFF, IdentityModel docs |
| enterprise-architecture | TOGAF, Zachman, ADRs, cloud alignment |
| event-modeling | Event-driven design: Event Modeling, Event Storming, CQRS, sagas |
| figma | Figma MCP server: design context, code generation, design tokens |
| formal-specification | Formal methods: UML/SysML, TLA+, OpenAPI/AsyncAPI, state machines |
| git | Git config, GPG signing, hooks, GitHub issues, history exploration |
| google-ecosystem | Gemini CLI docs, Claude-to-Gemini integration, configuration management |
| melodic-software | Developer onboarding, environment setup, commit workflows |
| microsoft | Microsoft MCP servers: Microsoft Learn, Azure, NuGet, Azure DevOps |
| milan-jovanovic | Milan Jovanovic .NET patterns: Clean Architecture, DDD, CQRS, EF Core |
| openai-ecosystem | OpenAI Codex CLI docs |
| requirements-elicitation | Requirements gathering: LLMREI interviews, gap analysis, prioritization |
| research | Research workflows: MCP integration, multi-source synthesis, structured output |
| response-quality | Response quality standards, source citations |
| security | Security: OWASP, authentication, cryptography, DevSecOps, threat modeling, 12 skills |
| soft-skills | Career progression, interviews, communication, professional visibility |