# Publish Agent Skills Across Marketplaces

Skill marketplaces accept different inputs and expose separate review, package, and listing states. This guide helps prepare scoped releases and verify each result with traceable evidence.

## Install

```bash
npx skillstore add hunxuankai/skill-publishing-guide
```

## Metadata

- Status: approved
- Slug: hunxuankai-skill-publishing-guide
- Version: 1.2.3
- Author version: 1.2.3
- Skillstore revision: r1
- Version status: valid
- Tree hash: f74adb0327896f0d1d9c7fd7b95b7cf8cb823e92e8a5453c1402f04c67721d35
- Author: hunxuankai
- GitHub username: hunxuankai
- License: MIT
- Repository: https://github.com/hunxuankai/skill-publishing-guide/tree/38ce8f6dd2a2f9a9a475cc60d093deea13551d9b/skills/skill-publishing-guide
- Ref: c993c6abcbffafea2683d7748b53b3dfaf438415
- 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: network, external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/hunxuankai-skill-publishing-guide
- Manifest: https://skillstore.pages.dev/api/skills/hunxuankai-skill-publishing-guide/manifest

## Capabilities

- Guide publication through GitHub, skills.sh, Tencent SkillHub, SkillHub.club, Skillstore, ClawHub, VoltAgent, and Agensi.
- Define a single skill release scope and prepare channel-specific URL or ZIP inputs with source references and hashes.
- Prepare platform summaries and full overview text that reflect actual functionality, dependencies, system support, and verification limits.
- Guide authorized CLI and browser workflows while separating local preparation, remote drafts, uploads, review, and public release.
- Compare public versions, available package files, summaries, and overview text against the selected release.
- Produce submission records and recovery steps for unknown results, duplicate versions, filtered files, and stale listings.

## Use Cases

- Prepare a first skill release: Identify the correct submission route and prepare a complete skill package, summary, and overview before any upload.
- Coordinate marketplace updates: Track source commits, author versions, platform revisions, package hashes, and listing changes across authorized channels.
- Verify a reported publication: Check public identity, target version, available files, and listing text without treating upload receipts as proof of publication.

## Prompt Templates

### Choose a publishing route

```
Explain how to publish [skill path] to [platform]. Identify required inputs and checks. Do not upload, log in, or change remote state.
```

### Prepare local release materials

```
Prepare [skill path] at [source ref] for [platform]. Check dependencies, license, package layout, summary, and full overview. Keep all work local.
```

### Publish an authorized update

```
Update [namespace/slug] on [platform] using [source ref] and author version [version]. I authorize uploading and publishing this skill only. Preserve visibility and license. Check package and listing content before submission, then report each verification result.
```

### Investigate an uncertain submission

```
Investigate [submission ID or URL] after [timeout or conflict]. Use read-only checks first. Correlate identity, version, source, package, summary, and overview. Report evidence and unknowns. Do not retry, rename, bump versions, or recreate entries without authorization.
```

## Limitations

- The skill provides Markdown guidance and templates, not a bundled publishing service or executable automation.
- Publishing requires appropriate tools, authentication, permissions, and user authorization for external changes.
- Platform rules and interfaces can change; documented observations require confirmation before use.
- The guide cannot guarantee acceptance, review timing, complete file delivery, or automatic listing synchronization.

## Best Practices

- Fix the selected skill, source ref, author version, license, and authorized channels before building or submitting materials.
- Recheck current official rules and compare the actual upload file list with required resources before remote writes.
- Record package, version, summary, and overview results separately, with evidence dates and explicit unknowns.

## Anti Patterns

- Uploading an entire repository when the user selected only one skill.
- Treating an upload receipt, successful command, or visible old version as proof that the complete new release is public.
- Retrying ambiguous writes by renaming, incrementing versions, deleting entries, or repeating uploads without checking existing records.

## Security Audit

- Audited at: 2026-11-08T06:55:09.601\+00:00
- Summary: All 19 static findings are false positives involving readable multilingual documentation, Markdown formatting, placeholder links, or authorized publishing commands. The guide explicitly limits remote writes, protects credentials, and separates preparation from publication. No evidence found of prompt injection, credential exfiltration, or concealed payloads in the reviewed files.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 1
- Popularity score: 0