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 strong in specificity and distinctiveness, clearly identifying Bitbucket as the target platform and listing concrete resource types it manages. However, it lacks an explicit 'Use when...' clause and misses common user-facing 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, or workspace management.'
Include common user-facing synonyms and abbreviations such as 'PR', 'repo', 'merge', 'code review', and 'git' to improve trigger term coverage.
| 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, which caps this at 2 per the rubric guidelines. | 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'. The term 'Rube MCP (Composio)' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to Bitbucket specifically and mentions the specific tooling (Rube MCP/Composio), making it highly distinguishable from generic git, GitHub, or GitLab skills. | 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 well-structured reference skill for Bitbucket automation that excels in workflow clarity with clearly sequenced steps and explicit warnings for destructive operations. Its main weaknesses are redundant content (pitfalls repeated in multiple places) and lack of concrete executable examples showing actual tool invocations with sample parameters. The content would benefit from deduplication and the addition of at least one complete worked example.
Suggestions
Add 1-2 concrete, complete tool call examples with filled-in parameters (e.g., a full BITBUCKET_CREATE_PULL_REQUEST call with workspace, repo_slug, title, source_branch values) to improve actionability.
Consolidate pitfalls into the single 'Known Pitfalls' section and remove duplicates from individual workflow sections, replacing them with a brief 'See Known Pitfalls' reference to reduce redundancy.
Consider extracting the detailed per-workflow parameter lists and the quick reference table into a separate REFERENCE.md file, keeping SKILL.md as a leaner overview with the most critical information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but has significant redundancy — pitfalls are repeated across individual workflow sections AND in the consolidated 'Known Pitfalls' section (e.g., BBQL double quotes, assignee vs assignee_account_id, delete irreversibility). The quick reference table also duplicates information already covered. Some trimming would improve token efficiency without losing clarity. | 2 / 3 |
Actionability | The skill provides specific tool names, parameter names, and clear sequences, which is good. However, it lacks concrete executable examples — no actual tool call invocations with sample parameters are shown. For instance, showing a complete RUBE_SEARCH_TOOLS call or a BITBUCKET_CREATE_PULL_REQUEST call with filled-in parameters would make it copy-paste ready. The guidance is specific but stops short of fully executable. | 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 ID resolution pattern serves as a validation checkpoint before operations. | 3 / 3 |
Progressive Disclosure | The content is a monolithic single file with no references to supporting files, which is understandable given no bundle exists. However, at ~200+ lines, the detailed parameter lists and pitfalls for each workflow could benefit from being split into separate reference files. The structure within the file is well-organized with clear headers, but the sheer volume of inline detail works against progressive disclosure principles. | 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
d065ead
- 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.