bitbucket-automation
Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.
74
65%
Does it follow best practices?
Impact
88%
1.33xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/bitbucket-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is reasonably specific about what it does (Bitbucket automation across repos, PRs, branches, issues, workspaces) and is distinctly scoped to Bitbucket via Composio. However, it lacks an explicit 'Use when...' clause and misses common user trigger terms like 'PR', 'repo', 'merge', or 'code review' that would improve discoverability.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Bitbucket repositories, pull requests, branches, issues, or workspace operations.'
Include common user-facing trigger term variations such as 'PR', 'repo', 'merge', 'code review', and 'Bitbucket Cloud' to improve matching.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: repositories, pull requests, branches, issues, and workspace management. Also specifies the tool (Rube MCP/Composio) and includes a concrete instruction to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate Bitbucket repos, PRs, branches, issues, workspace management), but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the domain mention. | 2 / 3 |
Trigger Term Quality | Includes good keywords like 'Bitbucket', 'repositories', 'pull requests', 'branches', 'issues', and 'workspace management', but misses common user variations like 'PR', 'repo', 'merge', 'code review', or 'git'. Also 'Rube MCP (Composio)' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Bitbucket specifically via Composio/Rube MCP, which creates a distinct niche. Unlikely to conflict with GitHub, GitLab, or other VCS skills due to the explicit Bitbucket mention. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive Bitbucket automation skill with excellent workflow clarity — clear sequences, labeled step importance, and thorough pitfall documentation. Its main weaknesses are verbosity from duplicated content (pitfalls appear both inline and consolidated) and lack of concrete executable examples showing actual tool invocations with sample parameters. The monolithic structure would benefit from splitting reference material into separate files.
Suggestions
Add 1-2 concrete tool invocation examples with actual sample parameters (e.g., a complete BITBUCKET_CREATE_PULL_REQUEST call with filled-in workspace, repo_slug, title, source_branch, and reviewers) to improve actionability.
Remove the duplicated 'Known Pitfalls' consolidated section since all pitfalls are already covered per-workflow, or conversely, remove per-workflow pitfalls and keep only the consolidated section to reduce token usage.
Extract the Quick Reference table and detailed parameter lists into a separate REFERENCE.md bundle file, keeping SKILL.md as a leaner overview with pointers to the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-organized but quite verbose at ~200+ lines. There's significant repetition — pitfalls are listed per-workflow AND again in a consolidated 'Known Pitfalls' section, and the quick reference table duplicates information already covered in each workflow. Some parameter descriptions repeat across sections. However, it avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear sequences, which is good. However, there are no executable code examples or concrete invocation snippets showing actual tool calls with sample parameters filled in. The guidance is specific but remains at the 'description' level rather than 'copy-paste ready' — e.g., no example of an actual RUBE_SEARCH_TOOLS call or a complete BITBUCKET_CREATE_PULL_REQUEST invocation with sample JSON. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps, labeled as [Prerequisite], [Required], or [Optional]. The setup section includes a verification flow (check connection → auth if needed → confirm ACTIVE). Destructive operations (delete repo, delete issue) are explicitly flagged with warnings and user confirmation guidance. The pitfalls sections serve as validation checkpoints by warning about common failure modes. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's monolithic — all content is in a single file with no references to supporting files. The repeated pitfalls (per-workflow and consolidated) and the lengthy parameter lists could be split into separate reference documents. For a skill this long (~200+ lines), some content should be offloaded to bundle files. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
74c7031
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.