What problem does it solve? Keeping GitKraken CLI workspaces organized across multiple machines, organizations, and Git providers is error-prone: duplicate cloud workspaces get created, repo identities get confused by name alone, and local clones get mistaken for hosted repos. This Skill provides a disciplined procedure for discovering, grouping, renaming, syncing, and sharing gk workspaces using native CLI state instead of a hand-maintained manifest. ## Core Features & Use Cases - Native inventory discovery: Uses gk workspace list, gk workspace info, and provider repo queries to inspect existing cloud and local workspaces before making any change. - Safe workspace mutations: Applies membership deltas through gk workspace update flags (--add-repos, --remove-repos, --add-teams, --name) while preserving stable workspace IDs and existing sharing. - Multi-context operations: Handles personal GitHub, a side-business organization, and employer Azure DevOps contexts, including remote inspection of a second machine (bb-mac) over SSH. - Use Case: You want to gather all Brown work repos from your Mac into the existing Brown cloud workspace. The Skill verifies access on both hosts, resolves provider-qualified repo identities, states the membership delta, applies it, and re-syncs to confirm the result. ## Quick Start Ask the agent to list my GitKraken cloud workspaces and move the tavern-ledger repo into the Priceless Development workspace, then verify the change.
