Core Plugin Directories in the Claude Plugins Community Repository

The anthropics/claude-plugins-community repository organizes its functionality into four core plugin directories—quickdesign/, testdino/, tres-finance-plugin/, and eli5/—each containing self-contained plugins with manifest files located at .claude-plugin/plugin.json.

The Claude Plugins Community repository serves as a centralized collection of open-source extensions for Claude Cowork and Claude Code. These core plugin directories house the source code, skill definitions, and metadata required to extend Claude's capabilities across design, testing, finance, and educational workflows.

What Are the Core Plugin Directories?

The repository structure centers on four top-level directories, each representing a standalone Claude plugin. Every directory follows a consistent internal layout, separating source code from plugin metadata.

quickdesign/

The quickdesign/ directory contains the QuickDesign plugin, which provides tools for generating promotional content and media. Its manifest is defined at [quickdesign/.claude-plugin/plugin.json](https://github.com/anthropics/claude-plugins-community/blob/main/quickdesign/.claude-plugin/plugin.json), while skill implementations reside in the quickdesign/skills/ subdirectory.

testdino/

The testdino/ directory hosts the TestDino plugin. According to the source code, this plugin includes its configuration at testdino/.claude-plugin/plugin.json and contains testing-related automation tools for software development workflows.

tres-finance-plugin/

The tres-finance-plugin/ directory implements the Tres Finance integration. This plugin connects Claude with financial data services, storing its manifest at tres-finance-plugin/.claude-plugin/plugin.json alongside its core logic.

eli5/

The eli5/ directory contains the ELI5 (Explain Like I'm 5) plugin, designed for educational content simplification. Its metadata is located at eli5/.claude-plugin/plugin.json, following the same structural pattern as the other core directories.

Plugin Manifest and Configuration Structure

Each core plugin directory contains a .claude-plugin/ subdirectory that houses the plugin.json manifest. These JSON files expose critical metadata including the plugin name, version, description, author, licensing, and entry points required by Claude Cowork and Claude Code.

The repository also maintains a top-level marketplace descriptor at .claude-plugin/marketplace.json. This file aggregates the manifests from all core plugin directories, enabling discovery and installation through the Claude plugin marketplace interface.

Installing and Using Core Plugins

You can install any of these core plugins using the Claude Code CLI. The following commands demonstrate adding the community marketplace and installing specific plugins.

Adding the Community Marketplace

First, register the community repository as a plugin source:

# Add the community marketplace to your local plugin index

claude plugin marketplace add anthropics/claude-plugins-community

Installing Specific Plugins

Install individual plugins by referencing their directory name with the claude-community version tag:

# Install a specific plugin (e.g., QuickDesign) at its latest version

claude plugin install quickdesign@claude-community

Loading Skills in Claude Cowork

Once installed, plugins expose their skills during Claude Cowork sessions. For example, interacting with the QuickDesign plugin works as follows:

User: I want to generate a short promotional video.
Claude: Sure! I'll use the **quickdesign** plugin to create it.
[The plugin runs the "quickdesign" skill and returns a video link.]

This interaction succeeds because the quickdesign/skills/ directory contains the skill definitions referenced by the plugin manifest.

Key Files Across Core Directories

File Path	Purpose
quickdesign/.claude-plugin/plugin.json	Manifest for the QuickDesign plugin
testdino/.claude-plugin/plugin.json	Manifest for the TestDino plugin
tres-finance-plugin/.claude-plugin/plugin.json	Manifest for the Tres Finance plugin
eli5/.claude-plugin/plugin.json	Manifest for the ELI5 plugin
.claude-plugin/marketplace.json	Aggregated marketplace index of all community plugins
README.md	Repository overview and usage instructions

Summary

• The anthropics/claude-plugins-community repository contains four core plugin directories: quickdesign/, testdino/, tres-finance-plugin/, and eli5/.
• Each directory is self-contained, storing source code and a .claude-plugin/plugin.json manifest file.
• The .claude-plugin/marketplace.json file at the repository root aggregates all plugin manifests for marketplace discovery.
• Install plugins using claude plugin install <name>@claude-community after adding the community marketplace.
• Skills are loaded from subdirectories like quickdesign/skills/ as defined in each plugin's manifest.

Frequently Asked Questions

What defines a plugin within the core directories?

Each core plugin directory must contain a .claude-plugin/plugin.json file that defines the plugin's name, version, description, author, licensing, and skill entry points. This manifest file enables Claude Cowork and Claude Code to load and execute the plugin's functionality.

How does the marketplace.json file function?

The .claude-plugin/marketplace.json file serves as an aggregated index that references the individual manifests from all four core plugin directories. This top-level descriptor allows the Claude plugin marketplace to discover and list available community plugins without scanning each subdirectory individually.

Where are plugin skills stored in the directory structure?

Plugin skills are stored in subdirectories within each core plugin folder. For example, the QuickDesign plugin stores its skills in quickdesign/skills/, as referenced by the main manifest file located at quickdesign/.claude-plugin/plugin.json.

What metadata is exposed in the plugin.json manifests?

According to the source code analysis, the plugin.json files expose the plugin name, version, description, author, licensing, and other metadata required by Claude Cowork and Claude Code to properly identify, display, and execute the plugin.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}