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 ./.trae/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 highly distinctive due to the Bitbucket focus. However, it lacks an explicit 'Use when...' clause and misses common user trigger terms like 'PR', 'repo', 'merge', or 'code review', which limits its effectiveness for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Bitbucket repositories, pull requests, branches, issues, or workspace management.'
Include common user-facing trigger term variations such as 'PR', 'repo', 'merge', 'code review', and 'git' to improve matching against natural user language.
| 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'. Also 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Bitbucket' specifically and 'Rube MCP (Composio)' makes this highly distinctive. It would not easily conflict with GitHub, GitLab, or other VCS skills due to the explicit Bitbucket scoping. | 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 and thorough Bitbucket automation skill with excellent workflow clarity and valuable pitfall documentation. Its main weaknesses are verbosity through repetition (pitfalls duplicated across sections), lack of concrete executable examples showing actual tool invocations with sample data, and all content being packed into a single large file rather than using progressive disclosure to separate reference material.
Suggestions
Add at least one concrete, complete tool call example per workflow showing actual parameter values (e.g., a full BITBUCKET_CREATE_PULL_REQUEST call with sample workspace, repo_slug, title, source_branch, and reviewers filled in).
Consolidate pitfalls into the single 'Known Pitfalls' section and remove per-workflow pitfall lists to eliminate repetition (or vice versa — keep per-workflow and remove the consolidated section).
Extract the Quick Reference table and detailed parameter/pitfall documentation into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with workflow sequences and links to details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but quite verbose at ~250 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. The BBQL double-quote requirement is mentioned at least 3 times. However, most content is genuinely useful rather than explaining things Claude already knows. | 2 / 3 |
Actionability | The skill provides clear tool names, parameter lists, and step sequences, which is good. However, there are no concrete executable examples showing actual tool calls with sample parameters filled in. Everything is described abstractly (e.g., 'Call BITBUCKET_CREATE_PULL_REQUEST with title, source branch') rather than showing a concrete invocation with example values. The pitfalls sections are highly actionable with specific format requirements. | 2 / 3 |
Workflow Clarity | Workflows are clearly sequenced with numbered steps, labeled as [Required], [Optional], or [Prerequisite]. The setup section includes a verification flow. Destructive operations (delete repo, delete issue) are explicitly flagged with warnings and the instruction to confirm with the user. The ID resolution pattern provides a clear prerequisite chain before operations. | 3 / 3 |
Progressive Disclosure | The content is essentially monolithic — everything is in one large file with no references to separate detailed documents. For a skill this long (~250 lines), the detailed parameter lists and pitfalls for each workflow could be split into separate reference files. The structure within the file is good (clear sections, table of contents via headers), but the sheer volume in a single file hurts discoverability. | 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
- Lingjie-chen/MT5
- Commit
3069d33
- 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.