Contributing to Claude Code Plugins banner
jeremylongshore jeremylongshore

Contributing to Claude Code Plugins

Development community intermediate

Description

Thank you for your interest in contributing to the Claude Code Plugins marketplace. With hundreds of plugins and thousands of agent skills, this is a community-driven project and contributions of all

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

Repository README

This is the README for jeremylongshore/claude-code-plugins-plus-skills, shared by 25 entries in this directory. It describes the repository, not this entry specifically.

Contributing to Claude Code Plugins

Thank you for your interest in contributing to the Claude Code Plugins marketplace. With hundreds of plugins and thousands of agent skills, this is a community-driven project and contributions of all sizes are welcome.

Quick Start

  1. Fork and clone the repository
  2. Copy a template from templates/ (minimal-plugin, command-plugin, agent-plugin, or full-plugin)
  3. Develop your plugin
  4. Run validation: ./scripts/quick-test.sh
  5. Open a PR

Ways to Contribute

  • New plugins -- Add tools, workflows, or integrations for Claude Code
  • New skills -- Create auto-activating SKILL.md files for existing or new plugins
  • Bug fixes -- Fix issues in existing plugins, the marketplace site, or the CLI
  • Documentation -- Improve READMEs, guides, or inline documentation
  • Security reports -- Responsibly disclose vulnerabilities (see Security below)
  • Plugin reviews -- Test and review open PRs from other contributors

Adding a Plugin

  1. Pick a category from plugins/ (e.g., devops, productivity, api-development) or propose a new one in your PR.
  2. Copy a template:
    cp -r templates/command-plugin plugins/[category]/my-plugin
  3. Edit .claude-plugin/plugin.json with the required fields: name, version, description, author.
  4. Add a README.md and optionally a LICENSE file (MIT recommended).
  5. Add commands/, agents/, or skills/ directories as needed.
  6. Add an entry to .claude-plugin/marketplace.extended.json.
  7. Run pnpm run sync-marketplace to regenerate the CLI-compatible catalog.
  8. Run ./scripts/quick-test.sh -- this must pass before opening a PR.

Only these fields are allowed in `plugin.json`: `name`, `version`, `description`, `author`, `repository`, `homepage`, `license`, `keywords`. CI rejects anything else.

Adding Skills

Create a `skills/[skill-name]/SKILL.md` file inside any plugin directory. Use the 2026 Schema frontmatter:

---
name: skill-name
description: |
  When to use this skill. Include trigger phrases.
allowed-tools: Read, Write, Edit, Bash(npm:*), Glob
version: 1.0.0
author: Your Name 
---

Validate your skills with:

python3 scripts/validate-skills-schema.py --skills-only

Validation Requirements

CI runs the following checks on every PR:

  • JSON validity and plugin structure -- All plugin.json files must be well-formed with required fields.
  • Catalog sync -- marketplace.extended.json and marketplace.json must be in sync. Run pnpm run sync-marketplace before committing.
  • Security scan -- No hardcoded secrets, API keys, or dangerous patterns.
  • Marketplace build and route validation -- The Astro site must build successfully with all plugin routes resolving.
  • Frontmatter validation -- Commands, agents, and skills must have valid YAML frontmatter.
  • E2E tests -- Playwright tests run on chromium, webkit, and mobile viewports.

Run `.