← ClaudeAtlas

promote-to-marketplacelisted

Move a personal skill or hook from ~/.claude/ into the unifylabs-workflow marketplace plugin so the rest of the team gets it. Use when the user says "/promote-to-marketplace <name>" or wants to share a skill/hook they created locally.
unifylabs-dev/unify-kit · ★ 0 · Code & Development · score 60
Install: claude install-skill unifylabs-dev/unify-kit
# promote-to-marketplace Promotes a personal skill or hook from `~/.claude/` into the `unifylabs-workflow` plugin inside the `unify-kit` marketplace, and creates a symlink back so the user's normal `~/.claude/...` workflow keeps working. ## When to use - The user has created a skill in `~/.claude/skills/<name>/` that's proven useful and should be shared - The user has created a hook in `~/.claude/hooks/<name>.sh` that should run for the whole team - The user types `/promote-to-marketplace <name>` (with or without a `--hook` flag) ## Inputs - **`<name>`** (required) — the skill directory name or hook filename (without `.sh`) under `~/.claude/` - **`--hook`** (optional flag) — treat the name as a hook instead of a skill (default: skill) ## Preconditions to check before doing anything 1. The unify-kit clone exists at `~/Projects/unify-kit/`. If not, abort with an instruction to clone it first (`gh repo clone unifylabs-dev/unify-kit ~/Projects/unify-kit`). 2. The named source exists at `~/.claude/skills/<name>/` (or `~/.claude/hooks/<name>.sh`). 3. The source is NOT already a symlink into the marketplace (= already promoted). 4. The name is NOT in `~/.claude/.personal-skills` (= explicitly opted out of sharing). 5. The unify-kit working tree is clean (`git -C ~/Projects/unify-kit status` shows no uncommitted changes) — if not, ask the user to commit/stash first. ## What to do 1. **Move** the source into the plugin: - Skill: `mv ~/.claude/skills/<name> ~/Projects/unify