workspace-skill

name	workspace-skill
description	Share skills with your team and collaboratively improve them through a git-based workspace registry — publish a skill, sync the team's skills, pool eval results, and walk a reviewer through promoting a skill to a stable channel. Use when the user wants to share, publish, sync, or promote team skills.
version	1.0.0
tools	["Bash","Read"]
triggers	["publish this skill to the team","sync team skills","promote to stable","share this skill"]
mutating	true

workspace-skill

Operate the team workspace registry. The registry is just a git repo the team pushes/pulls — no server. The CLI handles publish/sync/pool/promote; you handle the conversation and the review.

Publish

scripts/workspace.sh publish --registry <dir> --skill-dir <dir> --channel dev --by "<name>"

New work goes to dev first. After publishing, remind the user to commit and push the registry repo so teammates can sync.

Sync

scripts/workspace.sh sync --registry <dir> [--channel dev]

Synced skills land under ~/.skillmax/workspace/<registry>/ as trusted:false. A synced skill whose name collides with a local skill is namespaced by origin — the local skill and its history are never overwritten. Tell the user which synced skills collided. From there they can install or optimize a synced skill explicitly.

Pool eval results (collaborative optimization)

Contributors share scores so anyone can optimize against the team's pooled signal:

scripts/workspace.sh pool --registry <dir> --skill <name> --score <0..1> --by "<name>"

Pooled results are append-only (merge-friendly). Use them as the eval signal when running optimize-skill against a shared skill.

Promote (review-gated)

Promotion up the channel ladder (dev → beta → stable) requires explicit review and approval:

scripts/workspace.sh promote --registry <dir> --skill <name> --channel stable --approve --approver "<name>"

• Without --approve and an --approver, promotion is refused.
• If a different version already occupies the target channel, the CLI reports a conflict and stops — never silently merging. Resolve manually (decide which version wins) and re-run.
• Each approval is recorded as an append-only receipt in the registry.

Walk the reviewer through the diff and the pooled scores before they approve. Do not pass --approve on the user's behalf without their explicit go-ahead.

Trust note

Synced/published skills are untrusted by default. Treat registry content as you would any shared input; never auto-grant trust or execute a synced skill's code without the user's confirmation.