Safely publish skills to your platform's registry. Sanitize, format, verify, and publish without modifying your local files.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add clawic/skills --skill skill-publish --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skill Publish?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/clawic-skill-publish)More formats (shields.io, HTML) on the badges page.
---
name: Skill Publish
slug: skill-publish
version: 1.0.0
description: Safely publish skills to your platform's registry. Sanitize, format, verify, and publish without modifying your local files.
homepage: https://clawic.com/skills/skill-publish
metadata:
clawdbot:
emoji: 📤
displayName: Skill Publish
---
## Publish Skills Safely
Transform any knowledge into a publishable skill. Sanitize personal data, format correctly, verify before publishing.
**Key principle:** Never modify user's original files. Create clean publish-ready version separately.
**References:**
- `sanitize.md` — Security checklist and personal data removal
- `transform.md` — Convert any format to proper skill structure
- `verify.md` — Pre-publish verification process
---
### When to Use
- User wants to publish an existing skill/instructions to a registry
- User wants to share knowledge they've developed locally
- User has content in any format that should become a public skill
### The Process
1. **Understand** — What knowledge/skill exists? Where is it?
2. **Transform** — Convert to proper skill format (see `transform.md`)
3. **Sanitize** — Remove personal/dangerous content (see `sanitize.md`)
4. **Verify** — Confirm with user before publishing (see `verify.md`)
5. **Publish** — Only after explicit approval, using whichever publish command the target platform provides (each registry has its own CLI or web flow) — see `verify.md`
### Critical Rules
⚠️ **Never modify original files** — Create separate publish version
⚠️ **Never publish without sanitization** — Check `sanitize.md`
⚠️ **Never publish without user approval** — Always verify first
⚠️ **When in doubt, include more** — User can remove, harder to add later
### Asking the User
Before transforming, clarify:
- What should be PUBLIC vs kept private?
- Any specific names/references to remove?
- Target audience (beginners, experts, specific domain)?
- Desired slug/name for the target registry? Check it doesn't collide with a slug you already own there — naming rules vary by platform.
---
**Always run `sanitize.md` checklist before any publish.**
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!