hashgraph-online/awesome-codex-plugins / plugins/avivsinai/bitbucket-cli/skills/bkt
bkt
VerifiedOperate 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.
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
- pipelines or variables
- Bitbucket Cloud Issues no longer exist (Atlassian removed them in August 2026); route issue tracking to Jira.
- 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.
- Every bkt build carries its Cloud browser-OAuth consumer, so
bkt auth login --kind cloud --webneeds 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
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |