Skill Matrix Publisher Free

Problem

When syncing one SKILL.md to multiple platforms, the main risk is not publishing, but publishing the wrong state. A “update” may hit a create endpoint, duplicate entries may appear, platform domains, token prefixes, and ID formats may be confused, versions may increase without a changelog, and deletion may match the wrong Skill. This skill turns those issues into explicit checks to prevent accidental creation, duplication, and deletion during matrix distribution.

How It Works

It can run as a guided chat assistant or a local CLI. Key capabilities include:
- Six-channel publishing: supports Tencent SkillHub personal/team, XiaLiao, XiaYou SkillHub, GitHub, and ClawHub, using API calls, browser upload, or git push as needed.
- Pre-operation probing: before create, update, or delete, it checks whether a matching slug or name exists, then reports existence, version, and status for user confirmation.
- Create vs update separation: creation uses platform create/publish endpoints; updates use the correct upsert or overwrite path and sync both version and changelog.
- Credential handling: after the user provides api_key, token, invitation code, or related fields once, the skill stores them by platform and avoids asking again.
- Platform adaptation: it handles category mapping, packaging, and platform quirks such as avoiding non-ASCII tags on ClawHub, using slug for circle on XiaLiao, and manual team uploads for Tencent SkillHub.

Boundaries & Notes

Best for maintainers who already have a publishable Skill package and need cross-platform versioning. Confirm the target domain and account type first; skillhub.cn and aiskillhub.vip do not share tokens or ID formats. For deletion, prefer dry-run preview and verify slug, ID, and version before execution. If a platform cannot list existing entries, do not publish blindly—ask for evidence such as screenshots, skillId, or status confirmation.