mcpField
B
bkt

bkt

github.com/avivsinaiDevelopment2482.0k installsUpdated 3d ago
Repository

About bkt

bkt is a CLI skill for Bitbucket Cloud and Data Center operations. It guides command selection by platform and task, with structured output recommended for automation and clear boundaries around changes and credentials.

Key features

  1. 01Guides Bitbucket CLI command selection
  2. 02Covers Cloud and Data Center workflows
  3. 03Recommends structured output for automation
  4. 04Routes tasks to focused command references
  5. 05Sets safeguards for writes and credentials

Use cases

  1. 01Inspect repositories, branches and pull requests
  2. 02Run or inspect Cloud pipelines
  3. 03Manage authentication and CLI contexts

MCP support

The skill includes guidance for bkt's MCP server reference, which is described as a Model Context Protocol server for agents.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/avivsinai/bitbucket-cli --skill bkt

After installing, type/bktin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

rules/
admin.md
auth.md
branch.md
commit.md
context.md
extension.md
guide.md
headless.md
mcp.md
other.md
perms.md
pipeline.md
pr.md
project.md
repo.md
status.md
variable.md
webhook.md

Details

From the project README

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:

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

  • admin — Administrative operations for Bitbucket (DC)
  • auth — Manage Bitbucket authentication credentials
  • branch — Inspect and manage branches
  • commit — Work with commits
  • context — Manage Bitbucket CLI contexts
  • extension — Manage bkt CLI extensions
  • mcp — Model Context Protocol server for agents
  • perms — Manage Bitbucket permissions (DC)
  • pipeline — Run and inspect Bitbucket Cloud pipelines (Cloud)
  • pr — Manage pull requests
  • project — Work with Bitbucket projects (DC)
  • repo — Work with Bitbucket repositories
  • skill — Install and manage agent skills
  • status — Inspect commit and pull request statuses
  • variable — Manage pipeline variables (Cloud)
  • webhook — Manage Bitbucket webhooks
  • other — api

Comments

Markdown supported