How to Get Support for Claude Plugin Development: Three Official Channels Explained
Developers can obtain support for Claude plugin development through three primary channels: checking individual plugin manifests for maintainer contact information, using the official submission portal for review-related issues, and consulting the README for policy questions.
The anthropics/claude-plugins-community repository serves as the public, read-only mirror of Anthropic’s community plugin marketplace. This guide explains how to get support for Claude plugin development by navigating the repository structure, parsing manifest files, and accessing the correct communication channels for technical assistance.
Understanding the Claude Plugins Community Repository
The repository operates as a curated index of community-contributed plugins. At its core, the architecture consists of a marketplace index (.claude-plugin/marketplace.json) that enumerates every published plugin alongside their metadata and support contacts.
Individual plugin bundles reside in dedicated directories, each containing a plugin.json manifest (located at .claude-plugin/plugin.json within the plugin folder). These manifests define the plugin’s name, version, entry points, and optional support contact information.
The README.md file provides the high-level workflow for using the marketplace and directs developers to the official submission portal. For policy clarifications or platform-level questions, the README links to the official anthropics/claude-plugins-official repository.
Three Ways to Get Support for Claude Plugin Development
When encountering manifest-validation errors, security-scan failures, or API usage questions, developers should follow this structured escalation path:
Contact Plugin Maintainers Directly
Many plugins expose a support or email field within their manifest. For example, the testdino plugin lists support@testdino.com in its configuration file.
To extract a support contact from any plugin manifest:
# Extract the email field from a specific plugin's manifest
jq '.email' testdino/.claude-plugin/plugin.json
This querying method allows you to programmatically retrieve maintainer contact information without manually browsing directories.
Use the Official Submission Portal
For issues regarding the review pipeline, submission status, or marketplace policies, Anthropic maintains a dedicated web form at https://clau.de/plugin-directory-submission. This portal serves as the official entry point for:
- Submitting new plugins for review
- Reporting bugs in the marketplace infrastructure
- Requesting feature enhancements
- Clarifying submission guidelines
Submissions processed through this portal enter Anthropic’s internal review pipeline, ensuring synchronized updates to the community marketplace.
Consult the Official Anthropic Documentation
For broader platform-level questions or policy clarifications, refer to the repository’s README.md and the linked official plugins repository. These resources provide authoritative guidance on security requirements, API compatibility, and marketplace governance that individual maintainers cannot modify.
Locating Support Contacts in Plugin Manifests
The marketplace.json file serves as the master directory for all community plugins. Each entry contains metadata including support channels.
Query the marketplace JSON to find support contacts programmatically:
import json
import pathlib
# Load the marketplace index
marketplace_path = pathlib.Path(".claude-plugin/marketplace.json")
data = json.loads(marketplace_path.read_text())
# Find support contact for a specific plugin
plugin = next(p for p in data["plugins"] if p["name"] == "testdino")
print(plugin.get("support", "No support contact listed"))
# Output: {'email': 'support@testdino.com'}
For the tres-finance-plugin and other community contributions, support information follows the same schema within their respective manifest files at tres-finance-plugin/.claude-plugin/plugin.json.
Working with the Marketplace CLI
When developing plugins locally, you can add the community marketplace to your Claude Code session and install specific plugins for testing:
# Add the community marketplace to your Claude Code environment
claude plugin marketplace add anthropics/claude-plugins-community
# Install a specific plugin to examine its implementation
claude plugin install tres-finance-plugin@claude-community
These commands help you inspect working examples before submitting your own plugin through the official portal.
Summary
- Check plugin manifests first: Individual
plugin.jsonfiles in.claude-plugin/directories contain maintainer email addresses (e.g.,support@testdino.com). - Use the submission portal: Visit
https://clau.de/plugin-directory-submissionfor review-related issues, bug reports, and new plugin submissions. - Query marketplace.json: The root
.claude-plugin/marketplace.jsonfile contains a master list of all plugins with their support metadata. - Refer to the README: File-level documentation in
README.mdprovides policy guidance and links to the official Anthropic repository.
Frequently Asked Questions
Where do I report a security vulnerability in a community plugin?
Report security vulnerabilities directly to the email address listed in the plugin's .claude-plugin/plugin.json manifest under the support or email field. If the plugin lacks contact information, submit the issue through the official submission portal at https://clau.de/plugin-directory-submission so Anthropic’s review pipeline can investigate.
How do I update my plugin after submitting it to the marketplace?
Submit updates through the same portal used for initial submissions (https://clau.de/plugin-directory-submission). The internal review pipeline processes version updates and synchronizes changes to the marketplace.json index after validation.
Can I get API support for Claude integration issues through this repository?
No. The anthropics/claude-plugins-community repository only handles marketplace-specific concerns. For core API integration questions, refer to the linked anthropics/claude-plugins-official repository or Anthropic’s primary developer documentation.
What information should I include when contacting a plugin maintainer?
Include your Claude Code version, the specific error message or manifest validation failure, and the output of jq '.' .claude-plugin/plugin.json from your plugin directory. This provides maintainers with complete context for troubleshooting.
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 →