What Plugin Categories Are Available in the Claude Plugins Community Repository?
The Claude Plugins Community repository defines three plugin categories in its marketplace manifest: testing, productivity, and development.
The Claude Plugins Community repository maintains a lightweight taxonomy for organizing community-built plugins. Each plugin's optional category field is defined in .claude-plugin/marketplace.json, which serves as the single source of truth for the marketplace. This article breaks down the three categories currently available, explains how they're implemented in the source code, and shows how to extract them programmatically.
The Three Plugin Categories
The marketplace uses a deliberately minimal classification system. Based on the source analysis of .claude-plugin/marketplace.json, only three distinct category values appear across all plugins:
testing
Plugins in the testing category add testing-related capabilities to Claude. The Meticulous plugin exemplifies this category, providing visual-regression testing functionality.
Relevant source location: .claude-plugin/marketplace.json#L1005-L1012
productivity
The productivity category covers plugins that enhance workflow efficiency. Adspirer-Ads-Agent uses this category, bundling multiple ad-management tools into a unified productivity suite.
Relevant source location: .claude-plugin/marketplace.json#L6668-L6674
development
Plugins tagged development offer development-oriented integrations. Agentic-Commerce demonstrates this category, providing a suite of e-commerce-related development tools.
Relevant source location: .claude-plugin/marketplace.json#L6934-L6942
How Categories Are Defined in the Source Code
The category field is optional — many plugins omit it entirely. This design choice keeps the taxonomy lightweight and avoids over-classification. The field appears as a simple string attribute within each plugin's entry in the marketplace JSON array.
Here's how to programmatically extract all available categories from .claude-plugin/marketplace.json:
import json
from pathlib import Path
# Load the marketplace manifest
manifest_path = Path(
"/cache/repos/github.com/anthropics/claude-plugins-community/main/.claude-plugin/marketplace.json"
)
with manifest_path.open() as fp:
data = json.load(fp)
# Extract distinct, non-empty categories
categories = sorted(
{p["category"] for p in data["plugins"] if p.get("category")}
)
print("Available plugin categories:", ", ".join(categories))
# → Available plugin categories: development, productivity, testing
This script demonstrates the filtering pattern needed when working with the optional field: always check p.get("category") to handle entries where the attribute is missing.
Key Files for Understanding Plugin Categories
| File | Purpose |
|---|---|
.claude-plugin/marketplace.json |
Primary source — contains the full plugin registry with optional category attributes for each entry |
README.md |
Repository documentation that points users to the marketplace file for plugin discovery |
opencode.json |
Metadata for automated tooling that assists with repository analysis and marketplace data processing |
Summary
- Three categories exist:
testing,productivity, anddevelopment - Source of truth:
.claude-plugin/marketplace.jsonin the repository root - Optional field: The
categoryattribute is not required; many plugins don't specify one - Lightweight design: The taxonomy is intentionally minimal with no hierarchical structure
Frequently Asked Questions
What happens if a plugin doesn't specify a category?
Plugins without a category field are still valid and appear in the marketplace. They simply aren't grouped into any category, making the field truly optional rather than enforced.
Can plugin authors propose new categories?
The current implementation in .claude-plugin/marketplace.json suggests categories are defined by convention rather than an enumerated schema. New values would likely need repository maintainer approval to maintain taxonomy consistency.
Where should I look to find all plugins in a specific category?
Parse .claude-plugin/marketplace.json and filter by the category field using standard JSON tooling. The repository doesn't currently expose category-specific endpoints or views beyond the raw manifest.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →