# AI use cases for Claude Plugins Official (anthropics/claude-plugins-official)

Repo: [anthropics/claude-plugins-official](https://github.com/anthropics/claude-plugins-official) | Use cases: 4 | Page: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/

A curated, Anthropic-managed marketplace of Claude Code plugins, split into internal plugins and third-party plugins.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Install a vetted plugin from the official marketplace: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/install-marketplace-plugin/
- Build a plugin in the standard layout for submission: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/build-external-plugin-for-submission/
- Publish existing SKILL.md files as a marketplace bundle: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/publish-skill-bundle-without-manifest/
- Change a published plugin's label without breaking installs: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/rename-plugin-without-breaking-installs/

## How to install a vetted plugin from the official marketplace with Claude Plugins Official

Repo: [anthropics/claude-plugins-official](https://github.com/anthropics/claude-plugins-official) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README

Add a ready-made Claude Code plugin from the official directory in one command.

**Who it is for:** A Claude Code user who needs a capability that an official plugin already provides and wants to avoid building it.

**The problem:** Finding and installing a reliable Claude Code plugin takes time when you have to search for it by hand.

**The outcome:** The chosen plugin is installed from the Claude Plugins Official marketplace and ready to use in Claude Code.

### Steps

1. Open Claude Code and run `/plugin > Discover` to browse the marketplace, or note the plugin name you want.
2. Read the plugin's homepage and confirm you trust it before installing.
3. Run `/plugin install {plugin-name}@claude-plugins-official`, replacing {plugin-name} with the plugin you chose.
4. Open `/plugin` to confirm the plugin is listed as installed.

### Prompt to paste into your agent

```text
Using the anthropics/claude-plugins-official repo, install the plugin <plugin-name> with `/plugin install <plugin-name>@claude-plugins-official` in Claude Code. Report the install result and the plugin's homepage URL. Verify the plugin appears under `/plugin` before reporting success.
```

### Caveat

The README says Anthropic does not control what MCP servers, files, or other software a plugin includes, so the install step does not guarantee the plugin works as intended.

Risk, remote script: Plugins can include MCP servers and other software that Anthropic does not control or verify, so review the plugin's homepage before installing or updating it.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/install-marketplace-plugin/

## How to build a plugin in the standard layout for submission with Claude Plugins Official

Repo: [anthropics/claude-plugins-official](https://github.com/anthropics/claude-plugins-official) | Difficulty: Intermediate | Time: 2 hours | Basis: From the README

Scaffold a Claude Code plugin with the required manifest and submit it for review.

**Who it is for:** A third-party developer or partner who wants a Claude Code plugin included in the marketplace.

**The problem:** Getting a plugin accepted requires the correct folder structure and metadata before the submission form can be used.

**The outcome:** A plugin folder with a valid plugin.json manifest, documentation, and optional commands, agents, or skills, ready for the submission form.

### Steps

1. Create a folder named plugin-name with a .claude-plugin/plugin.json file (required metadata).
2. Add optional folders as needed: .mcp.json, commands/, agents/, or skills/.
3. Write a README.md that documents the plugin.
4. Review /plugins/example-plugin in the repo as a reference implementation.
5. Submit the plugin through the plugin directory submission form at https://clau.de/plugin-directory-submission. External plugins must meet quality and security standards for approval.

### Prompt to paste into your agent

```text
In the anthropics/claude-plugins-official repo, scaffold a plugin folder named <plugin-name> that follows the standard structure with .claude-plugin/plugin.json and README.md, using /plugins/example-plugin as the reference. Output the list of created files. Verify that .claude-plugin/plugin.json exists and is valid JSON before preparing the submission.
```

### Caveat

External plugins must meet the marketplace's quality and security standards, and the README does not describe the review timeline or criteria in detail.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/build-external-plugin-for-submission/

## How to publish existing SKILL.md files as a marketplace bundle with Claude Plugins Official

Repo: [anthropics/claude-plugins-official](https://github.com/anthropics/claude-plugins-official) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

List skill folders from a source repo in a marketplace entry with strict set to false.

**Who it is for:** A maintainer of an SDK or skills repo who ships SKILL.md files but no plugin.json manifest.

**The problem:** Skills in a source repo cannot be offered through the marketplace without a manifest unless the marketplace entry declares them directly.

**The outcome:** A marketplace entry that exposes a chosen set of skills from the source repo, each registered in Claude Code.

### Steps

1. Confirm each skill folder you want to publish contains a SKILL.md file.
2. Create a marketplace entry with name, description, author, category, and a git-subdir source that gives the url, path, ref, and sha.
3. Set "strict": false and list the skill paths in the skills array, relative to source.path.
4. Add a homepage URL and submit the entry for review.
5. Confirm each skill appears in Claude Code after the entry is accepted.

### Prompt to paste into your agent

```text
Using the strict false skill-bundle format in the anthropics/claude-plugins-official README, draft a marketplace entry for the skills at <skill-path> in <source-repo-url>. Output the JSON entry. Verify that every path in the skills array points to a directory containing a SKILL.md file.
```

### Caveat

The README example for the source sha field shows a blank value, so confirm the required value against the marketplace documentation before submitting.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/publish-skill-bundle-without-manifest/

## How to change a published plugin's label without breaking installs with Claude Plugins Official

Repo: [anthropics/claude-plugins-official](https://github.com/anthropics/claude-plugins-official) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Update displayName or add a renames entry so existing users keep working.

**Who it is for:** A marketplace maintainer who needs to change a published plugin's name or label.

**The problem:** Changing the name field of a published plugin makes existing installs fail with a plugin-not-found error.

**The outcome:** The plugin keeps working for current users, with its UI label updated or its old slug migrated to the new name.

### Steps

1. Leave the name field unchanged, since it is an immutable slug for published plugins.
2. To change the UI label, set or update displayName in the marketplace entry.
3. If a rename is unavoidable, add an entry to the top-level renames map in .claude-plugin/marketplace.json, for example "old-name": "new-name".
4. Verify that the old slug is mapped and the new name is correct before merging.

### Prompt to paste into your agent

```text
In the anthropics/claude-plugins-official repo, update the marketplace entry for <plugin-name> so its UI label changes to <new-label> by setting displayName, without changing name. Output the diff. Verify that the name field is unchanged.
```

### Caveat

The README says the Claude Code plugin loader rewrites old slugs on the user's next sync, but it does not say how long migration takes or what happens if a user is offline.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/anthropics-claude-plugins-official/rename-plugin-without-breaking-installs/