[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M2KWAD7D31XCZ7WSG0ACG4":3,"skill-same:01M6M2KWAD7D31XCZ7WSG0ACG4":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":13,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6M2KWAD7D31XCZ7WSG0ACG4","seedance-interview",null,"This skill should be used when the user has a vague Seedance 2.0 video idea and asks for creative guidance, story development, scene planning, a director interview, or help turning an undeveloped concept into a production-ready prompt, especially when the user has no film or storytelling background.","endman100\u002Fskill-router-nexus","endman100","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F31997019?v=4","01M6KPDX17BYDWW4RRB0TNGGMX","01M6KPDX64Y2QBEWVFG5W5PWPF",0,"MIT","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FVideo-Generation\u002Fseedance-20\u002Fskills\u002Fseedance-interview\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"seedance interview","interview","seedance","direction","when","creative-direction","vague","for","concept","production-ready","true","FiLM","github","director","ready","prompt","Video","brief","help","planning","development","2026-11-10 10:12:30",false,"---\nname: bitbucket-automation\ndescription: \"Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.\"\nrisk: unknown\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Bitbucket Automation via Rube MCP\n\nAutomate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Bitbucket connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n3. If connection is not ACTIVE, follow the returned auth link to complete Bitbucket OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Pull Requests\n\n**When to use**: User wants to create, review, or inspect pull requests\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - Discover accessible workspaces [Prerequisite]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - Find the target repository [Prerequisite]\n3. `BITBUCKET_LIST_BRANCHES` - Verify source and destination branches exist [Prerequisite]\n4. `BITBUCKET_CREATE_PULL_REQUEST` - Create a new PR with title, source branch, and optional reviewers [Required]\n5. `BITBUCKET_LIST_PULL_REQUESTS` - List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional]\n6. `BITBUCKET_GET_PULL_REQUEST` - Get full details of a specific PR by ID [Optional]\n7. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Fetch unified diff for code review [Optional]\n8. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get changed files with lines added\u002Fremoved [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug or UUID (required for all operations)\n- `repo_slug`: URL-friendly repository name\n- `source_branch`: Branch with changes to merge\n- `destination_branch`: Target branch (defaults to repo main branch if omitted)\n- `reviewers`: List of objects with `uuid` field for reviewer assignment\n- `state`: Filter for LIST_PULL_REQUESTS - `OPEN`, `MERGED`, or `DECLINED`\n- `max_chars`: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffs\n\n**Pitfalls**:\n- `reviewers` expects an array of objects with `uuid` key, NOT usernames: `[{\"uuid\": \"{...}\"}]`\n- UUID format must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- `destination_branch` defaults to the repo's main branch if omitted, which may not be `main`\n- `pull_request_id` is an integer for GET\u002FDIFF operations but comes back as part of PR listing\n- Large diffs can overwhelm context; always set `max_chars` (e.g., 50000) on GET_PULL_REQUEST_DIFF\n\n### 2. Manage Repositories and Workspaces\n\n**When to use**: User wants to list, create, or delete repositories or explore workspaces\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - List all accessible workspaces [Required]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - List repos with optional BBQL filtering [Required]\n3. `BITBUCKET_CREATE_REPOSITORY` - Create a new repo with language, privacy, and project settings [Optional]\n4. `BITBUCKET_DELETE_REPOSITORY` - Permanently delete a repository (irreversible) [Optional]\n5. `BITBUCKET_LIST_WORKSPACE_MEMBERS` - List members for reviewer assignment or access checks [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug (find via LIST_WORKSPACES)\n- `repo_slug`: URL-friendly name for create\u002Fdelete\n- `q`: BBQL query filter (e.g., `name~\"api\"`, `project.key=\"PROJ\"`, `is_private=true`)\n- `role`: Filter repos by user role: `member`, `contributor`, `admin`, `owner`\n- `sort`: Sort field with optional `-` prefix for descending (e.g., `-updated_on`)\n- `is_private`: Boolean for repository visibility (defaults to `true`)\n- `project_key`: Bitbucket project key; omit to use workspace's oldest project\n\n**Pitfalls**:\n- `BITBUCKET_DELETE_REPOSITORY` is **irreversible** and does not affect forks\n- BBQL string values MUST be enclosed in double quotes: `name~\"my-repo\"` not `name~my-repo`\n- `repository` is NOT a valid BBQL field; use `name` instead\n- Default pagination is 10 results; set `pagelen` explicitly for complete listings\n- `CREATE_REPOSITORY` defaults to private; set `is_private: false` for public repos\n\n### 3. Manage Issues\n\n**When to use**: User wants to create, update, list, or comment on repository issues\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_ISSUES` - List issues with optional filters for state, priority, kind, assignee [Required]\n2. `BITBUCKET_CREATE_ISSUE` - Create a new issue with title, content, priority, and kind [Required]\n3. `BITBUCKET_UPDATE_ISSUE` - Modify issue attributes (state, priority, assignee, etc.) [Optional]\n4. `BITBUCKET_CREATE_ISSUE_COMMENT` - Add a markdown comment to an existing issue [Optional]\n5. `BITBUCKET_DELETE_ISSUE` - Permanently delete an issue [Optional]\n\n**Key parameters**:\n- `issue_id`: String identifier for the issue\n- `title`, `content`: Required for creation\n- `kind`: `bug`, `enhancement`, `proposal`, or `task`\n- `priority`: `trivial`, `minor`, `major`, `critical`, or `blocker`\n- `state`: `new`, `open`, `resolved`, `on hold`, `invalid`, `duplicate`, `wontfix`, `closed`\n- `assignee`: Bitbucket username for CREATE; `assignee_account_id` (UUID) for UPDATE\n- `due_on`: ISO 8601 format date string\n\n**Pitfalls**:\n- Issue tracker must be enabled on the repository (`has_issues: true`) or API calls will fail\n- `CREATE_ISSUE` uses `assignee` (username string), but `UPDATE_ISSUE` uses `assignee_account_id` (UUID) -- they are different fields\n- `DELETE_ISSUE` is permanent with no undo\n- `state` values include spaces: `\"on hold\"` not `\"on_hold\"`\n- Filtering by `assignee` in LIST_ISSUES uses account ID, not username; use `\"null\"` string for unassigned\n\n### 4. Manage Branches\n\n**When to use**: User wants to create branches or explore branch structure\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_BRANCHES` - List branches with optional BBQL filter and sorting [Required]\n2. `BITBUCKET_CREATE_BRANCH` - Create a new branch from a specific commit hash [Required]\n\n**Key parameters**:\n- `name`: Branch name without `refs\u002Fheads\u002F` prefix (e.g., `feature\u002Fnew-login`)\n- `target_hash`: Full SHA1 commit hash to branch from (must exist in repo)\n- `q`: BBQL filter (e.g., `name~\"feature\u002F\"`, `name=\"main\"`)\n- `sort`: Sort by `name` or `-target.date` (descending commit date)\n- `pagelen`: 1-100 results per page (default is 10)\n\n**Pitfalls**:\n- `CREATE_BRANCH` requires a full commit hash, NOT a branch name as `target_hash`\n- Do NOT include `refs\u002Fheads\u002F` prefix in branch names\n- Branch names must follow Bitbucket naming conventions (alphanumeric, `\u002F`, `.`, `_`, `-`)\n- BBQL string values need double quotes: `name~\"feature\u002F\"` not `name~feature\u002F`\n\n### 5. Review Pull Requests with Comments\n\n**When to use**: User wants to add review comments to pull requests, including inline code comments\n\n**Tool sequence**:\n1. `BITBUCKET_GET_PULL_REQUEST` - Get PR details and verify it exists [Prerequisite]\n2. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Review the actual code changes [Prerequisite]\n3. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get list of changed files [Optional]\n4. `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` - Post review comments [Required]\n\n**Key parameters**:\n- `pull_request_id`: String ID of the PR\n- `content_raw`: Markdown-formatted comment text\n- `content_markup`: Defaults to `markdown`; also supports `plaintext`\n- `inline`: Object with `path`, `from`, `to` for inline code comments\n- `parent_comment_id`: Integer ID for threaded replies to existing comments\n\n**Pitfalls**:\n- `pull_request_id` is a string in CREATE_PULL_REQUEST_COMMENT but an integer in GET_PULL_REQUEST\n- Inline comments require `inline.path` at minimum; `from`\u002F`to` are optional line numbers\n- `parent_comment_id` creates a threaded reply; omit for top-level comments\n- Line numbers in inline comments reference the diff, not the source file\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve human-readable names to IDs before operations:\n- **Workspace**: `BITBUCKET_LIST_WORKSPACES` to get workspace slugs\n- **Repository**: `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` with `q` filter to find repo slugs\n- **Branch**: `BITBUCKET_LIST_BRANCHES` to verify branch existence before PR creation\n- **Members**: `BITBUCKET_LIST_WORKSPACE_MEMBERS` to get UUIDs for reviewer assignment\n\n### Pagination\nBitbucket uses page-based pagination (not cursor-based):\n- Use `page` (starts at 1) and `pagelen` (items per page) parameters\n- Default page size is typically 10; set `pagelen` explicitly (max 50 for PRs, 100 for others)\n- Check response for `next` URL or total count to determine if more pages exist\n- Always iterate through all pages for complete results\n\n### BBQL Filtering\nBitbucket Query Language is available on list endpoints:\n- String values MUST use double quotes: `name~\"pattern\"`\n- Operators: `=` (exact), `~` (contains), `!=` (not equal), `>`, `>=`, `\u003C`, `\u003C=`\n- Combine with `AND` \u002F `OR`: `name~\"api\" AND is_private=true`\n\n## Known Pitfalls\n\n### ID Formats\n- Workspace: slug string (e.g., `my-workspace`) or UUID in braces (`{uuid}`)\n- Reviewer UUIDs must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- Issue IDs are strings; PR IDs are integers in some tools, strings in others\n- Commit hashes must be full SHA1 (40 characters)\n\n### Parameter Quirks\n- `assignee` vs `assignee_account_id`: CREATE_ISSUE uses username, UPDATE_ISSUE uses UUID\n- `state` values for issues include spaces: `\"on hold\"`, not `\"on_hold\"`\n- `destination_branch` omission defaults to repo main branch, not `main` literally\n- BBQL `repository` is not a valid field -- use `name`\n\n### Rate Limits\n- Bitbucket Cloud API has rate limits; large batch operations should include delays\n- Paginated requests count against rate limits; minimize unnecessary page fetches\n\n### Destructive Operations\n- `BITBUCKET_DELETE_REPOSITORY` is irreversible and does not remove forks\n- `BITBUCKET_DELETE_ISSUE` is permanent with no recovery option\n- Always confirm with the user before executing delete operations\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List workspaces | `BITBUCKET_LIST_WORKSPACES` | `q`, `sort` |\n| List repos | `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` | `workspace`, `q`, `role` |\n| Create repo | `BITBUCKET_CREATE_REPOSITORY` | `workspace`, `repo_slug`, `is_private` |\n| Delete repo | `BITBUCKET_DELETE_REPOSITORY` | `workspace`, `repo_slug` |\n| List branches | `BITBUCKET_LIST_BRANCHES` | `workspace`, `repo_slug`, `q` |\n| Create branch | `BITBUCKET_CREATE_BRANCH` | `workspace`, `repo_slug`, `name`, `target_hash` |\n| List PRs | `BITBUCKET_LIST_PULL_REQUESTS` | `workspace`, `repo_slug`, `state` |\n| Create PR | `BITBUCKET_CREATE_PULL_REQUEST` | `workspace`, `repo_slug`, `title`, `source_branch` |\n| Get PR details | `BITBUCKET_GET_PULL_REQUEST` | `workspace`, `repo_slug`, `pull_request_id` |\n| Get PR diff | `BITBUCKET_GET_PULL_REQUEST_DIFF` | `workspace`, `repo_slug`, `pull_request_id`, `max_chars` |\n| Get PR diffstat | `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` | `workspace`, `repo_slug`, `pull_request_id` |\n| Comment on PR | `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` | `workspace`, `repo_slug`, `pull_request_id`, `content_raw` |\n| List issues | `BITBUCKET_LIST_ISSUES` | `workspace`, `repo_slug`, `state`, `priority` |\n| Create issue | `BITBUCKET_CREATE_ISSUE` | `workspace`, `repo_slug`, `title`, `content` |\n| Update issue | `BITBUCKET_UPDATE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| Comment on issue | `BITBUCKET_CREATE_ISSUE_COMMENT` | `workspace`, `repo_slug`, `issue_id`, `content` |\n| Delete issue | `BITBUCKET_DELETE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| List members | `BITBUCKET_LIST_WORKSPACE_MEMBERS` | `workspace` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Bitbucket Automation via Rube MCP\n\nAutomate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Bitbucket connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n3. If connection is not ACTIVE, follow the returned auth link to complete Bitbucket OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Pull Requests\n\n**When to use**: User wants to create, review, or inspect pull requests\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - Discover accessible workspaces [Prerequisite]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - Find the target repository [Prerequisite]\n3. `BITBUCKET_LIST_BRANCHES` - Verify source and destination branches exist [Prerequisite]\n4. `BITBUCKET_CREATE_PULL_REQUEST` - Create a new PR with title, source branch, and optional reviewers [Required]\n5. `BITBUCKET_LIST_PULL_REQUESTS` - List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional]\n6. `BITBUCKET_GET_PULL_REQUEST` - Get full details of a specific PR by ID [Optional]\n7. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Fetch unified diff for code review [Optional]\n8. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get changed files with lines added\u002Fremoved [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug or UUID (required for all operations)\n- `repo_slug`: URL-friendly repository name\n- `source_branch`: Branch with changes to merge\n- `destination_branch`: Target branch (defaults to repo main branch if omitted)\n- `reviewers`: List of objects with `uuid` field for reviewer assignment\n- `state`: Filter for LIST_PULL_REQUESTS - `OPEN`, `MERGED`, or `DECLINED`\n- `max_chars`: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffs\n\n**Pitfalls**:\n- `reviewers` expects an array of objects with `uuid` key, NOT usernames: `[{\"uuid\": \"{...}\"}]`\n- UUID format must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- `destination_branch` defaults to the repo's main branch if omitted, which may not be `main`\n- `pull_request_id` is an integer for GET\u002FDIFF operations but comes back as part of PR listing\n- Large diffs can overwhelm context; always set `max_chars` (e.g., 50000) on GET_PULL_REQUEST_DIFF\n\n### 2. Manage Repositories and Workspaces\n\n**When to use**: User wants to list, create, or delete repositories or explore workspaces\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - List all accessible workspaces [Required]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - List repos with optional BBQL filtering [Required]\n3. `BITBUCKET_CREATE_REPOSITORY` - Create a new repo with language, privacy, and project settings [Optional]\n4. `BITBUCKET_DELETE_REPOSITORY` - Permanently delete a repository (irreversible) [Optional]\n5. `BITBUCKET_LIST_WORKSPACE_MEMBERS` - List members for reviewer assignment or access checks [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug (find via LIST_WORKSPACES)\n- `repo_slug`: URL-friendly name for create\u002Fdelete\n- `q`: BBQL query filter (e.g., `name~\"api\"`, `project.key=\"PROJ\"`, `is_private=true`)\n- `role`: Filter repos by user role: `member`, `contributor`, `admin`, `owner`\n- `sort`: Sort field with optional `-` prefix for descending (e.g., `-updated_on`)\n- `is_private`: Boolean for repository visibility (defaults to `true`)\n- `project_key`: Bitbucket project key; omit to use workspace's oldest project\n\n**Pitfalls**:\n- `BITBUCKET_DELETE_REPOSITORY` is **irreversible** and does not affect forks\n- BBQL string values MUST be enclosed in double quotes: `name~\"my-repo\"` not `name~my-repo`\n- `repository` is NOT a valid BBQL field; use `name` instead\n- Default pagination is 10 results; set `pagelen` explicitly for complete listings\n- `CREATE_REPOSITORY` defaults to private; set `is_private: false` for public repos\n\n### 3. Manage Issues\n\n**When to use**: User wants to create, update, list, or comment on repository issues\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_ISSUES` - List issues with optional filters for state, priority, kind, assignee [Required]\n2. `BITBUCKET_CREATE_ISSUE` - Create a new issue with title, content, priority, and kind [Required]\n3. `BITBUCKET_UPDATE_ISSUE` - Modify issue attributes (state, priority, assignee, etc.) [Optional]\n4. `BITBUCKET_CREATE_ISSUE_COMMENT` - Add a markdown comment to an existing issue [Optional]\n5. `BITBUCKET_DELETE_ISSUE` - Permanently delete an issue [Optional]\n\n**Key parameters**:\n- `issue_id`: String identifier for the issue\n- `title`, `content`: Required for creation\n- `kind`: `bug`, `enhancement`, `proposal`, or `task`\n- `priority`: `trivial`, `minor`, `major`, `critical`, or `blocker`\n- `state`: `new`, `open`, `resolved`, `on hold`, `invalid`, `duplicate`, `wontfix`, `closed`\n- `assignee`: Bitbucket username for CREATE; `assignee_account_id` (UUID) for UPDATE\n- `due_on`: ISO 8601 format date string\n\n**Pitfalls**:\n- Issue tracker must be enabled on the repository (`has_issues: true`) or API calls will fail\n- `CREATE_ISSUE` uses `assignee` (username string), but `UPDATE_ISSUE` uses `assignee_account_id` (UUID) -- they are different fields\n- `DELETE_ISSUE` is permanent with no undo\n- `state` values include spaces: `\"on hold\"` not `\"on_hold\"`\n- Filtering by `assignee` in LIST_ISSUES uses account ID, not username; use `\"null\"` string for unassigned\n\n### 4. Manage Branches\n\n**When to use**: User wants to create branches or explore branch structure\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_BRANCHES` - List branches with optional BBQL filter and sorting [Required]\n2. `BITBUCKET_CREATE_BRANCH` - Create a new branch from a specific commit hash [Required]\n\n**Key parameters**:\n- `name`: Branch name without `refs\u002Fheads\u002F` prefix (e.g., `feature\u002Fnew-login`)\n- `target_hash`: Full SHA1 commit hash to branch from (must exist in repo)\n- `q`: BBQL filter (e.g., `name~\"feature\u002F\"`, `name=\"main\"`)\n- `sort`: Sort by `name` or `-target.date` (descending commit date)\n- `pagelen`: 1-100 results per page (default is 10)\n\n**Pitfalls**:\n- `CREATE_BRANCH` requires a full commit hash, NOT a branch name as `target_hash`\n- Do NOT include `refs\u002Fheads\u002F` prefix in branch names\n- Branch names must follow Bitbucket naming conventions (alphanumeric, `\u002F`, `.`, `_`, `-`)\n- BBQL string values need double quotes: `name~\"feature\u002F\"` not `name~feature\u002F`\n\n### 5. Review Pull Requests with Comments\n\n**When to use**: User wants to add review comments to pull requests, including inline code comments\n\n**Tool sequence**:\n1. `BITBUCKET_GET_PULL_REQUEST` - Get PR details and verify it exists [Prerequisite]\n2. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Review the actual code changes [Prerequisite]\n3. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get list of changed files [Optional]\n4. `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` - Post review comments [Required]\n\n**Key parameters**:\n- `pull_request_id`: String ID of the PR\n- `content_raw`: Markdown-formatted comment text\n- `content_markup`: Defaults to `markdown`; also supports `plaintext`\n- `inline`: Object with `path`, `from`, `to` for inline code comments\n- `parent_comment_id`: Integer ID for threaded replies to existing comments\n\n**Pitfalls**:\n- `pull_request_id` is a string in CREATE_PULL_REQUEST_COMMENT but an integer in GET_PULL_REQUEST\n- Inline comments require `inline.path` at minimum; `from`\u002F`to` are optional line numbers\n- `parent_comment_id` creates a threaded reply; omit for top-level comments\n- Line numbers in inline comments reference the diff, not the source file\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve human-readable names to IDs before operations:\n- **Workspace**: `BITBUCKET_LIST_WORKSPACES` to get workspace slugs\n- **Repository**: `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` with `q` filter to find repo slugs\n- **Branch**: `BITBUCKET_LIST_BRANCHES` to verify branch existence before PR creation\n- **Members**: `BITBUCKET_LIST_WORKSPACE_MEMBERS` to get UUIDs for reviewer assignment\n\n### Pagination\nBitbucket uses page-based pagination (not cursor-based):\n- Use `page` (starts at 1) and `pagelen` (items per page) parameters\n- Default page size is typically 10; set `pagelen` explicitly (max 50 for PRs, 100 for others)\n- Check response for `next` URL or total count to determine if more pages exist\n- Always iterate through all pages for complete results\n\n### BBQL Filtering\nBitbucket Query Language is available on list endpoints:\n- String values MUST use double quotes: `name~\"pattern\"`\n- Operators: `=` (exact), `~` (contains), `!=` (not equal), `>`, `>=`, `\u003C`, `\u003C=`\n- Combine with `AND` \u002F `OR`: `name~\"api\" AND is_private=true`\n\n## Known Pitfalls\n\n### ID Formats\n- Workspace: slug string (e.g., `my-workspace`) or UUID in braces (`{uuid}`)\n- Reviewer UUIDs must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- Issue IDs are strings; PR IDs are integers in some tools, strings in others\n- Commit hashes must be full SHA1 (40 characters)\n\n### Parameter Quirks\n- `assignee` vs `assignee_account_id`: CREATE_ISSUE uses username, UPDATE_ISSUE uses UUID\n- `state` values for issues include spaces: `\"on hold\"`, not `\"on_hold\"`\n- `destination_branch` omission defaults to repo main branch, not `main` literally\n- BBQL `repository` is not a valid field -- use `name`\n\n### Rate Limits\n- Bitbucket Cloud API has rate limits; large batch operations should include delays\n- Paginated requests count against rate limits; minimize unnecessary page fetches\n\n### Destructive Operations\n- `BITBUCKET_DELETE_REPOSITORY` is irreversible and does not remove forks\n- `BITBUCKET_DELETE_ISSUE` is permanent with no recovery option\n- Always confirm with the user before executing delete operations\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List workspaces | `BITBUCKET_LIST_WORKSPACES` | `q`, `sort` |\n| List repos | `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` | `workspace`, `q`, `role` |\n| Create repo | `BITBUCKET_CREATE_REPOSITORY` | `workspace`, `repo_slug`, `is_private` |\n| Delete repo | `BITBUCKET_DELETE_REPOSITORY` | `workspace`, `repo_slug` |\n| List branches | `BITBUCKET_LIST_BRANCHES` | `workspace`, `repo_slug`, `q` |\n| Create branch | `BITBUCKET_CREATE_BRANCH` | `workspace`, `repo_slug`, `name`, `target_hash` |\n| List PRs | `BITBUCKET_LIST_PULL_REQUESTS` | `workspace`, `repo_slug`, `state` |\n| Create PR | `BITBUCKET_CREATE_PULL_REQUEST` | `workspace`, `repo_slug`, `title`, `source_branch` |\n| Get PR details | `BITBUCKET_GET_PULL_REQUEST` | `workspace`, `repo_slug`, `pull_request_id` |\n| Get PR diff | `BITBUCKET_GET_PULL_REQUEST_DIFF` | `workspace`, `repo_slug`, `pull_request_id`, `max_chars` |\n| Get PR diffstat | `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` | `workspace`, `repo_slug`, `pull_request_id` |\n| Comment on PR | `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` | `workspace`, `repo_slug`, `pull_request_id`, `content_raw` |\n| List issues | `BITBUCKET_LIST_ISSUES` | `workspace`, `repo_slug`, `state`, `priority` |\n| Create issue | `BITBUCKET_CREATE_ISSUE` | `workspace`, `repo_slug`, `title`, `content` |\n| Update issue | `BITBUCKET_UPDATE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| Comment on issue | `BITBUCKET_CREATE_ISSUE_COMMENT` | `workspace`, `repo_slug`, `issue_id`, `content` |\n| Delete issue | `BITBUCKET_DELETE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| List members | `BITBUCKET_LIST_WORKSPACE_MEMBERS` | `workspace` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":49,"risk":50,"source":51,"date_added":52,"description":53},"bitbucket-automation","unknown","community","2026-02-27","Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.","main","8749e6a65f3d97164fb74ec18f758fc2d4fe1745","Video-Generation\u002Fseedance-20\u002Fskills\u002Fseedance-interview","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus","https:\u002F\u002Fgithub.com\u002Fendman100","2026-11-09 17:00:01",{"source":8,"skillName":49,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add endman100\u002Fskill-router-nexus --skill bitbucket-automation",{"tool":66,"command":67},"bunx","bunx skills add endman100\u002Fskill-router-nexus --skill bitbucket-automation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add endman100\u002Fskill-router-nexus --skill bitbucket-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FVideo-Generation\u002Fseedance-20\u002Fskills\u002Fseedance-interview\u002FSKILL.md",true,[],[75,96,133,155,164,188],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":85,"publishedAt":44},"01M6MPCT5BXVER8HQZTW3QE9AS","create-master","基于佛教经典文献，生成特定高僧大德的 AI 教学角色","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMetaphysics-and-Spirituality\u002FMaster-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FMetaphysics-and-Spirituality\u002FMaster-skill\u002FSKILL.md",[82],{"categoryNo":83,"categoryName":84,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000039","教师与教育",[86,87,88,89,33,90,91,92,93,94,95],"create master","master","create","生成","webfetch","edit","write","read","grep","Bash",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":114,"publishedAt":44},"01M6M43AKE95Y64E1JRXEF5QQ3","writing-dna-skill","从至少 20 篇完整文章中蒸馏可复用的写作 DNA，分析语言、文章结构、选题逻辑、素材策略、认知框架和视觉风格，并生成 Writing-DNA.md；按该 DNA 写作时会读取全部蒸馏产物和 5 篇相关原文。用于中英文作者、账号、品牌或出版物的风格分析与一致性写作。 Distill reusable Writing DNA from at least 20 complete articles for Chinese or English authors, publications, brands, and accounts; use for language, structure, topic logic, source strategy, cognitive-frame, and visual-style analysis.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fwriting-dna-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fwriting-dna-skill\u002FSKILL.md",[103,108,111],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000036","内容创作者",[115,116,117,118,119,120,121,122,123,124,125,126,127,89,128,129,130,30,131,132],"writing dna skill","DNA","writing","strategy","english","logic","visual","structure","chinese","reusable","use","style","distill","analysis","frame","source","at","complete",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":137,"sourceHtmlUrl":138,"categories":139,"keywords":142,"publishedAt":44},"01M6M428TTCGQ4ME3KY99VN037","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fstop-slop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fstop-slop\u002FSKILL.md",[140,141],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},[143,144,145,146,27,147,148,149,150,125,151,152,153,30,154,117],"slop","stop slop","stop","drafting","drafts","https","patterns","prose","remove","editing","text","content",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":44},"01M6M41X0B7EBX42TK435DMGGR","shuorenhua","检查和清理中英文文本里的 AI 套路，适用于“去 AI 味”“说人话”“自然一点”“别像模板”“先标问题”这类改写和审稿需求；按场景控制力度，同时保留事实、术语、语域和责任主体。","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fshuorenhua\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fshuorenhua\u002FSKILL.md",[],[157,163],"文本",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":168,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":44},"01M6M3ZD12WBEW5KXKDM4N6DFG","naming","Name products, SaaS, brands, open source projects, bots, and apps. Use when the user needs to name something, find a brand name, or pick a product name. Metaphor-driven process that produces memorable, meaningful names and avoids AI slop.","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fnaming-main\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fnaming-main\u002FSKILL.md",[],[166,172,173,174,175,176,125,177,93,130,178,179,180,181,95,182,183,184,185,27,186,187,143],"repo","websearch","product name","apps","bots","view","brand","pick","gh","projects","open","saas","open source","product","describe","ai slop",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":192,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":44},"01M6M3YVXAFAAWJ7F6JMPFREYE","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FWriting-and-Content\u002Fhumanizer-zh\u002FSKILL.md",[195],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},[197,198,199,93,92,91,117,89,163,200,143,145],"humanizer","zh","humanizer zh","翻译"]