Claude Code Plugin Marketplace Authoring Capability Pack Skill
Expert plugin marketplace authoring capability pack applying documented marketplace.json catalogs, /plugin marketplace add flows, private repo distribution, and supply-chain review from official plugin marketplace documentation.
Open the source and read safety notes before installing.
Safety notes
- Autonomous runs can execute tools without mid-run user input—scope paths and connectors first.
- Do not enable destructive automation without explicit approval gates.
- Review outputs as draft until a human validates evidence.
Privacy notes
- Run output may contain proprietary code and credentials.
- Summaries for external channels require redaction.
Prerequisites
- Claude Code version and plan eligibility per official documentation.
- Team policy for autonomous or shared automation workflows.
- Staging environment for safe validation.
- Human owner for production rollout approval.
Schema details
- Install type
- package
- Reading time
- 9 min
- Difficulty score
- 74
- Troubleshooting
- Yes
- Breaking changes
- No
- Scope
- Source repo
- Skill type
- capability-pack
- Skill level
- expert
- Verification
- validated
- Verified at
- 2026-06-16
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
Full copyable content
# Trigger
"Apply the claude code plugin marketplace authoring capability pack capability pack."
# Required output
1) Scope and configuration checklist
2) Risk and policy findings
3) Review matrix actions
4) Verification and rollback plan
5) Privacy-safe summaryAbout this resource
Knowledge Freshness
Grounded in official documentation verified on 2026-06-16. Behavior can change with releases; prefer live docs.
Retrieval Sources
- https://code.claude.com/docs/en/plugin-marketplaces
- https://code.claude.com/docs/en/plugins
- https://code.claude.com/docs/en/settings
- https://code.claude.com/docs/en/skills
- https://github.com/anthropics/claude-code
- https://developers.google.com/search/docs/fundamentals/creating-helpful-content
Source Verification Notes
Verified on 2026-06-16:
- Official plugin marketplace docs describe marketplace.json catalogs hosted on git repositories.
- Users add marketplaces with
/plugin marketplace addand install with/plugin install. - Private repositories can host internal-only marketplaces per documentation.
- Plugins may bundle hooks, MCP servers, and binaries that run with user privileges.
- Marketplace updates refresh via
/plugin marketplace update.
Scope Note
Community reusable workflow skill applying documented steps—not an official Anthropic product. Applies documented marketplace authoring steps—not a separate Anthropic marketplace product.
Core Workflow
- Inventory plugins and document bundled hooks, MCP, and binaries.
- Author marketplace.json with version pins and source locations.
- Host catalog in git; test add/install/update on staging machine.
- Review each plugin for supply-chain risk before publishing.
- Document rollback to remove marketplace from team configs.
Capability Scope
- Configuration and eligibility checklist.
- Risk and policy review.
- Staging verification steps.
- Rollback planning.
- Privacy-safe stakeholder summary.
Compatibility
Native
- Claude Code: use as an Agent Skill during rollout planning.
Manual Adaptation
- Generic AGENTS: apply checklist against public documentation.
Required Inputs
- Target repository or organization context.
- Current settings and policy constraints.
- Stakeholders for security review when applicable.
Production Rules
- Require human approval before production-impacting automation.
- Redact secrets from skill outputs and public tickets.
- Prefer official documentation over forum assumptions.
- Document rollback before enabling scheduled or autonomous runs.
Review Matrix
| Signal | Action |
|---|---|
| Missing repro | Block autonomous run |
| Broad tool scope | Narrow allowlists |
| Draft findings | Label unverified until human review |
| Policy drift | Align to managed settings |
Output Contract
- Scope and configuration summary.
- Findings with severity.
- Review matrix actions.
- Verification and rollback plan.
- Privacy-safe summary.
Troubleshooting
Issue: Feature unavailable on your plan
Fix: Confirm /status and official doc eligibility requirements.
Issue: Run stalls on permissions Fix: Pre-approve read tools in staging; narrow path scope.
Duplicate Check
Complements building-a-claude-code-plugin-marketplace guide; no skills capability pack with review matrix yet.
Editorial Disclosure
Independent entry by kiannidev from public documentation. No paid placement or affiliate links.
Source citations
Add this badge to your README
Show that Claude Code Plugin Marketplace Authoring Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/claude-code-plugin-marketplace-authoring-capability-pack)How it compares
Claude Code Plugin Marketplace Authoring Capability Pack Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Claude Code Plugin Marketplace Authoring Capability Pack Skill Expert plugin marketplace authoring capability pack applying documented marketplace.json catalogs, /plugin marketplace add flows, private repo distribution, and supply-chain review from official plugin marketplace documentation. Open dossier | Claude Code Deep Links Runbook Capability Pack Skill Expert Claude Code deep links runbook capability pack for building safe claude-cli:// URLs, embedding them in incident runbooks, and validating cwd, repo, and prompt parameters before users press Enter. Open dossier | Claude Code Sandboxed Bash Policy Capability Pack Skill Expert Claude Code sandboxed bash policy capability pack applying documented /sandbox enablement, filesystem and network boundaries, autoAllowBashIfSandboxed review, and fail-closed settings for autonomous shell workflows. Open dossier | Claude Code Terminal Ergonomics Capability Pack Skill Expert Claude Code terminal ergonomics capability pack for auditing multiline input, Option/Meta shortcuts, tmux passthrough, notifications, fullscreen rendering, themes, status lines, Vim mode, and custom keybindings before a user blames Claude for terminal behavior. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | skills | skills | skills | skills |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | kiannidev | kiannidev | kiannidev | YB0y |
| Added | 2026-06-16 | 2026-06-13 | 2026-06-16 | 2026-06-10 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Autonomous runs can execute tools without mid-run user input—scope paths and connectors first. Do not enable destructive automation without explicit approval gates. Review outputs as draft until a human validates evidence. | ✓Deep links pre-fill prompts but never auto-send; users must press Enter after reviewing the external-link warning. Untrusted pages can craft malicious prompts; treat every deep link like untrusted input until a human reviews it. Prompts over 1,000 characters show an extended warning; require scroll review before sending long links. Network and UNC paths are rejected for cwd; use absolute local paths or repo slugs instead. If both cwd and repo are passed, cwd wins even when the path does not exist; validate parameters deliberately. Organizations can disable handler registration with disableDeepLinkRegistration in settings or managed policy. | ✓Sandboxing reduces blast radius but does not replace human review of diffs. autoAllowBashIfSandboxed auto-approves some sandboxed commands—pair with deny rules. Missing dependencies can disable sandbox silently unless fail-closed settings apply. Network allowlists still permit egress to listed domains—document allowed hosts. | ✓This skill recommends terminal and Claude Code configuration changes; it must not edit dotfiles, keybindings, hooks, themes, or tmux settings without showing the proposed diff first. `/terminal-setup` writes terminal or editor keybindings and may adjust integrated-terminal settings; run it in the host terminal and record what changed before relying on it. tmux passthrough allows escape sequences to reach the outer terminal; enable it deliberately, especially on shared, remote, or security-sensitive hosts. Notification hooks can execute local commands when Claude needs attention; keep them simple, review command paths, and avoid hooks that send prompts or logs to third-party services. Fullscreen rendering, theme files, status lines, and keybinding changes should be treated as reversible local UI preferences, not fixes for model quality or project bugs. |
| Privacy notes | ✓Run output may contain proprietary code and credentials. Summaries for external channels require redaction. | ✓Deep link URLs embed prompt text in query parameters, which may expose incident details, customer names, or internal service names in browser history, chat logs, or ticketing systems. repo resolution uses the most recently used local clone path, which can reveal directory layout on shared screens via the welcome header. Runbooks pasted into GitHub-rendered Markdown lose clickable claude-cli:// links; code-block copies still expose full URLs to readers. Public runbooks should use redacted example prompts and generic repo slugs unless the audience is internal-only. | ✓Sandbox logs and permission prompts may capture command text and paths. Allowed write paths may include files with secrets—keep credentials out of sandbox scope. Policy summaries for external auditors should omit internal hostnames when possible. | ✓Terminal settings, tmux files, keybinding files, status line commands, and hook snippets can expose usernames, hostnames, project paths, shell aliases, secrets in environment commands, and internal repository names. Notification commands and status line scripts may reveal task names, working directories, git branches, model names, costs, or local operational context. Remote terminal and SSH notification behavior can surface session activity on a local desktop; confirm the user is comfortable with that visibility. Public PR or issue notes should summarize symptoms and redacted settings, not paste complete dotfiles, shell history, terminal transcripts, or private hook scripts. |
| Prerequisites |
|
|
|
|
| Install | — | — | — | — |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.