267c4e6f06
The nvidia-skills entry was added in PR #2088 with: "source": { "source": "git-subdir", "url": "https://github.com/NVIDIA/skills.git", "path": "plugins/nvidia-skills", "ref": "main" } It's missing the required `sha` field. The marketplace validator enforces invariant I5 ("source.sha is missing or not a 40-char hex SHA") on every git-subdir source — without it, the action fails: ##[error]invariant I5: nvidia-skills: source.sha is missing or not a 40-char hex SHA This has been silently failing the "Validate Plugins" CI on every PR that touches marketplace.json since #2088 merged on 2026-05-03. Confirmed by checking the last 5 completed validate runs on main — all 5 ❌, including PR #2114 (security-guidance bump that you merged earlier today). The validator failure was getting swallowed because all the other PR-level checks (Check MCP URLs, Scan Plugins, Validate Plugin Licenses) were passing, and humans were `gh pr merge --admin`-ing through it. Fix: add the sha field pinned to the current upstream HEAD of github.com/NVIDIA/skills.git on the `main` branch. Resolved via: git ls-remote https://github.com/NVIDIA/skills.git refs/heads/main SHA: 62b685a20ac45285cafd1e22782abbed33172c17 This mirrors the shape of other git-subdir entries with both `ref` and `sha` (e.g. 42crunch-api-security-testing pins ref="v1.5.5", sha="b404d99a...", adobe-for-creativity pins ref="main", sha="8d74ee6b..."). Unblocks every in-flight PR that touches marketplace.json — including PR #2154 (security-guidance venv-deepdive) which is currently red-blocked on this. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Claude Code Plugins Directory
A curated directory of high-quality plugins for Claude Code.
⚠️ Important: Make sure you trust a plugin before installing, updating, or using it. Anthropic does not control what MCP servers, files, or other software are included in plugins and cannot verify that they will work as intended or that they won't change. See each plugin's homepage for more information.
Structure
/plugins- Internal plugins developed and maintained by Anthropic/external_plugins- Third-party plugins from partners and the community
Installation
Plugins can be installed directly from this marketplace via Claude Code's plugin system.
To install, run /plugin install {plugin-name}@claude-plugins-official
or browse for the plugin in /plugin > Discover
Contributing
Internal Plugins
Internal plugins are developed by Anthropic team members. See /plugins/example-plugin for a reference implementation.
External Plugins
Third-party partners can submit plugins for inclusion in the marketplace. External plugins must meet quality and security standards for approval. To submit a new plugin, use the plugin directory submission form.
Plugin Structure
Each plugin follows a standard structure:
plugin-name/
├── .claude-plugin/
│ └── plugin.json # Plugin metadata (required)
├── .mcp.json # MCP server configuration (optional)
├── commands/ # Slash commands (optional)
├── agents/ # Agent definitions (optional)
├── skills/ # Skill definitions (optional)
└── README.md # Documentation
Skill-bundle plugins
When a plugin's source repository ships skills (SKILL.md files) without a .claude-plugin/plugin.json manifest, the marketplace entry can declare the skills directly using strict: false and an explicit skills array.
{
"name": "example-bundle",
"description": "Brief description of the bundled skills.",
"author": { "name": "Author Name" },
"category": "development",
"source": {
"source": "git-subdir",
"url": "https://github.com/example-org/sdk.git",
"path": "packages/agent-skills",
"ref": "main",
"sha": "<commit sha>"
},
"strict": false,
"skills": [
"./skill-a",
"./skill-b",
"./skill-c"
],
"homepage": "https://github.com/example-org/sdk"
}
Each path in skills is relative to source.path and points at a directory containing a SKILL.md. Paths can reach deeper than a single level — for example, ["./libA/skill-1", "./libB/skill-2"] exposes a curated subset across multiple library subdirectories. Each skill is registered as <plugin-name>:<skill-name> in Claude Code.
For the underlying schema, see Strict mode in the marketplace documentation.
License
Please see each linked plugin for the relevant LICENSE file.
Documentation
For more information on developing Claude Code plugins, see the official documentation.