# Automate Marketplace Plugin Releases

Marketplace maintainers must release plugins without mixing versions across a shared repository. This skill guides validation, version updates, tags, pushes, and GitHub releases for one plugin at a time.

## Install

```bash
npx skillstore add emasoft/marketplace-release
```

## Metadata

- Status: approved
- Slug: emasoft-marketplace-release
- Skillstore revision: r1
- Version status: missing
- Tree hash: 146c9357165ae15ab19f2a877c4487da116b8f3ab30e6b6054e787c2e528076e
- Author: Emasoft
- GitHub username: Emasoft
- License: MIT
- Repository: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/marketplace-utils/skills/marketplace-release
- Ref: 30c73eac2afe762f6aa9c4553158769369d47351
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/emasoft-marketplace-release
- Manifest: https://skillstore.pages.dev/api/skills/emasoft-marketplace-release/manifest

## Capabilities

- Explains how to release a named plugin with patch, minor, or major version bumps.
- Guides validation of one plugin or all plugins before release.
- Describes coordinated updates to marketplace and plugin version metadata.
- Documents plugin-specific git tags and GitHub release creation.
- Shows how release notes and installation instructions are assembled.
- Covers troubleshooting for common release errors.

## Use Cases

- Release One Plugin: Create a patch, minor, or major release for one plugin while leaving other plugins unchanged.
- Validate Before Publishing: Run validation checks before publishing a plugin update to reduce failed releases.
- Maintain Version Documentation: Keep marketplace README version tables and plugin badges aligned with each release.

## Prompt Templates

### List Plugin Versions

```
Show me how to list every plugin in this marketplace and summarize the current versions before I choose a release target.
```

### Prepare Patch Release

```
Guide me through a patch release for the selected plugin. Include validation, version changes, tag naming, and confirmation points.
```

### Create Minor Release Notes

```
Help me prepare a minor plugin release with concise release notes, installation instructions, and a changelog summary.
```

### Audit Multi-Plugin Release Impact

```
Review this marketplace release plan and identify which files, tags, README sections, and GitHub release steps should change for one plugin only.
```

## Limitations

- Requires the referenced release and validation scripts to exist in the marketplace project.
- Requires GitHub CLI authentication and access to push tags and releases.
- Does not replace human review of generated release notes or repository changes.
- Does not provide the release script source code in this skill package.

## Best Practices

- Review the working tree and generated release notes before confirming a release.
- Validate the target plugin before changing versions, tags, or remote releases.
- Use plugin-specific tags so independent plugin versions remain clear.

## Anti Patterns

- Do not release from a plugin subdirectory when the script expects the marketplace root.
- Do not publish with unresolved validation errors or unclear release notes.
- Do not use a shared marketplace version when plugins are released independently.

## Security Audit

- Audited at: 2026-07-05T14:37:51.163\+00:00
- Summary: No evidence of prompt injection, credential exfiltration, or hidden malicious behavior was found in SKILL.md. The static findings are Markdown formatting around command examples, configuration paths, version values, and a placeholder changelog URL rather than executable Ruby or shell code.

## Stats

- Views: 221
- Downloads: 9
- Favorites: 0
- Popularity score: 0