Agent skill · software engineering · avivsinai
bkt
Operate Bitbucket Cloud or Data Center repositories, pull requests, branches, issues, pipelines, permissions, and webhooks with bkt. Use when a request names Bitbucket or bkt; confirm the platform before platform-specific commands.
Why this skill is useful
Adds specific commands and workflows for managing Bitbucket repositories that the AI wouldn't reliably generate on its own.
What it needs
Requires brew, go, scoop installed locally. Requires bitbucket account access. About 2k tokens when loaded. Last updated 2026-08-05. 180 stars on the source repository.
What this skill does
Bitbucket CLI (bkt) Use bkt for Bitbucket Cloud and Data Center operations. Prefer structured --json, --yaml, --jq, or --template output for automation. Start with the requested operation Run bkt --version only when installation or compatibility is uncertain. Run bkt auth status when the command needs authentication or the active platform and context are unknown. Do not make setup a prerequisite for an already configured read-only request. Cloud and Data Center have different feature sets. Determine the platform from the active context or ask when it cannot be inferred. Do not suggest a Cloud-only command for Data Center, or the reverse. Read setup and common workflows when installing, authenticating, creating a context, or learning the main command patterns. For config-free CI or containers, read headless authentication. Route to the command reference Read only the reference for the requested command group: pull requests, repositories, branches, commits, or statuses Cloud issues, pipelines, or variables Data Center administration, projects, or permissions authentication, contexts, webhooks, extensions, MCP, skills, or raw API Mutation and credential boundaries Listing, viewing, status, and checks are read-only. Create, edit, approve, merge, delete, rerun, or permission changes modify Bitbucket; perform them only when the user requested that change. Never place tokens, OAuth secrets, or passwords in commands that could enter logs or committed files. Use the CLI's supported credential flow or environment variables described in the auth references. Official release binaries embed the Cloud browser-OAuth consumer credentials. Do not remove that behavior as generic hardening. Source and Nix builds may require BKTOAUTHCLIENTID and BKTOAUTHCLIENTSECRET. Before a merge or other consequential write, inspect the exact target, repository, and current checks. Report the resulting URL or identifier. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills avivsinai/bkt--bf79ff