Set up plugin marketplace structure

[fusionfx1]

Sets up repository structure for plugin marketplace. Moves all plugin content to plugins/everything-claude-code/ and adds marketplace.json with proper schema.

Summary by CodeRabbit

• New Features

  • Registered the "everything-claude-code" plugin for enhanced agents and skills.

• Chores

  • Updated plugin metadata and added a top-level schema and description for clearer registry info.
  • Switched plugin source to reference its GitHub repository.
  • Added a plugin configuration entry including author information and basic metadata; removed legacy homepage/repository/license/tags fields.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Replaces and restructures plugin marketplace metadata: adds top-level "$schema" and "description", removes the legacy "metadata" block, changes the plugin "source" from "." to a GitHub object, and removes several plugin-level fields. Also adds plugins/everything-claude-code/.claude-plugin/plugin.json with name, description, and author.

Changes

Cohort / File(s)	Summary
Marketplace manifest \.claude-plugin/marketplace.json	Added top-level "$schema" and "description"; removed top-level "metadata" (and its description, version); replaced plugin entry "source": "." with "source": { "source": "github", "repo": "affaan-m/everything-claude-code" }; removed "homepage", "repository", "license", "keywords", "category", "tags", and "author" fields from plugin entry.
Plugin config (new) plugins/everything-claude-code/\.claude-plugin/plugin.json	New file added containing plugin metadata: name, description, and author (name and email). No behavioral code changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through JSON, tidy and bright,
New schema and source now gleam in the light,
A plugin's small card with author in tow,
Registry refreshed — ready to go! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Set up plugin marketplace structure' directly aligns with the PR's main objective to restructure the repository and prepare a plugin marketplace by adding marketplace.json and plugin.json files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.claude-plugin/marketplace.json:
- Line 7: Replace the placeholder email value "[email protected]" in the
marketplace.json "email" property with a real contact address; open the
.claude-plugin/marketplace.json file, locate the "email" field and set it to a
valid, monitored email (e.g., support or maintainer address) before publishing.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Placeholder email should be replaced.

The email [email protected] uses the reserved example.com domain, which is a placeholder. Consider replacing it with a valid contact email before publishing.

🤖 Prompt for AI Agents

In @.claude-plugin/marketplace.json at line 7, Replace the placeholder email
value "[email protected]" in the marketplace.json "email" property with a real
contact address; open the .claude-plugin/marketplace.json file, locate the
"email" field and set it to a valid, monitored email (e.g., support or
maintainer address) before publishing.

[affaan-m]

Thanks for the contribution! We've already set up the plugin structure differently - the plugin now works with content at the repo root. Appreciate the effort! 🙏