bkt
Skill257 starsChanged 18 days agoMITView on GitHub
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.
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- vnord/skillstheir own version, first seen Jul 10, 2026
- mitchdowd/skillsedited, first seen Mar 30, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- mitchdowd/skills★ 118% same
Wrote their own version · 1
- vnord/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 12
Use bkt for Bitbucket Cloud and Data Center operations.
- Very specific: line 17
Run bkt --version only when installation or compatibility is uncertain.
- Distinctive: line 26
Read setup and common workflows when installing, authenticating, creating a context, or learning the main command patterns.
- Distinctive: line 32
Read only the reference for the requested command group:
- Distinctive: line 51
Never place tokens, OAuth secrets, or passwords in commands that could enter logs or committed files.
- Very specific: line 54
Every bkt build carries its Cloud browser-OAuth consumer, so bkt auth login --kind cloud --web needs no setup.
- Distinctive: line 56
Before a merge or other consequential write, inspect the exact target, repository, and current checks.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
<!-- auto-generated by cmd/docgen — do not edit below this line -->- 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
<!-- end auto-generated -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.