How do I install the Bitbucket skill?

Run npx skillmds@latest add tomevault-io/bitbucket-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bitbucket safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bitbucket?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bitbucket free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bitbucket?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bitbucket by tomevault-io — Agent Skill

Name: Bitbucket
Author: tomevault-io

Bitbucket

Interact with Bitbucket repositories and pull requests using the BITBUCKET_TOKEN environment variable. Use when working with code hosted on Bitbucket or managing Bitbucket resources via API. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

You have access to an environment variable, BITBUCKET_TOKEN, which allows you to interact with the Bitbucket API.

If you encounter authentication issues when pushing to Bitbucket (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: git remote set-url origin https://x-token-auth:${BITBUCKET_TOKEN}@bitbucket.org/username/repo.git

Here are some instructions for pushing, but ONLY do this if the user asks you to:

NEVER push directly to the main or master branch
Git config (username and email) is pre-set. Do not modify.
You may already be on a branch starting with openhands-workspace. Create a new branch with a better name before pushing.
Use the create_bitbucket_pr tool to create a pull request, if you haven't already
Once you've created your own branch or a pull request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name.
Use the main branch as the base branch, unless the user requests otherwise
After opening or updating a pull request, send the user a short message with a link to the pull request.
Do NOT mark a pull request as ready to review unless the user explicitly says so
Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:

git remote -v && git branch # to find the current org, repo and branch
git checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: bitbucket-2description: Interact with Bitbucket repositories and pull requests using the BITBUCKET_TOKEN environment variable. Use when working with code hosted on Bitbucket or managing Bitbucket resources via API. Use when this capability is needed.---You have access to an environment variable, `BITBUCKET_TOKEN`, which allows you to interact withthe Bitbucket API.<IMPORTANT>You can use `curl` with the `BITBUCKET_TOKEN` to interact with Bitbucket's API.ALWAYS use the Bitbucket API for operations instead of a web browser.ALWAYS use the `create_bitbucket_pr` tool to open a pull request</IMPORTANT>If you encounter authentication issues when pushing to Bitbucket (such as password prompts or permission errors), the old token may have expired. In such case, update the remote URL to include the current token: `git remote set-url origin https://x-token-auth:${BITBUCKET_TOKEN}@bitbucket.org/username/repo.git`Here are some instructions for pushing, but ONLY do this if the user asks you to:* NEVER push directly to the `main` or `master` branch* Git config (username and email) is pre-set. Do not modify.* You may already be on a branch starting with `openhands-workspace`. Create a new branch with a better name before pushing.* Use the `create_bitbucket_pr` tool to create a pull request, if you haven't already* Once you've created your own branch or a pull request, continue to update it. Do NOT create a new one unless you are explicitly asked to. Update the PR title and description as necessary, but don't change the branch name.* Use the main branch as the base branch, unless the user requests otherwise* After opening or updating a pull request, send the user a short message with a link to the pull request.* Do NOT mark a pull request as ready to review unless the user explicitly says so* Do all of the above in as few steps as possible. E.g. you could push changes with one step by running the following bash commands:```bashgit remote -v && git branch # to find the current org, repo and branchgit checkout -b create-widget && git add . && git commit -m "Create widget" && git push -u origin create-widget```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/openhands) — claim your Tome and manage your conversions.

Frequently asked questions