{"id":"8058cfa2-abc6-4cb6-86b6-f3cc4c598a4c","entityType":"agent","slug":"clawhub-hith3sh-bitbucket-repos","name":"Bitbucket","canonicalUrl":"https://www.xpersona.co/agent/clawhub-hith3sh-bitbucket-repos","canonicalPath":"/agent/clawhub-hith3sh-bitbucket-repos","generatedAt":"2026-10-09T19:22:28.759Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T12:42:49.453Z","emptyReason":null},"description":"Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want t... Skill: Bitbucket Owner: hith3sh Summary: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want t... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:04:22.071Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sou","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 2.6K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:bitbucket-repos","sourceUrl":"https://clawhub.ai/hith3sh/bitbucket-repos","homepage":"https://clawhub.ai/hith3sh/skills/bitbucket-repos","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/hith3sh/bitbucket-repos","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/hith3sh/skills/bitbucket-repos","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":68,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want t..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:42:49.453Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:42:49.453Z","emptyReason":null},"stars":null,"forks":null,"downloads":2631,"packageName":null,"latestVersion":"1.0.6","tractionLabel":"2.6K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T12:42:49.453Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T12:42:49.453Z","lastCrawledAt":"2026-10-09T12:42:49.453Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T12:42:49.453Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.6","createdAt":"2026-06-09T07:04:22.071Z","changelog":"Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.","fileCount":3,"zipByteSize":6326},{"version":"1.0.5","createdAt":"2026-06-09T06:08:03.980Z","changelog":"- Updated branding image URL in documentation for Bitbucket logo. - Removed unnecessary file: skill-card.md. - No changes to configuration or core functionality.","fileCount":3,"zipByteSize":6187},{"version":"1.0.4","createdAt":"2026-06-09T04:44:43.302Z","changelog":"- Removed the redundant skill-card.md file. - No functional or user-facing changes were made in this version.","fileCount":3,"zipByteSize":6380},{"version":"1.0.2","createdAt":"2026-06-08T16:44:50.154Z","changelog":"- No functional or documentation changes; this release contains no file modifications. - Version bump to 1.0.2 for maintenance and consistency.","fileCount":3,"zipByteSize":6275},{"version":"1.0.1","createdAt":"2026-06-08T16:25:59.867Z","changelog":"- Added Bitbucket logo image to the top of SKILL.md for enhanced branding. - Minor document formatting adjustments for improved readability. - Removed skill-card.md file.","fileCount":3,"zipByteSize":6237},{"version":"0.1.1","createdAt":"2026-06-07T13:27:11.903Z","changelog":"Full rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.","fileCount":3,"zipByteSize":6185},{"version":"0.1.0","createdAt":"2026-05-06T14:21:57.220Z","changelog":"bitbucket-repos 0.1.0 - Initial release. - Enables browsing Bitbucket repositories, managing branches, reviewing pull requests, and coordinating repository workflows through ClawLink integration. - Uses ClawLink to handle authentication and tool access, so no manual Bitbucket API setup is required. - Includes clear setup and usage instructions for connecting Bitbucket via ClawLink and discovering available tools. - Emphasizes secure handling of credentials and confirmation before performing write or destructive actions.","fileCount":3,"zipByteSize":3568}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s173vws87a7ss71xf9rq53k5gd8568kv:bitbucket-repos","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-09T19:22:28.756Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-hith3sh-bitbucket-repos/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T12:42:49.453Z","emptyReason":null},"readme":"Skill: Bitbucket\n\nOwner: hith3sh\n\nSummary: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want t...\n\nTags: latest:1.0.6\n\nVersion history:\n\nv1.0.6 | 2026-06-09T07:04:22.071Z | user\n\nAdd UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic source.\n\nv1.0.5 | 2026-06-09T06:08:03.980Z | auto\n\n- Updated branding image URL in documentation for Bitbucket logo.\n- Removed unnecessary file: skill-card.md.\n- No changes to configuration or core functionality.\n\nv1.0.4 | 2026-06-09T04:44:43.302Z | auto\n\n- Removed the redundant skill-card.md file.\n- No functional or user-facing changes were made in this version.\n\nv1.0.2 | 2026-06-08T16:44:50.154Z | auto\n\n- No functional or documentation changes; this release contains no file modifications.\n- Version bump to 1.0.2 for maintenance and consistency.\n\nv1.0.1 | 2026-06-08T16:25:59.867Z | auto\n\n- Added Bitbucket logo image to the top of SKILL.md for enhanced branding.\n- Minor document formatting adjustments for improved readability.\n- Removed skill-card.md file.\n\nv0.1.1 | 2026-06-07T13:27:11.903Z | user\n\nFull rewrite to new standard: added tool reference tables, 3-step GIF table, architecture diagram, code examples, error handling, and troubleshooting.\n\nv0.1.0 | 2026-05-06T14:21:57.220Z | auto\n\nbitbucket-repos 0.1.0\n\n- Initial release.\n- Enables browsing Bitbucket repositories, managing branches, reviewing pull requests, and coordinating repository workflows through ClawLink integration.\n- Uses ClawLink to handle authentication and tool access, so no manual Bitbucket API setup is required.\n- Includes clear setup and usage instructions for connecting Bitbucket via ClawLink and discovering available tools.\n- Emphasizes secure handling of credentials and confirmation before performing write or destructive actions.\n\nArchive index:\n\nArchive v1.0.6: 3 files, 6326 bytes\n\nFiles: skill-card.md (2426b), SKILL.md (16874b), _meta.json (134b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: bitbucket-repos\ndescription: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.\n---\n\n# Bitbucket\n\n\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=bitbucket-repos) for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Bitbucket |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Bitbucket |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Bitbucket again.\"\n\n## Quick Start\n\n```bash\n# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-workspace\"}'\n\n# List branches in a repository\nclawlink_call_tool --tool \"bitbucket_list_branches\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\"}'\n\n# Get a pull request\nclawlink_call_tool --tool \"bitbucket_get_pull_request\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\", \"pull_request_id\": 1}'\n```\n\n## Authentication\n\nAll Bitbucket tool calls are authenticated automatically by ClawLink using the user's connected Bitbucket account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Bitbucket API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `bitbucket` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration bitbucket\n```\n\n**Response:** Returns the live tool catalog for Bitbucket.\n\n### Reconnect\n\nIf Bitbucket tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=bitbucket\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration bitbucket`\n\n## Security& Permissions\n\n- Access is scoped to repositories and resources accessible to the connected Bitbucket account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete repository, delete branch, delete issue) are marked as high-impact and must be confirmed.\n- Repository deletion does not affect forks.\n\n## Tool Reference\n\n### Repository Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_repositories_in_workspace` | List repositories in a workspace | Read |\n| `bitbucket_list_repositories` | List public repositories | Read |\n| `bitbucket_get_repository` | Get repository metadata | Read |\n| `bitbucket_create_repository` | Create a new repository in a workspace | Write |\n| `bitbucket_delete_repository` | Permanently delete a repository | Write |\n| `bitbucket_browse_repository_path` | Get file content or list directory at a revision | Read |\n| `bitbucket_get_file_from_repository` | Get a specific file's content at a commit | Read |\n| `bitbucket_list_repository_paths` | List files and directories under a path | Read |\n\n### Branch Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_branches` | List branches with optional name filtering | Read |\n| `bitbucket_get_branch` | Get branch metadata and target commit | Read |\n| `bitbucket_create_branch` | Create a new branch from a target commit | Write |\n| `bitbucket_get_repositories_branching_model` | Get the repository's branch workflow configuration | Read |\n| `bitbucket_get_repositories_effective_branching_model` | Get effective branching model (including inheritance) | Read |\n\n### Commit Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_commits` | List commits with optional branch/path filters | Read |\n| `bitbucket_get_repositories_commit` | Get detailed commit information | Read |\n| `bitbucket_get_commit_diff` | Get the unified diff for a commit or range | Read |\n| `bitbucket_get_commit_changes` | Get changed files in a commit | Read |\n| `bitbucket_get_commit_build_status` | Get build status for a commit | Read |\n| `bitbucket_get_commit_diffstat` | Get diffstat (files changed, lines added/removed) | Read |\n\n### Pull Request Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pull_requests` | List pull requests by state (OPEN/MERGED/DECLINED) | Read |\n| `bitbucket_get_pull_request` | Get a single pull request with full details | Read |\n| `bitbucket_get_pull_request_commits` | Get commits included in a PR | Read |\n| `bitbucket_get_pull_request_diff` | Get the unified diff for a PR | Read |\n| `bitbucket_get_pull_request_diffstat` | Get diffstat for a PR | Read |\n| `bitbucket_create_pull_request` | Create a new pull request | Write |\n| `bitbucket_update_pull_request` | Update PR title, description, or reviewers | Write |\n| `bitbucket_merge_pull_request` | Merge a pull request | Write |\n| `bitbucket_approve_pull_request` | Approve a pull request | Write |\n| `bitbucket_request_pull_request_changes` | Request changes on a PR | Write |\n| `bitbucket_create_pull_request_comment` | Add a top-level or threaded comment to a PR | Write |\n| `bitbucket_delete_pull_request_comment` | Delete a PR comment | Write |\n| `bitbucket_resolve_pull_request_comment` | Resolve or reopen a PR comment thread | Write |\n\n### Issue Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_issues` | List issues with optional state/priority filters | Read |\n| `bitbucket_create_issue` | Create a new issue | Write |\n| `bitbucket_update_issue` | Update issue attributes | Write |\n| `bitbucket_delete_issue` | Permanently delete an issue | Write |\n| `bitbucket_create_issue_comment` | Add a comment to an issue | Write |\n\n### User & Workspace\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_current_user` | Get the authenticated user's profile | Read |\n| `bitbucket_list_workspaces` | List workspaces accessible to the user | Read |\n| `bitbucket_get_workspace` | Get workspace metadata | Read |\n| `bitbucket_list_workspace_members` | List members of a workspace | Read |\n| `bitbucket_list_workspace_projects` | List projects in a workspace | Read |\n\n### Pipelines & Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pipelines` | List pipeline runs for a repository | Read |\n| `bitbucket_get_repositories_pipelines2` | Get a specific pipeline's details | Read |\n| `bitbucket_list_repositories_environments` | List deployment environments | Read |\n| `bitbucket_list_deployments` | List deployment history | Read |\n\n### Code Search\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_workspaces_search_code` | Search code across all repos in a workspace | Read |\n| `bitbucket_search_user_repositories_code` | Search code in a specific user's repos | Read |\n\n## Code Examples\n\n### List branches in a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_list_branches\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"q\": \"name~\\\"feature\\\"\"\n }'\n```\n\n### Create a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_create_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"title\": \"Add new feature\",\n \"source_branch\": \"feature/new-feature\",\n \"destination_branch\": \"main\",\n \"description\": \"This PR adds the new feature as described in issue #123\"\n }'\n```\n\n### Approve a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_approve_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"pull_request_id\": 42\n }'\n```\n\n### Get file content from a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_get_file_from_repository\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"path\": \"README.md\",\n \"commit_revision\": \"main\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Bitbucket is connected.\n2. Call `clawlink_list_tools --integration bitbucket` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `bitbucket`.\n5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List repos → List branches → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Branch names must be unique within a repository and must not include the `refs/heads/` prefix.\n- Pull request IDs are numeric. Use `bitbucket_list_pull_requests` to find PR IDs.\n- Repository deletion does not affect forks — forks are separate copies.\n- Pagination: use the `next` field in responses to iterate through large result sets.\n- BBQL (Bitbucket Query Language) supports server-side filtering for branch names.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration bitbucket`. |\n| Missing connection | Bitbucket is not connected. Direct the user to https://claw-link.dev/dashboard?add=bitbucket. |\n| `BranchNotFound` | Branch does not exist. Check the branch name. |\n| `PullRequestNotFound` | Pull request does not exist. Check the PR ID. |\n| `RepositoryNotFound` | Repository does not exist or is not accessible. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `bitbucket`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=bitbucket-repos\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub repository operations\n- [GitLab](https://clawhub.ai/hith3sh/gitlab-repos) — For GitLab repository operations\n- [Jira](https://clawhub.ai/hith3sh/jira-projects) — For Jira issue tracking\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=bitbucket-repos)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780988662071\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nBrowse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to inspect Bitbucket repository contents, manage branches, review pull requests, and coordinate code workflows from chat through ClawLink and the Bitbucket Cloud API.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill installs and persistently allowlists an unpinned external plugin with OAuth-backed repository write capabilities.\n\nMitigation: Verify the ClawLink plugin publisher, prefer a pinned and reviewed version when available, and remove the plugin allowlist if behavior does not match expectations.\n\nRisk: Repository, branch, pull request, and issue write operations can change or delete Bitbucket resources accessible to the connected account.\n\nMitigation: Connect Bitbucket with the minimum scopes needed and review every preview before approving write operations.\n\nRisk: OAuth access may remain active after installation.\n\nMitigation: Be prepared to revoke the OAuth integration if access is no longer needed or if any activity looks wrong.\n\n## Reference(s):\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/bitbucket-repos)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, API Calls]\n\n**Output Format:** [Markdown with inline bash and JSON snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires review and explicit confirmation before write operations.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.5: 3 files, 6187 bytes\n\nFiles: skill-card.md (2375b), SKILL.md (16670b), _meta.json (134b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: bitbucket-repos\ndescription: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.\n---\n\n# Bitbucket\n\n\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Bitbucket |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Bitbucket |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Bitbucket again.\"\n\n## Quick Start\n\n```bash\n# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-workspace\"}'\n\n# List branches in a repository\nclawlink_call_tool --tool \"bitbucket_list_branches\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\"}'\n\n# Get a pull request\nclawlink_call_tool --tool \"bitbucket_get_pull_request\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\", \"pull_request_id\": 1}'\n```\n\n## Authentication\n\nAll Bitbucket tool calls are authenticated automatically by ClawLink using the user's connected Bitbucket account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Bitbucket API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `bitbucket` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration bitbucket\n```\n\n**Response:** Returns the live tool catalog for Bitbucket.\n\n### Reconnect\n\nIf Bitbucket tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=bitbucket\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration bitbucket`\n\n## Security& Permissions\n\n- Access is scoped to repositories and resources accessible to the connected Bitbucket account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete repository, delete branch, delete issue) are marked as high-impact and must be confirmed.\n- Repository deletion does not affect forks.\n\n## Tool Reference\n\n### Repository Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_repositories_in_workspace` | List repositories in a workspace | Read |\n| `bitbucket_list_repositories` | List public repositories | Read |\n| `bitbucket_get_repository` | Get repository metadata | Read |\n| `bitbucket_create_repository` | Create a new repository in a workspace | Write |\n| `bitbucket_delete_repository` | Permanently delete a repository | Write |\n| `bitbucket_browse_repository_path` | Get file content or list directory at a revision | Read |\n| `bitbucket_get_file_from_repository` | Get a specific file's content at a commit | Read |\n| `bitbucket_list_repository_paths` | List files and directories under a path | Read |\n\n### Branch Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_branches` | List branches with optional name filtering | Read |\n| `bitbucket_get_branch` | Get branch metadata and target commit | Read |\n| `bitbucket_create_branch` | Create a new branch from a target commit | Write |\n| `bitbucket_get_repositories_branching_model` | Get the repository's branch workflow configuration | Read |\n| `bitbucket_get_repositories_effective_branching_model` | Get effective branching model (including inheritance) | Read |\n\n### Commit Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_commits` | List commits with optional branch/path filters | Read |\n| `bitbucket_get_repositories_commit` | Get detailed commit information | Read |\n| `bitbucket_get_commit_diff` | Get the unified diff for a commit or range | Read |\n| `bitbucket_get_commit_changes` | Get changed files in a commit | Read |\n| `bitbucket_get_commit_build_status` | Get build status for a commit | Read |\n| `bitbucket_get_commit_diffstat` | Get diffstat (files changed, lines added/removed) | Read |\n\n### Pull Request Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pull_requests` | List pull requests by state (OPEN/MERGED/DECLINED) | Read |\n| `bitbucket_get_pull_request` | Get a single pull request with full details | Read |\n| `bitbucket_get_pull_request_commits` | Get commits included in a PR | Read |\n| `bitbucket_get_pull_request_diff` | Get the unified diff for a PR | Read |\n| `bitbucket_get_pull_request_diffstat` | Get diffstat for a PR | Read |\n| `bitbucket_create_pull_request` | Create a new pull request | Write |\n| `bitbucket_update_pull_request` | Update PR title, description, or reviewers | Write |\n| `bitbucket_merge_pull_request` | Merge a pull request | Write |\n| `bitbucket_approve_pull_request` | Approve a pull request | Write |\n| `bitbucket_request_pull_request_changes` | Request changes on a PR | Write |\n| `bitbucket_create_pull_request_comment` | Add a top-level or threaded comment to a PR | Write |\n| `bitbucket_delete_pull_request_comment` | Delete a PR comment | Write |\n| `bitbucket_resolve_pull_request_comment` | Resolve or reopen a PR comment thread | Write |\n\n### Issue Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_issues` | List issues with optional state/priority filters | Read |\n| `bitbucket_create_issue` | Create a new issue | Write |\n| `bitbucket_update_issue` | Update issue attributes | Write |\n| `bitbucket_delete_issue` | Permanently delete an issue | Write |\n| `bitbucket_create_issue_comment` | Add a comment to an issue | Write |\n\n### User & Workspace\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_current_user` | Get the authenticated user's profile | Read |\n| `bitbucket_list_workspaces` | List workspaces accessible to the user | Read |\n| `bitbucket_get_workspace` | Get workspace metadata | Read |\n| `bitbucket_list_workspace_members` | List members of a workspace | Read |\n| `bitbucket_list_workspace_projects` | List projects in a workspace | Read |\n\n### Pipelines & Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pipelines` | List pipeline runs for a repository | Read |\n| `bitbucket_get_repositories_pipelines2` | Get a specific pipeline's details | Read |\n| `bitbucket_list_repositories_environments` | List deployment environments | Read |\n| `bitbucket_list_deployments` | List deployment history | Read |\n\n### Code Search\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_workspaces_search_code` | Search code across all repos in a workspace | Read |\n| `bitbucket_search_user_repositories_code` | Search code in a specific user's repos | Read |\n\n## Code Examples\n\n### List branches in a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_list_branches\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"q\": \"name~\\\"feature\\\"\"\n }'\n```\n\n### Create a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_create_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"title\": \"Add new feature\",\n \"source_branch\": \"feature/new-feature\",\n \"destination_branch\": \"main\",\n \"description\": \"This PR adds the new feature as described in issue #123\"\n }'\n```\n\n### Approve a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_approve_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"pull_request_id\": 42\n }'\n```\n\n### Get file content from a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_get_file_from_repository\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"path\": \"README.md\",\n \"commit_revision\": \"main\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Bitbucket is connected.\n2. Call `clawlink_list_tools --integration bitbucket` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `bitbucket`.\n5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List repos → List branches → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Branch names must be unique within a repository and must not include the `refs/heads/` prefix.\n- Pull request IDs are numeric. Use `bitbucket_list_pull_requests` to find PR IDs.\n- Repository deletion does not affect forks — forks are separate copies.\n- Pagination: use the `next` field in responses to iterate through large result sets.\n- BBQL (Bitbucket Query Language) supports server-side filtering for branch names.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration bitbucket`. |\n| Missing connection | Bitbucket is not connected. Direct the user to https://claw-link.dev/dashboard?add=bitbucket. |\n| `BranchNotFound` | Branch does not exist. Check the branch name. |\n| `PullRequestNotFound` | Pull request does not exist. Check the PR ID. |\n| `RepositoryNotFound` | Repository does not exist or is not accessible. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `bitbucket`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub repository operations\n- [GitLab](https://clawhub.ai/hith3sh/gitlab-repos) — For GitLab repository operations\n- [Jira](https://clawhub.ai/hith3sh/jira-projects) — For Jira issue tracking\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.5:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"1.0.5\",\n \"publishedAt\": 1780985283980\n}\n\nFile v1.0.5:skill-card.md\n\n## Description:
\nBrowse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to inspect Bitbucket repository contents, manage branches, review pull requests, and coordinate source-code workflows through authenticated Bitbucket Cloud API tools.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill requires OAuth access to the user's Bitbucket account through ClawLink.
\nMitigation: Install only when the user trusts ClawLink with Bitbucket access, and review the Bitbucket permissions granted during OAuth.
\nRisk: Repository, branch, pull request, issue, and comment operations can modify or delete Bitbucket resources.
\nMitigation: Require clear user confirmation before repository deletion, branch changes, pull request merges or approvals, issue deletion, or public comments.
\n\n\n## Reference(s):
\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)
\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)
\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink](https://claw-link.dev)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Guidance may include authenticated Bitbucket tool calls through ClawLink and should preserve user confirmation before write operations.]
\n\n## Skill Version(s):
\n1.0.5 (source: server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.4: 3 files, 6380 bytes\n\nFiles: skill-card.md (2876b), SKILL.md (16666b), _meta.json (134b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: bitbucket-repos\ndescription: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.\n---\n\n# Bitbucket\n\n\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Bitbucket |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Bitbucket |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Bitbucket again.\"\n\n## Quick Start\n\n```bash\n# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-workspace\"}'\n\n# List branches in a repository\nclawlink_call_tool --tool \"bitbucket_list_branches\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\"}'\n\n# Get a pull request\nclawlink_call_tool --tool \"bitbucket_get_pull_request\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\", \"pull_request_id\": 1}'\n```\n\n## Authentication\n\nAll Bitbucket tool calls are authenticated automatically by ClawLink using the user's connected Bitbucket account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Bitbucket API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `bitbucket` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration bitbucket\n```\n\n**Response:** Returns the live tool catalog for Bitbucket.\n\n### Reconnect\n\nIf Bitbucket tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=bitbucket\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration bitbucket`\n\n## Security& Permissions\n\n- Access is scoped to repositories and resources accessible to the connected Bitbucket account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete repository, delete branch, delete issue) are marked as high-impact and must be confirmed.\n- Repository deletion does not affect forks.\n\n## Tool Reference\n\n### Repository Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_repositories_in_workspace` | List repositories in a workspace | Read |\n| `bitbucket_list_repositories` | List public repositories | Read |\n| `bitbucket_get_repository` | Get repository metadata | Read |\n| `bitbucket_create_repository` | Create a new repository in a workspace | Write |\n| `bitbucket_delete_repository` | Permanently delete a repository | Write |\n| `bitbucket_browse_repository_path` | Get file content or list directory at a revision | Read |\n| `bitbucket_get_file_from_repository` | Get a specific file's content at a commit | Read |\n| `bitbucket_list_repository_paths` | List files and directories under a path | Read |\n\n### Branch Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_branches` | List branches with optional name filtering | Read |\n| `bitbucket_get_branch` | Get branch metadata and target commit | Read |\n| `bitbucket_create_branch` | Create a new branch from a target commit | Write |\n| `bitbucket_get_repositories_branching_model` | Get the repository's branch workflow configuration | Read |\n| `bitbucket_get_repositories_effective_branching_model` | Get effective branching model (including inheritance) | Read |\n\n### Commit Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_commits` | List commits with optional branch/path filters | Read |\n| `bitbucket_get_repositories_commit` | Get detailed commit information | Read |\n| `bitbucket_get_commit_diff` | Get the unified diff for a commit or range | Read |\n| `bitbucket_get_commit_changes` | Get changed files in a commit | Read |\n| `bitbucket_get_commit_build_status` | Get build status for a commit | Read |\n| `bitbucket_get_commit_diffstat` | Get diffstat (files changed, lines added/removed) | Read |\n\n### Pull Request Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pull_requests` | List pull requests by state (OPEN/MERGED/DECLINED) | Read |\n| `bitbucket_get_pull_request` | Get a single pull request with full details | Read |\n| `bitbucket_get_pull_request_commits` | Get commits included in a PR | Read |\n| `bitbucket_get_pull_request_diff` | Get the unified diff for a PR | Read |\n| `bitbucket_get_pull_request_diffstat` | Get diffstat for a PR | Read |\n| `bitbucket_create_pull_request` | Create a new pull request | Write |\n| `bitbucket_update_pull_request` | Update PR title, description, or reviewers | Write |\n| `bitbucket_merge_pull_request` | Merge a pull request | Write |\n| `bitbucket_approve_pull_request` | Approve a pull request | Write |\n| `bitbucket_request_pull_request_changes` | Request changes on a PR | Write |\n| `bitbucket_create_pull_request_comment` | Add a top-level or threaded comment to a PR | Write |\n| `bitbucket_delete_pull_request_comment` | Delete a PR comment | Write |\n| `bitbucket_resolve_pull_request_comment` | Resolve or reopen a PR comment thread | Write |\n\n### Issue Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_issues` | List issues with optional state/priority filters | Read |\n| `bitbucket_create_issue` | Create a new issue | Write |\n| `bitbucket_update_issue` | Update issue attributes | Write |\n| `bitbucket_delete_issue` | Permanently delete an issue | Write |\n| `bitbucket_create_issue_comment` | Add a comment to an issue | Write |\n\n### User & Workspace\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_current_user` | Get the authenticated user's profile | Read |\n| `bitbucket_list_workspaces` | List workspaces accessible to the user | Read |\n| `bitbucket_get_workspace` | Get workspace metadata | Read |\n| `bitbucket_list_workspace_members` | List members of a workspace | Read |\n| `bitbucket_list_workspace_projects` | List projects in a workspace | Read |\n\n### Pipelines & Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pipelines` | List pipeline runs for a repository | Read |\n| `bitbucket_get_repositories_pipelines2` | Get a specific pipeline's details | Read |\n| `bitbucket_list_repositories_environments` | List deployment environments | Read |\n| `bitbucket_list_deployments` | List deployment history | Read |\n\n### Code Search\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_workspaces_search_code` | Search code across all repos in a workspace | Read |\n| `bitbucket_search_user_repositories_code` | Search code in a specific user's repos | Read |\n\n## Code Examples\n\n### List branches in a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_list_branches\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"q\": \"name~\\\"feature\\\"\"\n }'\n```\n\n### Create a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_create_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"title\": \"Add new feature\",\n \"source_branch\": \"feature/new-feature\",\n \"destination_branch\": \"main\",\n \"description\": \"This PR adds the new feature as described in issue #123\"\n }'\n```\n\n### Approve a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_approve_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"pull_request_id\": 42\n }'\n```\n\n### Get file content from a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_get_file_from_repository\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"path\": \"README.md\",\n \"commit_revision\": \"main\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Bitbucket is connected.\n2. Call `clawlink_list_tools --integration bitbucket` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `bitbucket`.\n5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List repos → List branches → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Branch names must be unique within a repository and must not include the `refs/heads/` prefix.\n- Pull request IDs are numeric. Use `bitbucket_list_pull_requests` to find PR IDs.\n- Repository deletion does not affect forks — forks are separate copies.\n- Pagination: use the `next` field in responses to iterate through large result sets.\n- BBQL (Bitbucket Query Language) supports server-side filtering for branch names.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration bitbucket`. |\n| Missing connection | Bitbucket is not connected. Direct the user to https://claw-link.dev/dashboard?add=bitbucket. |\n| `BranchNotFound` | Branch does not exist. Check the branch name. |\n| `PullRequestNotFound` | Pull request does not exist. Check the PR ID. |\n| `RepositoryNotFound` | Repository does not exist or is not accessible. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `bitbucket`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub repository operations\n- [GitLab](https://clawhub.ai/hith3sh/gitlab-repos) — For GitLab repository operations\n- [Jira](https://clawhub.ai/hith3sh/jira-projects) — For Jira issue tracking\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1780980283302\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:
\nBrowse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to inspect Bitbucket repositories, browse files, manage branches, review pull requests, and coordinate source-control workflows through an authenticated Bitbucket Cloud connection.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The connected ClawLink plugin can access Bitbucket resources available to the authenticated account.
\nMitigation: Use least-privilege Bitbucket access where possible and connect only the account or workspace needed for the task.
\nRisk: Write operations can create, update, merge, approve, comment on, or delete Bitbucket resources.
\nMitigation: Preview the intended change and require explicit user confirmation before executing any write or destructive operation.
\nRisk: The live Bitbucket tool catalog may differ from the examples in the skill text.
\nMitigation: List or describe available Bitbucket tools before use, and treat the live catalog as the source of truth for tool names and parameters.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/bitbucket-repos)
\n- [ClawLink](https://claw-link.dev)
\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)
\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)
\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Code, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline shell commands, JSON tool parameters, and source-control guidance]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include Bitbucket tool names, command snippets, preview guidance, and user-confirmation prompts for write operations.]
\n\n## Skill Version(s):
\n1.0.4 (source: release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.2: 3 files, 6275 bytes\n\nFiles: skill-card.md (2650b), SKILL.md (16666b), _meta.json (134b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: bitbucket-repos\ndescription: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.\n---\n\n# Bitbucket\n\n\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Bitbucket |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Bitbucket |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Bitbucket again.\"\n\n## Quick Start\n\n```bash\n# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-workspace\"}'\n\n# List branches in a repository\nclawlink_call_tool --tool \"bitbucket_list_branches\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\"}'\n\n# Get a pull request\nclawlink_call_tool --tool \"bitbucket_get_pull_request\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\", \"pull_request_id\": 1}'\n```\n\n## Authentication\n\nAll Bitbucket tool calls are authenticated automatically by ClawLink using the user's connected Bitbucket account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Bitbucket API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `bitbucket` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration bitbucket\n```\n\n**Response:** Returns the live tool catalog for Bitbucket.\n\n### Reconnect\n\nIf Bitbucket tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=bitbucket\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration bitbucket`\n\n## Security& Permissions\n\n- Access is scoped to repositories and resources accessible to the connected Bitbucket account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete repository, delete branch, delete issue) are marked as high-impact and must be confirmed.\n- Repository deletion does not affect forks.\n\n## Tool Reference\n\n### Repository Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_repositories_in_workspace` | List repositories in a workspace | Read |\n| `bitbucket_list_repositories` | List public repositories | Read |\n| `bitbucket_get_repository` | Get repository metadata | Read |\n| `bitbucket_create_repository` | Create a new repository in a workspace | Write |\n| `bitbucket_delete_repository` | Permanently delete a repository | Write |\n| `bitbucket_browse_repository_path` | Get file content or list directory at a revision | Read |\n| `bitbucket_get_file_from_repository` | Get a specific file's content at a commit | Read |\n| `bitbucket_list_repository_paths` | List files and directories under a path | Read |\n\n### Branch Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_branches` | List branches with optional name filtering | Read |\n| `bitbucket_get_branch` | Get branch metadata and target commit | Read |\n| `bitbucket_create_branch` | Create a new branch from a target commit | Write |\n| `bitbucket_get_repositories_branching_model` | Get the repository's branch workflow configuration | Read |\n| `bitbucket_get_repositories_effective_branching_model` | Get effective branching model (including inheritance) | Read |\n\n### Commit Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_commits` | List commits with optional branch/path filters | Read |\n| `bitbucket_get_repositories_commit` | Get detailed commit information | Read |\n| `bitbucket_get_commit_diff` | Get the unified diff for a commit or range | Read |\n| `bitbucket_get_commit_changes` | Get changed files in a commit | Read |\n| `bitbucket_get_commit_build_status` | Get build status for a commit | Read |\n| `bitbucket_get_commit_diffstat` | Get diffstat (files changed, lines added/removed) | Read |\n\n### Pull Request Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pull_requests` | List pull requests by state (OPEN/MERGED/DECLINED) | Read |\n| `bitbucket_get_pull_request` | Get a single pull request with full details | Read |\n| `bitbucket_get_pull_request_commits` | Get commits included in a PR | Read |\n| `bitbucket_get_pull_request_diff` | Get the unified diff for a PR | Read |\n| `bitbucket_get_pull_request_diffstat` | Get diffstat for a PR | Read |\n| `bitbucket_create_pull_request` | Create a new pull request | Write |\n| `bitbucket_update_pull_request` | Update PR title, description, or reviewers | Write |\n| `bitbucket_merge_pull_request` | Merge a pull request | Write |\n| `bitbucket_approve_pull_request` | Approve a pull request | Write |\n| `bitbucket_request_pull_request_changes` | Request changes on a PR | Write |\n| `bitbucket_create_pull_request_comment` | Add a top-level or threaded comment to a PR | Write |\n| `bitbucket_delete_pull_request_comment` | Delete a PR comment | Write |\n| `bitbucket_resolve_pull_request_comment` | Resolve or reopen a PR comment thread | Write |\n\n### Issue Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_issues` | List issues with optional state/priority filters | Read |\n| `bitbucket_create_issue` | Create a new issue | Write |\n| `bitbucket_update_issue` | Update issue attributes | Write |\n| `bitbucket_delete_issue` | Permanently delete an issue | Write |\n| `bitbucket_create_issue_comment` | Add a comment to an issue | Write |\n\n### User & Workspace\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_current_user` | Get the authenticated user's profile | Read |\n| `bitbucket_list_workspaces` | List workspaces accessible to the user | Read |\n| `bitbucket_get_workspace` | Get workspace metadata | Read |\n| `bitbucket_list_workspace_members` | List members of a workspace | Read |\n| `bitbucket_list_workspace_projects` | List projects in a workspace | Read |\n\n### Pipelines & Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pipelines` | List pipeline runs for a repository | Read |\n| `bitbucket_get_repositories_pipelines2` | Get a specific pipeline's details | Read |\n| `bitbucket_list_repositories_environments` | List deployment environments | Read |\n| `bitbucket_list_deployments` | List deployment history | Read |\n\n### Code Search\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_workspaces_search_code` | Search code across all repos in a workspace | Read |\n| `bitbucket_search_user_repositories_code` | Search code in a specific user's repos | Read |\n\n## Code Examples\n\n### List branches in a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_list_branches\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"q\": \"name~\\\"feature\\\"\"\n }'\n```\n\n### Create a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_create_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"title\": \"Add new feature\",\n \"source_branch\": \"feature/new-feature\",\n \"destination_branch\": \"main\",\n \"description\": \"This PR adds the new feature as described in issue #123\"\n }'\n```\n\n### Approve a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_approve_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"pull_request_id\": 42\n }'\n```\n\n### Get file content from a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_get_file_from_repository\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"path\": \"README.md\",\n \"commit_revision\": \"main\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Bitbucket is connected.\n2. Call `clawlink_list_tools --integration bitbucket` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `bitbucket`.\n5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List repos → List branches → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Branch names must be unique within a repository and must not include the `refs/heads/` prefix.\n- Pull request IDs are numeric. Use `bitbucket_list_pull_requests` to find PR IDs.\n- Repository deletion does not affect forks — forks are separate copies.\n- Pagination: use the `next` field in responses to iterate through large result sets.\n- BBQL (Bitbucket Query Language) supports server-side filtering for branch names.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration bitbucket`. |\n| Missing connection | Bitbucket is not connected. Direct the user to https://claw-link.dev/dashboard?add=bitbucket. |\n| `BranchNotFound` | Branch does not exist. Check the branch name. |\n| `PullRequestNotFound` | Pull request does not exist. Check the PR ID. |\n| `RepositoryNotFound` | Repository does not exist or is not accessible. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `bitbucket`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub repository operations\n- [GitLab](https://clawhub.ai/hith3sh/gitlab-repos) — For GitLab repository operations\n- [Jira](https://clawhub.ai/hith3sh/jira-projects) — For Jira issue tracking\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1780937090154\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nBrowse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and repository maintainers use this skill to inspect Bitbucket repositories, browse files and commits, manage branches, and review pull requests from chat through an authenticated ClawLink connection.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can access repository data available to the connected Bitbucket account.
\nMitigation: Use a Bitbucket account with appropriate repository permissions and verify the target workspace, repository, branch, or pull request before calling tools.
\nRisk: Write-capable tools can create, update, merge, approve, comment on, or delete Bitbucket resources.
\nMitigation: Preview high-impact actions and require explicit user confirmation before any create, update, merge, approval, comment deletion, branch deletion, issue deletion, or repository deletion.
\nRisk: The skill requires installing and enabling the ClawLink plugin for OpenClaw tool access.
\nMitigation: Review the install commands before running them and install only the verified ClawLink plugin from ClawHub.
\n\n\n## Reference(s):
\n- [ClawHub Bitbucket skill page](https://clawhub.ai/hith3sh/bitbucket-repos)
\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)
\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)
\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)
\n- [ClawLink OpenClaw docs](https://docs.claw-link.dev/openclaw)
\n\n\n## Skill Output:
\n**Output Type(s):** [Guidance, Shell commands, API calls, Text]
\n**Output Format:** [Markdown with inline shell commands and JSON tool parameters]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Uses the live ClawLink Bitbucket tool catalog and requires an authenticated Bitbucket connection.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 6237 bytes\n\nFiles: skill-card.md (2472b), SKILL.md (16666b), _meta.json (134b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: bitbucket-repos\ndescription: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.\n---\n\n# Bitbucket\n\n\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Bitbucket |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Bitbucket |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Bitbucket again.\"\n\n## Quick Start\n\n```bash\n# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-workspace\"}'\n\n# List branches in a repository\nclawlink_call_tool --tool \"bitbucket_list_branches\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\"}'\n\n# Get a pull request\nclawlink_call_tool --tool \"bitbucket_get_pull_request\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\", \"pull_request_id\": 1}'\n```\n\n## Authentication\n\nAll Bitbucket tool calls are authenticated automatically by ClawLink using the user's connected Bitbucket account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Bitbucket API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `bitbucket` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration bitbucket\n```\n\n**Response:** Returns the live tool catalog for Bitbucket.\n\n### Reconnect\n\nIf Bitbucket tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=bitbucket\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration bitbucket`\n\n## Security& Permissions\n\n- Access is scoped to repositories and resources accessible to the connected Bitbucket account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete repository, delete branch, delete issue) are marked as high-impact and must be confirmed.\n- Repository deletion does not affect forks.\n\n## Tool Reference\n\n### Repository Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_repositories_in_workspace` | List repositories in a workspace | Read |\n| `bitbucket_list_repositories` | List public repositories | Read |\n| `bitbucket_get_repository` | Get repository metadata | Read |\n| `bitbucket_create_repository` | Create a new repository in a workspace | Write |\n| `bitbucket_delete_repository` | Permanently delete a repository | Write |\n| `bitbucket_browse_repository_path` | Get file content or list directory at a revision | Read |\n| `bitbucket_get_file_from_repository` | Get a specific file's content at a commit | Read |\n| `bitbucket_list_repository_paths` | List files and directories under a path | Read |\n\n### Branch Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_branches` | List branches with optional name filtering | Read |\n| `bitbucket_get_branch` | Get branch metadata and target commit | Read |\n| `bitbucket_create_branch` | Create a new branch from a target commit | Write |\n| `bitbucket_get_repositories_branching_model` | Get the repository's branch workflow configuration | Read |\n| `bitbucket_get_repositories_effective_branching_model` | Get effective branching model (including inheritance) | Read |\n\n### Commit Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_commits` | List commits with optional branch/path filters | Read |\n| `bitbucket_get_repositories_commit` | Get detailed commit information | Read |\n| `bitbucket_get_commit_diff` | Get the unified diff for a commit or range | Read |\n| `bitbucket_get_commit_changes` | Get changed files in a commit | Read |\n| `bitbucket_get_commit_build_status` | Get build status for a commit | Read |\n| `bitbucket_get_commit_diffstat` | Get diffstat (files changed, lines added/removed) | Read |\n\n### Pull Request Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pull_requests` | List pull requests by state (OPEN/MERGED/DECLINED) | Read |\n| `bitbucket_get_pull_request` | Get a single pull request with full details | Read |\n| `bitbucket_get_pull_request_commits` | Get commits included in a PR | Read |\n| `bitbucket_get_pull_request_diff` | Get the unified diff for a PR | Read |\n| `bitbucket_get_pull_request_diffstat` | Get diffstat for a PR | Read |\n| `bitbucket_create_pull_request` | Create a new pull request | Write |\n| `bitbucket_update_pull_request` | Update PR title, description, or reviewers | Write |\n| `bitbucket_merge_pull_request` | Merge a pull request | Write |\n| `bitbucket_approve_pull_request` | Approve a pull request | Write |\n| `bitbucket_request_pull_request_changes` | Request changes on a PR | Write |\n| `bitbucket_create_pull_request_comment` | Add a top-level or threaded comment to a PR | Write |\n| `bitbucket_delete_pull_request_comment` | Delete a PR comment | Write |\n| `bitbucket_resolve_pull_request_comment` | Resolve or reopen a PR comment thread | Write |\n\n### Issue Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_issues` | List issues with optional state/priority filters | Read |\n| `bitbucket_create_issue` | Create a new issue | Write |\n| `bitbucket_update_issue` | Update issue attributes | Write |\n| `bitbucket_delete_issue` | Permanently delete an issue | Write |\n| `bitbucket_create_issue_comment` | Add a comment to an issue | Write |\n\n### User & Workspace\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_current_user` | Get the authenticated user's profile | Read |\n| `bitbucket_list_workspaces` | List workspaces accessible to the user | Read |\n| `bitbucket_get_workspace` | Get workspace metadata | Read |\n| `bitbucket_list_workspace_members` | List members of a workspace | Read |\n| `bitbucket_list_workspace_projects` | List projects in a workspace | Read |\n\n### Pipelines & Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pipelines` | List pipeline runs for a repository | Read |\n| `bitbucket_get_repositories_pipelines2` | Get a specific pipeline's details | Read |\n| `bitbucket_list_repositories_environments` | List deployment environments | Read |\n| `bitbucket_list_deployments` | List deployment history | Read |\n\n### Code Search\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_workspaces_search_code` | Search code across all repos in a workspace | Read |\n| `bitbucket_search_user_repositories_code` | Search code in a specific user's repos | Read |\n\n## Code Examples\n\n### List branches in a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_list_branches\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"q\": \"name~\\\"feature\\\"\"\n }'\n```\n\n### Create a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_create_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"title\": \"Add new feature\",\n \"source_branch\": \"feature/new-feature\",\n \"destination_branch\": \"main\",\n \"description\": \"This PR adds the new feature as described in issue #123\"\n }'\n```\n\n### Approve a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_approve_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"pull_request_id\": 42\n }'\n```\n\n### Get file content from a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_get_file_from_repository\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"path\": \"README.md\",\n \"commit_revision\": \"main\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Bitbucket is connected.\n2. Call `clawlink_list_tools --integration bitbucket` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `bitbucket`.\n5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List repos → List branches → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Branch names must be unique within a repository and must not include the `refs/heads/` prefix.\n- Pull request IDs are numeric. Use `bitbucket_list_pull_requests` to find PR IDs.\n- Repository deletion does not affect forks — forks are separate copies.\n- Pagination: use the `next` field in responses to iterate through large result sets.\n- BBQL (Bitbucket Query Language) supports server-side filtering for branch names.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration bitbucket`. |\n| Missing connection | Bitbucket is not connected. Direct the user to https://claw-link.dev/dashboard?add=bitbucket. |\n| `BranchNotFound` | Branch does not exist. Check the branch name. |\n| `PullRequestNotFound` | Pull request does not exist. Check the PR ID. |\n| `RepositoryNotFound` | Repository does not exist or is not accessible. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `bitbucket`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub repository operations\n- [GitLab](https://clawhub.ai/hith3sh/gitlab-repos) — For GitLab repository operations\n- [Jira](https://clawhub.ai/hith3sh/jira-projects) — For Jira issue tracking\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780935959867\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nBrowse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to inspect Bitbucket repository contents, manage branches, review pull requests, and coordinate repository workflows through authenticated Bitbucket Cloud API calls.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill uses ClawLink to broker OAuth access to Bitbucket repositories reachable by the connected account.
\nMitigation: Connect a Bitbucket account with the minimum permissions needed and avoid highly privileged workspace accounts unless those actions are intended.
\nRisk: Repository, branch, pull request, and issue write operations can change or delete Bitbucket resources.
\nMitigation: Review previews carefully and require explicit confirmation before approving writes or deletions.
\n\n\n## Reference(s):
\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)
\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)
\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Verification](https://claw-link.dev/verify)
\n\n\n## Skill Output:
\n**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown with inline shell commands and tool-call examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May guide authenticated Bitbucket read and write workflows through ClawLink after account connection.]
\n\n## Skill Version(s):
\n1.0.1 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.1: 3 files, 6185 bytes\n\nFiles: skill-card.md (2385b), SKILL.md (16551b), _meta.json (134b)\n\nFile v0.1.1:SKILL.md\n\n---\nname: bitbucket-repos\ndescription: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.\n---\n\n# Bitbucket\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev) for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Bitbucket |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Bitbucket |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Bitbucket again.\"\n\n## Quick Start\n\n```bash\n# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-workspace\"}'\n\n# List branches in a repository\nclawlink_call_tool --tool \"bitbucket_list_branches\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\"}'\n\n# Get a pull request\nclawlink_call_tool --tool \"bitbucket_get_pull_request\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\", \"pull_request_id\": 1}'\n```\n\n## Authentication\n\nAll Bitbucket tool calls are authenticated automatically by ClawLink using the user's connected Bitbucket account.\n\n**No API key is required in chat.** ClawLink stores the OAuth token securely and injects it into every Bitbucket API request on the user's behalf.\n\n### Getting Connected\n\n1. Install the ClawLink plugin (see Install above).\n2. Pair the plugin with `clawlink_begin_pairing` if it is not configured yet.\n3. Open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket.\n4. Call `clawlink_list_integrations` to verify the connection is active.\n\n## Connection Management\n\n### List Connections\n\n```bash\nclawlink_list_integrations\n```\n\n**Response:** Returns all connected integrations. Look for `bitbucket` in the list.\n\n### Verify Connection\n\n```bash\nclawlink_list_tools --integration bitbucket\n```\n\n**Response:** Returns the live tool catalog for Bitbucket.\n\n### Reconnect\n\nIf Bitbucket tools are missing or the connection shows an error:\n\n1. Direct the user to https://claw-link.dev/dashboard?add=bitbucket\n2. After they confirm, call `clawlink_list_integrations` to verify\n3. Then call `clawlink_list_tools --integration bitbucket`\n\n## Security& Permissions\n\n- Access is scoped to repositories and resources accessible to the connected Bitbucket account.\n- **All write operations require explicit user confirmation.** Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.\n- Destructive actions (delete repository, delete branch, delete issue) are marked as high-impact and must be confirmed.\n- Repository deletion does not affect forks.\n\n## Tool Reference\n\n### Repository Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_repositories_in_workspace` | List repositories in a workspace | Read |\n| `bitbucket_list_repositories` | List public repositories | Read |\n| `bitbucket_get_repository` | Get repository metadata | Read |\n| `bitbucket_create_repository` | Create a new repository in a workspace | Write |\n| `bitbucket_delete_repository` | Permanently delete a repository | Write |\n| `bitbucket_browse_repository_path` | Get file content or list directory at a revision | Read |\n| `bitbucket_get_file_from_repository` | Get a specific file's content at a commit | Read |\n| `bitbucket_list_repository_paths` | List files and directories under a path | Read |\n\n### Branch Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_branches` | List branches with optional name filtering | Read |\n| `bitbucket_get_branch` | Get branch metadata and target commit | Read |\n| `bitbucket_create_branch` | Create a new branch from a target commit | Write |\n| `bitbucket_get_repositories_branching_model` | Get the repository's branch workflow configuration | Read |\n| `bitbucket_get_repositories_effective_branching_model` | Get effective branching model (including inheritance) | Read |\n\n### Commit Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_commits` | List commits with optional branch/path filters | Read |\n| `bitbucket_get_repositories_commit` | Get detailed commit information | Read |\n| `bitbucket_get_commit_diff` | Get the unified diff for a commit or range | Read |\n| `bitbucket_get_commit_changes` | Get changed files in a commit | Read |\n| `bitbucket_get_commit_build_status` | Get build status for a commit | Read |\n| `bitbucket_get_commit_diffstat` | Get diffstat (files changed, lines added/removed) | Read |\n\n### Pull Request Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pull_requests` | List pull requests by state (OPEN/MERGED/DECLINED) | Read |\n| `bitbucket_get_pull_request` | Get a single pull request with full details | Read |\n| `bitbucket_get_pull_request_commits` | Get commits included in a PR | Read |\n| `bitbucket_get_pull_request_diff` | Get the unified diff for a PR | Read |\n| `bitbucket_get_pull_request_diffstat` | Get diffstat for a PR | Read |\n| `bitbucket_create_pull_request` | Create a new pull request | Write |\n| `bitbucket_update_pull_request` | Update PR title, description, or reviewers | Write |\n| `bitbucket_merge_pull_request` | Merge a pull request | Write |\n| `bitbucket_approve_pull_request` | Approve a pull request | Write |\n| `bitbucket_request_pull_request_changes` | Request changes on a PR | Write |\n| `bitbucket_create_pull_request_comment` | Add a top-level or threaded comment to a PR | Write |\n| `bitbucket_delete_pull_request_comment` | Delete a PR comment | Write |\n| `bitbucket_resolve_pull_request_comment` | Resolve or reopen a PR comment thread | Write |\n\n### Issue Operations\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_issues` | List issues with optional state/priority filters | Read |\n| `bitbucket_create_issue` | Create a new issue | Write |\n| `bitbucket_update_issue` | Update issue attributes | Write |\n| `bitbucket_delete_issue` | Permanently delete an issue | Write |\n| `bitbucket_create_issue_comment` | Add a comment to an issue | Write |\n\n### User & Workspace\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_current_user` | Get the authenticated user's profile | Read |\n| `bitbucket_list_workspaces` | List workspaces accessible to the user | Read |\n| `bitbucket_get_workspace` | Get workspace metadata | Read |\n| `bitbucket_list_workspace_members` | List members of a workspace | Read |\n| `bitbucket_list_workspace_projects` | List projects in a workspace | Read |\n\n### Pipelines & Deployments\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_list_pipelines` | List pipeline runs for a repository | Read |\n| `bitbucket_get_repositories_pipelines2` | Get a specific pipeline's details | Read |\n| `bitbucket_list_repositories_environments` | List deployment environments | Read |\n| `bitbucket_list_deployments` | List deployment history | Read |\n\n### Code Search\n\n| Tool | Description | Mode |\n|------|-------------|------|\n| `bitbucket_get_workspaces_search_code` | Search code across all repos in a workspace | Read |\n| `bitbucket_search_user_repositories_code` | Search code in a specific user's repos | Read |\n\n## Code Examples\n\n### List branches in a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_list_branches\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"q\": \"name~\\\"feature\\\"\"\n }'\n```\n\n### Create a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_create_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"title\": \"Add new feature\",\n \"source_branch\": \"feature/new-feature\",\n \"destination_branch\": \"main\",\n \"description\": \"This PR adds the new feature as described in issue #123\"\n }'\n```\n\n### Approve a pull request\n\n```bash\nclawlink_call_tool --tool \"bitbucket_approve_pull_request\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"pull_request_id\": 42\n }'\n```\n\n### Get file content from a repository\n\n```bash\nclawlink_call_tool --tool \"bitbucket_get_file_from_repository\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"path\": \"README.md\",\n \"commit_revision\": \"main\"\n }'\n```\n\n## Discovery Workflow\n\n1. Call `clawlink_list_integrations` to confirm Bitbucket is connected.\n2. Call `clawlink_list_tools --integration bitbucket` to see the live catalog.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `bitbucket`.\n5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n\n## Execution Workflow\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ READ OPERATIONS (Safe) │\n│ list → get → search → describe → call │\n│ │\n│ Example: List repos → List branches → Show results │\n└─────────────────────────────────────────────────────────────┘\n │\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ WRITE OPERATIONS (Require Confirmation) │\n│ list → get → describe → preview → confirm → call │\n│ │\n│ Example: Describe tool → Preview changes → User approves │\n│ → Execute update │\n└─────────────────────────────────────────────────────────────┘\n```\n\n1. For unfamiliar tools, ambiguous requests, or any write action, call `clawlink_describe_tool` first.\n2. Use the returned guidance, schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups` to shape the call.\n3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first.\n5. Execute with `clawlink_call_tool`. Pass confirmation only after the preview matches the user's intent.\n6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## Notes\n\n- Branch names must be unique within a repository and must not include the `refs/heads/` prefix.\n- Pull request IDs are numeric. Use `bitbucket_list_pull_requests` to find PR IDs.\n- Repository deletion does not affect forks — forks are separate copies.\n- Pagination: use the `next` field in responses to iterate through large result sets.\n- BBQL (Bitbucket Query Language) supports server-side filtering for branch names.\n\n## Error Handling\n\n| Status / Error | Meaning |\n|----------------|---------|\n| Tool not found | The tool name does not exist in the current catalog. Verify with `clawlink_list_tools --integration bitbucket`. |\n| Missing connection | Bitbucket is not connected. Direct the user to https://claw-link.dev/dashboard?add=bitbucket. |\n| `BranchNotFound` | Branch does not exist. Check the branch name. |\n| `PullRequestNotFound` | Pull request does not exist. Check the PR ID. |\n| `RepositoryNotFound` | Repository does not exist or is not accessible. |\n| `InvalidArgument` | Invalid parameter or missing required field. Review the tool schema with `clawlink_describe_tool`. |\n| Write rejected | User did not confirm a write action. Always confirm before executing writes. |\n\n### Troubleshooting: Tools Not Visible\n\n1. Check that the ClawLink plugin is installed:\n ```bash\n openclaw plugins list\n ```\n2. If the plugin is installed but tools are missing, tell the user to send `/new` as a standalone message to reload the catalog.\n3. If a fresh chat does not help, run:\n ```bash\n openclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\n openclaw gateway restart\n ```\n4. After restart, tell the user to send `/new` again and retry.\n\n### Troubleshooting: Invalid Tool Call\n\n1. Ensure the integration slug is exactly `bitbucket`.\n2. Use `clawlink_describe_tool` to verify parameter names and types before calling.\n3. For write operations, always call `clawlink_preview_tool` first.\n\n## Resources\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n\n## Related Skills\n\n- [GitHub](https://clawhub.ai/hith3sh/github-repos) — For GitHub repository operations\n- [GitLab](https://clawhub.ai/hith3sh/gitlab-repos) — For GitLab repository operations\n- [Jira](https://clawhub.ai/hith3sh/jira-projects) — For Jira issue tracking\n\n---\n\n**Powered by [ClawLink](https://claw-link.dev)** — an integration hub for OpenClaw\n\n\n\nFile v0.1.1:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"0.1.1\",\n \"publishedAt\": 1780838831903\n}\n\nFile v0.1.1:skill-card.md\n\n## Description:
\nBrowse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and engineering teams use this skill to browse Bitbucket Cloud repositories, inspect files and branches, review pull requests, and coordinate code workflows through ClawLink-authenticated Bitbucket tools.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill enables OAuth-authenticated Bitbucket repository access, including write actions.
\nMitigation: Review the Bitbucket OAuth permissions during connection and confirm create, update, merge, or delete actions before execution.
\nRisk: Access remains available while the ClawLink plugin and OAuth connection stay active.
\nMitigation: Remove the ClawLink plugin or revoke the OAuth connection when this access is no longer needed.
\n\n\n## Reference(s):
\n- [ClawHub Bitbucket skill page](https://clawhub.ai/hith3sh/bitbucket-repos)
\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)
\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)
\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink](https://claw-link.dev)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON parameter examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [May include ClawLink tool names, Bitbucket object identifiers, repository file content, diffs, and confirmation prompts.]
\n\n## Skill Version(s):
\n0.1.1 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v0.1.0: 3 files, 3568 bytes\n\nFiles: skill-card.md (2443b), SKILL.md (5162b), _meta.json (134b)\n\nFile v0.1.0:SKILL.md\n\n---\nname: bitbucket-repos\ndescription: Browse repositories, manage branches, review pull requests, and work with source code and repository workflows — powered by ClawLink.\n---\n\n# Bitbucket via ClawLink\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows.\n\nPowered by [ClawLink](https://claw-link.dev), an integration hub for OpenClaw that handles hosted connection flows and credentials so you don't need to configure Bitbucket API access yourself.\n\n## Quick start\n\n1. Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`\n2. Start a fresh OpenClaw chat if the plugin was just installed and ClawLink tools are not visible yet\n3. If ClawLink is not configured, call `clawlink_begin_pairing`\n4. Tell the user to open the returned pairing URL, sign in to ClawLink if needed, and approve the device\n5. After the user confirms approval, call `clawlink_get_pairing_status`\n6. Tell the user to connect Bitbucket at [claw-link.dev/dashboard?add=bitbucket](https://claw-link.dev/dashboard?add=bitbucket)\n7. When the user confirms Bitbucket is connected, call `clawlink_list_integrations` and then `clawlink_list_tools` with the `bitbucket` integration slug\n\n## Setup details\n\n### Installing the plugin\n\nIf the ClawLink plugin is not installed yet, tell the user to run:\n\n```\nopenclaw plugins install clawhub:clawlink-plugin\n```\n\nIf the current chat started before the plugin was installed and ClawLink tools are still unavailable, tell the user to start a fresh chat so OpenClaw reloads the plugin tool catalog.\n\n### Pairing ClawLink\n\nIf ClawLink reports that the plugin is not configured, the plugin has not been paired with the user's ClawLink account yet.\n\n1. Call `clawlink_begin_pairing`.\n2. Tell the user to open the returned pairing URL in their browser.\n3. The user signs in to ClawLink if needed and approves the OpenClaw device.\n4. After the user confirms approval, call `clawlink_get_pairing_status` to finish local setup.\n\nThe resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`. The user should not paste raw credentials into chat.\n\n### Connecting Bitbucket\n\nTell the user to open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket there. The page opens the add-connection panel filtered to Bitbucket. ClawLink's hosted page runs the hosted OAuth flow — the user clicks through the Bitbucket login and authorization screen. When they confirm it is done, call `clawlink_list_integrations` to verify, then call `clawlink_list_tools` with integration `bitbucket`.\n\n## Using Bitbucket tools\n\nClawLink provides tools dynamically based on what the user has connected. You do not need to know tool names or schemas in advance.\n\n### Discovery\n\n1. Call `clawlink_list_integrations` to confirm Bitbucket is connected.\n2. Call `clawlink_list_tools` with integration `bitbucket`.\n3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.\n4. If the user describes a capability but the exact tool is unclear, call `clawlink_search_tools` with a short query and integration `bitbucket`.\n5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n\n### Execution\n\n1. Call `clawlink_describe_tool` before using an unfamiliar tool, before any write, or when the request is ambiguous.\n2. Use the returned schema, `whenToUse`, `askBefore`, `safeDefaults`, `examples`, and `followups`.\n3. Prefer read, list, search, and get operations before writes.\n4. For writes or anything marked as requiring confirmation, call `clawlink_preview_tool` first, then confirm with the user.\n5. Execute with `clawlink_call_tool`.\n6. If it fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.\n\n## What you can do\n\nTypical Bitbucket tasks (actual availability depends on the user's connected account, permissions, scopes, and current ClawLink tool catalog):\n\n- Browse repositories and inspect files or directories\n- Create and manage branches\n- Review pull requests and approvals\n- Read repository activity and metadata\n- Coordinate code and repository workflows\n- Inspect repo state before write actions\n\n## Rules\n\n- Always use ClawLink tools for Bitbucket. Do not ask the user for separate Bitbucket credentials.\n- Do not claim a capability is missing without checking the live ClawLink catalog in the current turn.\n- Do not invent slash commands or ask the user to paste raw credentials.\n- Ask for confirmation before destructive, external-facing, or bulk write actions.\n- If Bitbucket is not connected, direct the user to https://claw-link.dev/dashboard?add=bitbucket.\n- Never echo or repeat the user's ClawLink credential.\n\n## Resources\n\n- ClawLink: https://claw-link.dev\n- ClawLink Docs: https://docs.claw-link.dev/openclaw\n- ClawLink Verification: https://claw-link.dev/verify\n- ClawLink Source: https://github.com/hith3sh/clawlink\n- Bitbucket Cloud REST API: https://developer.atlassian.com/cloud/bitbucket/rest/\n\nFile v0.1.0:_meta.json\n\n{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"0.1.0\",\n \"publishedAt\": 1778077317220\n}\n\nFile v0.1.0:skill-card.md\n\n## Description:
\nBrowse repositories, manage branches, review pull requests, and work with source code and repository workflows through ClawLink.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[hith3sh](https://clawhub.ai/user/hith3sh)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nDevelopers and repository maintainers use this skill to work with Bitbucket repositories from an agent chat, including browsing code, managing branches, reviewing pull requests, and coordinating repository workflows through ClawLink.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: ClawLink and Bitbucket OAuth access can expose repositories and sensitive account-scoped data.
\nMitigation: Install only if ClawLink is trusted to mediate Bitbucket access, review OAuth scopes during connection, and connect only workspaces intended for agent-assisted repository management.
\nRisk: Write, destructive, external-facing, or bulk Bitbucket actions can change repository state.
\nMitigation: Use read and inspection tools first; preview write actions and confirm with the user before execution.
\nRisk: Tool availability depends on the live ClawLink catalog, connected account, permissions, and scopes.
\nMitigation: Discover and describe Bitbucket tools in the current session before use, and report live tool errors directly.
\n\n\n## Reference(s):
\n- [ClawLink Docs](https://docs.claw-link.dev/openclaw)
\n- [ClawLink Source](https://github.com/hith3sh/clawlink)
\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown guidance with inline shell commands, links, and ClawLink tool names]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Guidance depends on the user's connected Bitbucket account, OAuth scopes, permissions, and the current ClawLink tool catalog.]
\n\n## Skill Version(s):
\n0.1.0 (source: server release evidence)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
","readmeExcerpt":"Skill: Bitbucket Owner: hith3sh Summary: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want t... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:04:22.071Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sou","codeSnippets":[],"executableExamples":[{"language":"text","snippet":"┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘"},{"language":"bash","snippet":"openclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart"},{"language":"bash","snippet":"# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-workspace\"}'\n\n# List branches in a repository\nclawlink_call_tool --tool \"bitbucket_list_branches\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\"}'\n\n# Get a pull request\nclawlink_call_tool --tool \"bitbucket_get_pull_request\" --params '{\"workspace\": \"your-workspace\", \"repo_slug\": \"your-repo\", \"pull_request_id\": 1}'"},{"language":"bash","snippet":"clawlink_list_integrations"},{"language":"bash","snippet":"clawlink_list_tools --integration bitbucket"},{"language":"bash","snippet":"clawlink_call_tool --tool \"bitbucket_list_branches\" \\\n --params '{\n \"workspace\": \"your-workspace\",\n \"repo_slug\": \"your-repo\",\n \"q\": \"name~\\\"feature\\\"\"\n }'"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: bitbucket-repos\ndescription: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want to inspect repo contents, create branches, manage pull requests, or coordinate code workflows.\n---\n\n# Bitbucket\n\n\n\nWork with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.\n\nThis skill uses [ClawLink](https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=bitbucket-repos) for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.\n\n### Setup in 3 Steps\n\n| Step 1: Install | Step 2: Pair Account | Step 3: Connect Bitbucket |\n|:---:|:---:|:---:|\n|  |  | *App-specific connection GIF coming soon* |\n| Run the install command in OpenClaw | Sign in and approve the device | Open the dashboard and connect Bitbucket |\n\n## How It Works\n\n```\n┌─────────────────┐ ┌──────────────┐ ┌──────────────────────┐\n│ OpenClaw │────▶│ ClawLink │────▶│ Bitbucket Cloud API │\n│ (User Chat) │ │ (OAuth) │ │ (Repos/PRs/Branches)│\n└─────────────────┘ └──────────────┘ └──────────────────────┘\n │ │ │\n │ 1. Install Plugin │ │\n │ 2. Pair Device │ │\n │ 3. Connect Bitbucket │ │\n │ │ 4. Secure Token │\n │ │ 5. Proxy Requests │\n │ │ │\n ▼ ▼ ▼\n ┌──────────┐ ┌──────────┐ ┌──────────┐\n │ SKILL │ │ Dashboard│ │ Bitbucket│\n │ File │ │ Auth │ │ Cloud │\n └──────────┘ └──────────┘ └──────────┘\n```\n\n## Install\n\nInstall the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.\n\n```bash\nopenclaw plugins install clawhub:clawlink-plugin\nopenclaw config set tools.alsoAllow '[\"clawlink-plugin\"]' --strict-json\nopenclaw gateway restart\n```\n\nThen tell the user: \"OpenClaw has been restarted. Send `/new` as a standalone message to start a fresh chat, then ask for Bitbucket again.\"\n\n## Quick Start\n\n```bash\n# List repositories in a workspace\nclawlink_call_tool --tool \"bitbucket_list_repositories_in_workspace\" --params '{\"workspace\": \"your-wo"},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn713pxvayh8fjhb503zjb8yxh815j54\",\n \"slug\": \"bitbucket-repos\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1780988662071\n}"},{"path":"skill-card.md","content":"## Description:\n\nBrowse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[hith3sh](https://clawhub.ai/user/hith3sh)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers and engineers use this skill to inspect Bitbucket repository contents, manage branches, review pull requests, and coordinate code workflows from chat through ClawLink and the Bitbucket Cloud API.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill installs and persistently allowlists an unpinned external plugin with OAuth-backed repository write capabilities.\n\nMitigation: Verify the ClawLink plugin publisher, prefer a pinned and reviewed version when available, and remove the plugin allowlist if behavior does not match expectations.\n\nRisk: Repository, branch, pull request, and issue write operations can change or delete Bitbucket resources accessible to the connected account.\n\nMitigation: Connect Bitbucket with the minimum scopes needed and review every preview before approving write operations.\n\nRisk: OAuth access may remain active after installation.\n\nMitigation: Be prepared to revoke the OAuth integration if access is no longer needed or if any activity looks wrong.\n\n## Reference(s):\n\n- [Bitbucket Cloud REST API](https://developer.atlassian.com/cloud/bitbucket/rest/)\n- [Bitbucket Repository API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-repositories/)\n- [Bitbucket Pull Request API](https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/)\n- [ClawLink OpenClaw Docs](https://docs.claw-link.dev/openclaw)\n- [ClawHub Skill Page](https://clawhub.ai/hith3sh/skills/bitbucket-repos)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Shell commands, Configuration, API Calls]\n\n**Output Format:** [Markdown with inline bash and JSON snippets]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires review and explicit confirmation before write operations.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release evidence)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want t... Skill: Bitbucket Owner: hith3sh Summary: Browse Bitbucket repositories, manage branches, review pull requests, and work with source code via the Bitbucket Cloud API. Use this skill when users want t... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-06-09T07:04:22.071Z | user Add UTM attribution tags (utm_source=clawhub) to ClawLink branding links so visits from this skill page are tracked as a distinct traffic sou","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1055,"uniquenessScore":52,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:42:49.453Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T12:42:49.453Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-09T19:22:28.759Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}