# Publish Skills to Public Marketplaces

Publishing a skill safely requires audit, packaging, repository setup, and marketplace-specific submission steps. This skill gives Codex, Claude, and Claude Code users a repeatable public release workflow.

## Install

```bash
npx skillstore add sliense-ysd/skill-marketplace-publisher
```

## Metadata

- Status: approved
- Slug: sliense-ysd-skill-marketplace-publisher
- Skillstore revision: r1
- Version status: missing
- Tree hash: 0a75298af3cd528af1556ce2ed3fbe660ba4d798d746f7a56e5591da4a9ce6c7
- Author: Sliense-ysd
- GitHub username: Sliense-ysd
- License: MIT
- Repository: https://github.com/Sliense-ysd/skill-marketplace-publisher-public/tree/main/skills/skill-marketplace-publisher/
- Ref: 3e4b6c31a74a3bd1a291c98cf585d720cb9fbc88
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: env\_access, network, external\_commands, filesystem
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/sliense-ysd-skill-marketplace-publisher
- Manifest: https://skillstore.pages.dev/api/skills/sliense-ysd-skill-marketplace-publisher/manifest

## Capabilities

- Runs a local public-safety audit script over a skill tree.
- Guides source-versus-public-package decisions before release.
- Checks required skill metadata and referenced support files.
- Defines a clean public GitHub repository publication flow.
- Submits repository URLs to Skillstore and SkillMap feedback endpoints.

## Use Cases

- Prepare a Skillstore Submission: Audit a local skill, publish a clean GitHub repository, and submit the repository URL to Skillstore.
- Request a SkillMap Listing: Create a listing request with repository details, summary text, and contact information for SkillMap review.
- Package Private Work for Public Release: Decide when to publish source directly and when to create a sanitized public package first.

## Prompt Templates

### Audit a Skill

```
Audit this local skill for public release. Tell me whether it is safe to package or publish.
```

### Prepare a Marketplace Package

```
Prepare this skill for a public marketplace. Use public packaging if the source folder is not portable.
```

### Submit to Skillstore

```
Publish this skill to a public GitHub repository and submit the repository URL to Skillstore.
```

### Coordinate Multi-Marketplace Release

```
Audit, package, publish, and submit this skill to each verified marketplace. Record IDs, URLs, and follow-up items.
```

## Limitations

- Marketplace routes may change and need fresh verification.
- Local packaging and validation scripts must already exist.
- Marketplace acceptance is not guaranteed after submission.
- Audit output must be redacted to avoid exposing matched secrets.

## Best Practices

- Run the public-safety audit before copying files into a public repository.
- Use public packaging when a skill references private paths, secrets, or local-only assumptions.
- Record submission IDs, status URLs, timestamps, and manual follow-up items.

## Anti Patterns

- Do not publish a source folder that still contains secrets or private business logic.
- Do not claim a marketplace is supported without a verified public intake route.
- Do not submit to external endpoints before reviewing the payload and destination.

## Security Audit

- Audited at: 2026-07-09T07:49:22.215\+00:00
- Summary: Most high static secret detections are scanner regex definitions rather than embedded credentials. Real risks remain around .env scanning, redaction gaps, outbound marketplace submissions, sibling-directory command execution, and public repository publication.

## Stats

- Views: 116
- Downloads: 8
- Favorites: 0
- Popularity score: 0