What Are the In-Tree Plugins in the Claude Plugins Community Repository?

The anthropics/claude-plugins-community repository hosts three official in-tree plugins—Tres Finance Plugin, QuickDesign, and ELI5—each bundled with a .claude-plugin/plugin.json manifest and skill definitions for Claude Code and Claude Cowork integration.

The anthropics/claude-plugins-community repository serves as the central distribution point for community-maintained Claude plugins. This guide examines the in-tree plugins that ship directly within the repository source tree, detailing their specific capabilities, manifest structures, and the exact file paths that enable Claude to discover and execute their functionality.

Complete List of In-Tree Plugins

The repository currently maintains three self-contained plugins in the root directory. Each plugin follows the standard Claude plugin layout, utilizing a hidden .claude-plugin folder for metadata and a skills/ directory housing implementation logic.

Tres Finance Plugin

Located at tres-finance-plugin/, this enterprise-focused tool provides financial workflow automation including wallet uploads, transaction validation, invoice-bill matching, and cost-basis calculations. The plugin registers its capabilities through tres-finance-plugin/.claude-plugin/plugin.json and defines individual tools in skill markdown files under tres-finance-plugin/skills/.../SKILL.md.

QuickDesign

The quickdesign/ directory houses a visual-design assistance plugin enabling rapid content creation pipelines. It supports automatic subtitle generation, voice continuity handling, brand-compliance checks, and UGC video asset generation. Configuration resides in quickdesign/.claude-plugin/plugin.json, with primary documentation found in quickdesign/skills/quickdesign/SKILL.md.

ELI5 (Explain Like I'm 5)

Found in eli5/, this educational plugin allows Claude to deconstruct complex topics into simple, digestible explanations suitable for non-technical audiences. The manifest at eli5/.claude-plugin/plugin.json registers the plugin with Claude's ecosystem, while eli5/skills/eli5/SKILL.md documents the simplification skill interface for end users.

Plugin Structure and Manifest Files

Every in-tree plugin adheres to a strict directory convention that enables Claude Code and Claude Cowork to discover and load functionality automatically without external configuration.

The .claude-plugin/ hidden directory within each plugin root contains two critical metadata files:

• plugin.json — The primary manifest defining the plugin's name, description, version, and available capabilities
• marketplace.json — Metadata specific to the community marketplace listing and distribution

The skills/ subdirectory contains individual tool definitions, typically structured as skills/<skill-name>/SKILL.md files that describe available functions, parameters, and usage examples for Claude's reasoning engine.

Installation and Usage Examples

Developers can integrate these in-tree plugins using the Claude CLI or programmatically via the Claude SDK. The following examples demonstrate installation patterns and runtime invocation for each plugin.

Installing from the community marketplace via the Claude CLI:

# Add the community marketplace (one-time setup)

claude plugin marketplace add anthropics/claude-plugins-community

# Install specific in-tree plugins

claude plugin install quickdesign@claude-community
claude plugin install tres-finance-plugin@claude-community
claude plugin install eli5@claude-community

Python example for programmatic marketplace management:

# Example: Adding the QuickDesign plugin via Python subprocess

import subprocess

# Add the community marketplace

subprocess.run([
    'claude', 'plugin', 'marketplace', 'add', 
    'anthropics/claude-plugins-community'
])

# Install QuickDesign from the in-tree collection

subprocess.run([
    'claude', 'plugin', 'install', 
    'quickdesign@claude-community'
])

JavaScript SDK integration for the ELI5 plugin using the ClaudeClient:

// Example: Invoking the ELI5 plugin from a Node.js integration
const { ClaudeClient } = require('claude-sdk');

async function simplifyExplanation(topic) {
  const client = new ClaudeClient({ apiKey: process.env.CLAUDE_API_KEY });
  const response = await client.chat({
    messages: [
      { role: 'user', content: `@eli5 ${topic}` }
    ],
    plugins: ['eli5']
  });
  return response.content;
}

simplifyExplanation('What is quantum entanglement?')
  .then(answer => console.log(answer));

Manual installation workflow for Claude Cowork:

# 1. Launch Claude Cowork interface

# 2. Navigate to the Plugins panel

# 3. Search for "Tres Finance" and select Install

# 4. Invoke via natural language prompt:

#    "Upload my wallet CSV to the Tres Finance plugin for transaction validation"

Key Source Files and Implementation Details

Understanding the specific file paths within each plugin enables developers to extend functionality, debug integration issues, or contribute modifications to the in-tree collection.

Tres Finance Plugin stores its core manifest at tres-finance-plugin/.claude-plugin/plugin.json, which registers the plugin's wallet upload and transaction validation capabilities with Claude. Individual skill documentation resides in tres-finance-plugin/skills/.../SKILL.md, detailing the bookkeeping utilities and cost-basis calculation tools available to Claude.

QuickDesign maintains its metadata in quickdesign/.claude-plugin/plugin.json and pipeline documentation in quickdesign/skills/quickdesign/SKILL.md. These files collectively define the visual-design automation tools, brand-compliance checks, and subtitle generation parameters.

ELI5 uses eli5/.claude-plugin/plugin.json for plugin registration and eli5/skills/eli5/SKILL.md to document the explanation-generation interface. This structure ensures Claude can locate and execute the simplification logic when users invoke the @eli5 command prefix.

Summary

• The anthropics/claude-plugins-community repository ships with three in-tree plugins: Tres Finance Plugin, QuickDesign, and ELI5.
• Each plugin contains a .claude-plugin/plugin.json manifest and marketplace.json for community marketplace distribution.
• Plugin capabilities are defined in skills/<name>/SKILL.md files that Claude uses to understand available tools and their parameters.
• Installation supports both CLI commands (claude plugin install) and manual marketplace browsing in Claude Cowork.
• All three plugins follow identical directory structures, making it straightforward to add new in-tree contributions that Claude discovers automatically.

Frequently Asked Questions

What distinguishes in-tree plugins from external Claude plugins?

In-tree plugins live directly within the anthropics/claude-plugins-community repository source tree and are version-controlled alongside the core project. External plugins typically reside in separate repositories and are imported via URL references or package registries rather than being bundled in the main codebase.

How does Claude locate the plugin.json manifest for in-tree plugins?

Claude Code and Claude Cowork scan for the hidden .claude-plugin/ directory within each plugin folder. The plugin.json file inside this directory contains the registration metadata that Claude uses to identify the plugin name, version, and available skill handlers.

Can I modify the SKILL.md files in the in-tree plugins?

Yes, the skill markdown files located at paths like eli5/skills/eli5/SKILL.md or quickdesign/skills/quickdesign/SKILL.md define how Claude interprets each tool's purpose and parameters. Modifying these files changes the plugin's behavior, though changes should follow the repository's contribution guidelines and be submitted via pull request for in-tree plugins.

Are these plugins available in the Claude marketplace immediately?

The in-tree plugins are distributed through the community marketplace via the marketplace.json files found in each .claude-plugin/ directory. Users can install them immediately using claude plugin install after adding the anthropics/claude-plugins-community marketplace source to their Claude client configuration.

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