# Send Bitbucket Automation to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "bitbucket-automation", "name": "Bitbucket Automation", "source": "tencent", "type": "skill", "category": "效率提升", "sourceUrl": "https://clawhub.ai/sohamganatra/bitbucket-automation", "canonicalUrl": "https://clawhub.ai/sohamganatra/bitbucket-automation", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/bitbucket-automation", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=bitbucket-automation", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "slug": "bitbucket-automation", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-29T06:04:17.700Z", "expiresAt": "2026-05-06T06:04:17.700Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=bitbucket-automation", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=bitbucket-automation", "contentDisposition": "attachment; filename=\"bitbucket-automation-0.1.0.zip\"", "redirectLocation": null, "bodySnippet": null, "slug": "bitbucket-automation" }, "scope": "item", "summary": "Item download looks usable.", "detail": "Yavira can redirect you to the upstream package for this item.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/bitbucket-automation" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/bitbucket-automation", "downloadUrl": "https://openagent3.xyz/downloads/bitbucket-automation", "agentUrl": "https://openagent3.xyz/skills/bitbucket-automation/agent", "manifestUrl": "https://openagent3.xyz/skills/bitbucket-automation/agent.json", "briefUrl": "https://openagent3.xyz/skills/bitbucket-automation/agent.md" } } ``` ## Documentation ### Bitbucket Automation via Rube MCP Automate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit. ### Prerequisites Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Bitbucket connection via RUBE_MANAGE_CONNECTIONS with toolkit bitbucket Always call RUBE_SEARCH_TOOLS first to get current tool schemas ### Setup Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit bitbucket If connection is not ACTIVE, follow the returned auth link to complete Bitbucket OAuth Confirm connection status shows ACTIVE before running any workflows ### 1. Manage Pull Requests When to use: User wants to create, review, or inspect pull requests Tool sequence: BITBUCKET_LIST_WORKSPACES - Discover accessible workspaces [Prerequisite] BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE - Find the target repository [Prerequisite] BITBUCKET_LIST_BRANCHES - Verify source and destination branches exist [Prerequisite] BITBUCKET_CREATE_PULL_REQUEST - Create a new PR with title, source branch, and optional reviewers [Required] BITBUCKET_LIST_PULL_REQUESTS - List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional] BITBUCKET_GET_PULL_REQUEST - Get full details of a specific PR by ID [Optional] BITBUCKET_GET_PULL_REQUEST_DIFF - Fetch unified diff for code review [Optional] BITBUCKET_GET_PULL_REQUEST_DIFFSTAT - Get changed files with lines added/removed [Optional] Key parameters: workspace: Workspace slug or UUID (required for all operations) repo_slug: URL-friendly repository name source_branch: Branch with changes to merge destination_branch: Target branch (defaults to repo main branch if omitted) reviewers: List of objects with uuid field for reviewer assignment state: Filter for LIST_PULL_REQUESTS - OPEN, MERGED, or DECLINED max_chars: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffs Pitfalls: reviewers expects an array of objects with uuid key, NOT usernames: [{"uuid": "{...}"}] UUID format must include curly braces: {123e4567-e89b-12d3-a456-426614174000} destination_branch defaults to the repo's main branch if omitted, which may not be main pull_request_id is an integer for GET/DIFF operations but comes back as part of PR listing Large diffs can overwhelm context; always set max_chars (e.g., 50000) on GET_PULL_REQUEST_DIFF ### 2. Manage Repositories and Workspaces When to use: User wants to list, create, or delete repositories or explore workspaces Tool sequence: BITBUCKET_LIST_WORKSPACES - List all accessible workspaces [Required] BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE - List repos with optional BBQL filtering [Required] BITBUCKET_CREATE_REPOSITORY - Create a new repo with language, privacy, and project settings [Optional] BITBUCKET_DELETE_REPOSITORY - Permanently delete a repository (irreversible) [Optional] BITBUCKET_LIST_WORKSPACE_MEMBERS - List members for reviewer assignment or access checks [Optional] Key parameters: workspace: Workspace slug (find via LIST_WORKSPACES) repo_slug: URL-friendly name for create/delete q: BBQL query filter (e.g., name~"api", project.key="PROJ", is_private=true) role: Filter repos by user role: member, contributor, admin, owner sort: Sort field with optional - prefix for descending (e.g., -updated_on) is_private: Boolean for repository visibility (defaults to true) project_key: Bitbucket project key; omit to use workspace's oldest project Pitfalls: BITBUCKET_DELETE_REPOSITORY is irreversible and does not affect forks BBQL string values MUST be enclosed in double quotes: name~"my-repo" not name~my-repo repository is NOT a valid BBQL field; use name instead Default pagination is 10 results; set pagelen explicitly for complete listings CREATE_REPOSITORY defaults to private; set is_private: false for public repos ### 3. Manage Issues When to use: User wants to create, update, list, or comment on repository issues Tool sequence: BITBUCKET_LIST_ISSUES - List issues with optional filters for state, priority, kind, assignee [Required] BITBUCKET_CREATE_ISSUE - Create a new issue with title, content, priority, and kind [Required] BITBUCKET_UPDATE_ISSUE - Modify issue attributes (state, priority, assignee, etc.) [Optional] BITBUCKET_CREATE_ISSUE_COMMENT - Add a markdown comment to an existing issue [Optional] BITBUCKET_DELETE_ISSUE - Permanently delete an issue [Optional] Key parameters: issue_id: String identifier for the issue title, content: Required for creation kind: bug, enhancement, proposal, or task priority: trivial, minor, major, critical, or blocker state: new, open, resolved, on hold, invalid, duplicate, wontfix, closed assignee: Bitbucket username for CREATE; assignee_account_id (UUID) for UPDATE due_on: ISO 8601 format date string Pitfalls: Issue tracker must be enabled on the repository (has_issues: true) or API calls will fail CREATE_ISSUE uses assignee (username string), but UPDATE_ISSUE uses assignee_account_id (UUID) -- they are different fields DELETE_ISSUE is permanent with no undo state values include spaces: "on hold" not "on_hold" Filtering by assignee in LIST_ISSUES uses account ID, not username; use "null" string for unassigned ### 4. Manage Branches When to use: User wants to create branches or explore branch structure Tool sequence: BITBUCKET_LIST_BRANCHES - List branches with optional BBQL filter and sorting [Required] BITBUCKET_CREATE_BRANCH - Create a new branch from a specific commit hash [Required] Key parameters: name: Branch name without refs/heads/ prefix (e.g., feature/new-login) target_hash: Full SHA1 commit hash to branch from (must exist in repo) q: BBQL filter (e.g., name~"feature/", name="main") sort: Sort by name or -target.date (descending commit date) pagelen: 1-100 results per page (default is 10) Pitfalls: CREATE_BRANCH requires a full commit hash, NOT a branch name as target_hash Do NOT include refs/heads/ prefix in branch names Branch names must follow Bitbucket naming conventions (alphanumeric, /, ., _, -) BBQL string values need double quotes: name~"feature/" not name~feature/ ### 5. Review Pull Requests with Comments When to use: User wants to add review comments to pull requests, including inline code comments Tool sequence: BITBUCKET_GET_PULL_REQUEST - Get PR details and verify it exists [Prerequisite] BITBUCKET_GET_PULL_REQUEST_DIFF - Review the actual code changes [Prerequisite] BITBUCKET_GET_PULL_REQUEST_DIFFSTAT - Get list of changed files [Optional] BITBUCKET_CREATE_PULL_REQUEST_COMMENT - Post review comments [Required] Key parameters: pull_request_id: String ID of the PR content_raw: Markdown-formatted comment text content_markup: Defaults to markdown; also supports plaintext inline: Object with path, from, to for inline code comments parent_comment_id: Integer ID for threaded replies to existing comments Pitfalls: pull_request_id is a string in CREATE_PULL_REQUEST_COMMENT but an integer in GET_PULL_REQUEST Inline comments require inline.path at minimum; from/to are optional line numbers parent_comment_id creates a threaded reply; omit for top-level comments Line numbers in inline comments reference the diff, not the source file ### ID Resolution Always resolve human-readable names to IDs before operations: Workspace: BITBUCKET_LIST_WORKSPACES to get workspace slugs Repository: BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE with q filter to find repo slugs Branch: BITBUCKET_LIST_BRANCHES to verify branch existence before PR creation Members: BITBUCKET_LIST_WORKSPACE_MEMBERS to get UUIDs for reviewer assignment ### Pagination Bitbucket uses page-based pagination (not cursor-based): Use page (starts at 1) and pagelen (items per page) parameters Default page size is typically 10; set pagelen explicitly (max 50 for PRs, 100 for others) Check response for next URL or total count to determine if more pages exist Always iterate through all pages for complete results ### BBQL Filtering Bitbucket Query Language is available on list endpoints: String values MUST use double quotes: name~"pattern" Operators: = (exact), ~ (contains), != (not equal), >, >=, <, <= Combine with AND / OR: name~"api" AND is_private=true ### ID Formats Workspace: slug string (e.g., my-workspace) or UUID in braces ({uuid}) Reviewer UUIDs must include curly braces: {123e4567-e89b-12d3-a456-426614174000} Issue IDs are strings; PR IDs are integers in some tools, strings in others Commit hashes must be full SHA1 (40 characters) ### Parameter Quirks assignee vs assignee_account_id: CREATE_ISSUE uses username, UPDATE_ISSUE uses UUID state values for issues include spaces: "on hold", not "on_hold" destination_branch omission defaults to repo main branch, not main literally BBQL repository is not a valid field -- use name ### Rate Limits Bitbucket Cloud API has rate limits; large batch operations should include delays Paginated requests count against rate limits; minimize unnecessary page fetches ### Destructive Operations BITBUCKET_DELETE_REPOSITORY is irreversible and does not remove forks BITBUCKET_DELETE_ISSUE is permanent with no recovery option Always confirm with the user before executing delete operations ### Quick Reference TaskTool SlugKey ParamsList workspacesBITBUCKET_LIST_WORKSPACESq, sortList reposBITBUCKET_LIST_REPOSITORIES_IN_WORKSPACEworkspace, q, roleCreate repoBITBUCKET_CREATE_REPOSITORYworkspace, repo_slug, is_privateDelete repoBITBUCKET_DELETE_REPOSITORYworkspace, repo_slugList branchesBITBUCKET_LIST_BRANCHESworkspace, repo_slug, qCreate branchBITBUCKET_CREATE_BRANCHworkspace, repo_slug, name, target_hashList PRsBITBUCKET_LIST_PULL_REQUESTSworkspace, repo_slug, stateCreate PRBITBUCKET_CREATE_PULL_REQUESTworkspace, repo_slug, title, source_branchGet PR detailsBITBUCKET_GET_PULL_REQUESTworkspace, repo_slug, pull_request_idGet PR diffBITBUCKET_GET_PULL_REQUEST_DIFFworkspace, repo_slug, pull_request_id, max_charsGet PR diffstatBITBUCKET_GET_PULL_REQUEST_DIFFSTATworkspace, repo_slug, pull_request_idComment on PRBITBUCKET_CREATE_PULL_REQUEST_COMMENTworkspace, repo_slug, pull_request_id, content_rawList issuesBITBUCKET_LIST_ISSUESworkspace, repo_slug, state, priorityCreate issueBITBUCKET_CREATE_ISSUEworkspace, repo_slug, title, contentUpdate issueBITBUCKET_UPDATE_ISSUEworkspace, repo_slug, issue_idComment on issueBITBUCKET_CREATE_ISSUE_COMMENTworkspace, repo_slug, issue_id, contentDelete issueBITBUCKET_DELETE_ISSUEworkspace, repo_slug, issue_idList membersBITBUCKET_LIST_WORKSPACE_MEMBERSworkspace ## Trust - Source: tencent - Verification: Indexed source record - Publisher: sohamganatra - Version: 0.1.0 ## Source health - Status: healthy - Item download looks usable. - Yavira can redirect you to the upstream package for this item. - Health scope: item - Reason: direct_download_ok - Checked at: 2026-04-29T06:04:17.700Z - Expires at: 2026-05-06T06:04:17.700Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/bitbucket-automation) - [Send to Agent page](https://openagent3.xyz/skills/bitbucket-automation/agent) - [JSON manifest](https://openagent3.xyz/skills/bitbucket-automation/agent.json) - [Markdown brief](https://openagent3.xyz/skills/bitbucket-automation/agent.md) - [Download page](https://openagent3.xyz/downloads/bitbucket-automation)