bkt — Claude Code skill: what it does, how to install
Teaches agents to manage Bitbucket Cloud and Data Center via the bkt CLI. It guides pull requests, branch checks, pipelines, and safe repository mutations.
npx skills add avivsinai/bitbucket-cli --skill bkt -a claude-codeWhat bkt does
This skill routes AI coding assistants through the bkt command-line tool to manage Bitbucket Cloud and Data Center instances. It separates read-only operations like checking branch statuses from mutations such as merges, deletions, or pipeline reruns. Before performing any write, the agent must inspect the repository target and check statuses first.
Every bkt build packages an OAuth consumer for browser login, so running bkt auth login --kind cloud --web requires no manual credentials setup. Plain text tokens and secrets are forbidden in command arguments. For scripting, the skill directs the agent toward --json, --yaml, --jq, or --template output formats.
Cloud and Data Center enforce different feature sets. Project permissions and server admin rules exist only on Data Center, while pipelines and variables belong to Cloud. The agent identifies the active context upfront so it does not trigger unsupported commands across platforms.
What it helps with
- manage pull requests and inspect review statuses
- trigger and monitor Bitbucket Cloud pipelines
- audit branch permissions and administrative settings in Data Center
- run structured Bitbucket queries with JSON and jq output
Example prompts for the agent
- List open pull requests for this repository using bkt
- Check the latest Bitbucket Cloud pipeline run status
- Log in to Bitbucket with bkt auth login --kind cloud --web
How to install bkt
1Skills CLI (Vercel)
npx skills add avivsinai/bitbucket-cli --skill bkt -a claude-code2Manually: put the files in place
~/.claude/skills/bkt/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/bkt/
1Skills CLI (Vercel)
npx skills add avivsinai/bitbucket-cli --skill bkt -a codex2Manually: put the files in place
.agents/skills/bkt/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add avivsinai/bitbucket-cli --skill bkt -a cursor2Manually: put the files in place
.cursor/skills/bkt/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install avivsinai/bitbucket-cli bkt2Manually: put the files in place
.github/skills/bkt/SKILL.md1Skills CLI (Vercel)
npx skills add avivsinai/bitbucket-cli --skill bkt -a gemini-cli2Platform CLI
gemini skills install https://github.com/avivsinai/bitbucket-cli --path skills/bktManually: put the files in place
.devin/skills/bkt/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add avivsinai/bitbucket-cli --skill bkt -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about bkt
How to install bkt in Claude Code?
Run npx skills add avivsinai/bitbucket-cli --skill bkt -a claude-code. The skill will be placed in ~/.claude/skills/bkt/SKILL.md.
What does the bkt skill do?
It enables agents to inspect and modify Bitbucket repositories, branches, pull requests, and pipelines using the bkt CLI. The skill also enforces safety boundaries before destructive actions like merges or deletions.
How does bkt handle Bitbucket Cloud vs Data Center differences?
Data Center handles projects and permissions, while Bitbucket Cloud manages pipelines and variables. The skill instructs the agent to check the active context before running platform-specific commands.
Source text
SKILL.md · MIT
--- name: bkt version: 0.37.0 description: Operate Bitbucket Cloud or Data Center repositories, pull requests, branches, pipelines, permissions, and webhooks with bkt. Use when a request names Bitbucket or bkt; confirm the platform before platform-specific commands. metadata: short-description: Bitbucket CLI for repos, PRs, branches compatibility: claude-code, codex-cli --- # 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](rules/guide.md) when installing, authenticating, creating a context, or learning the main command patterns. For config-free CI or containers, read [headless authentication](rules/headless.md). ## Route to the command reference Read only the reference for the requested command group: - [pull requests](rules/pr.md), [repositories](rules/repo.md), [branches](rules/branch.md), [commits](rules/commit.md), or [statuses](rules/status.md) - [pipelines](rules/pipeline.md) or [variables](rules/variable.md) - Bitbucket Cloud Issues no longer exist (Atlassian removed them in August 2026); route issue tracking to Jira. - [Data Center administration](rules/admin.md), [projects](rules/project.md), or [permissions](rules/perms.md) - [authentication](rules/auth.md), [contexts](rules/context.md), [webhooks](rules/webhook.md), [extensions](rules/extension.md), [MCP](rules/mcp.md), [skills](rules/skill.md), or [raw API](rules/other.md) ## 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. - Every bkt build carries its Cloud browser-OAuth consumer, so `bkt auth login --kind cloud --web` needs no setup. - Before a merge or other consequential write, inspect the exact target, repository, and current checks. Report the resulting URL or identifier. ## References <!-- auto-generated by cmd/docgen — do not edit below this line --> - [admin](rules/admin.md) — Administrative operations for Bitbucket *(DC)* - [auth](rules/auth.md) — Manage Bitbucket authentication credentials - [branch](rules/branch.md) — Inspect and manage branches - [commit](rules/commit.md) — Work with commits - [context](rules/context.md) — Manage Bitbucket CLI contexts - [extension](rules/extension.md) — Manage bkt CLI extensions - [mcp](rules/mcp.md) — Model Context Protocol server for agents - [perms](rules/perms.md) — Manage Bitbucket permissions *(DC)* - [pipeline](rules/pipeline.md) — Run and inspect Bitbucket Cloud pipelines *(Cloud)* - [pr](rules/pr.md) — Manage pull requests - [project](rules/project.md) — Work with Bitbucket projects *(DC)* - [repo](rules/repo.md) — Work with Bitbucket repositories - [skill](rules/skill.md) — Install and manage agent skills - [status](rules/status.md) — Inspect commit and pull request statuses - [variable](rules/variable.md) — Manage pipeline variables *(Cloud)* - [webhook](rules/webhook.md) — Manage Bitbucket webhooks - [other](rules/other.md) — api <!-- end auto-generated -->
© avivsinai · MIT · avivsinai/bitbucket-cli