CtrlK
BlogDocsLog inGet started
Tessl Logo

bitbucket-automation

Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.

74

1.33x
Quality

Does it follow best practices?

Impact

88%

1.33x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable MCP tool reference with clear sequenced workflows and excellent parameter/pitfall detail. Its main weaknesses are a redundant 'Known Pitfalls' section and the absence of explicit verify-before-proceed feedback loops for irreversible delete operations.

Suggestions

Remove or deduplicate the 'Known Pitfalls' section, keeping the most critical gotchas only where each workflow's Pitfalls block already covers them.

Add an explicit validate-then-proceed step for destructive operations, e.g. 'List the repo to confirm identity, get user confirmation, then call DELETE_REPOSITORY and verify it no longer appears in LIST_REPOSITORIES'.

Add a verify/retry feedback loop for batch listing operations that fetch multiple pages, so partial results are detected and re-fetched.

DimensionReasoningScore

Conciseness

The body is largely lean and teaches no background concepts, but the 'Known Pitfalls' section restates gotchas already covered in each workflow's Pitfalls block (e.g. BBQL double-quoting, assignee vs assignee_account_id, irreversible deletes), which is redundancy that could be tightened.

2 / 3

Actionability

It gives concrete tool slugs, typed parameters with valid values, and copy-ready examples (e.g. 'name~"api"', '{"uuid": "{...}"'}', 'max_chars' 50000), leaving little ambiguity about what to call and how.

3 / 3

Workflow Clarity

Workflows are cleanly sequenced with [Prerequisite]/[Required]/[Optional] tags and a setup validation checkpoint ('Confirm connection status shows ACTIVE'), but destructive operations (DELETE_REPOSITORY, DELETE_ISSUE) only say to confirm with the user and lack a verify-then-proceed feedback loop, capping this at 2.

2 / 3

Progressive Disclosure

As a single self-contained reference with no bundle files, it is well organized into Prerequisites, Setup, per-workflow sections, Common Patterns, and a Quick Reference navigation table, making discovery easy without nested references.

3 / 3

Total

10

/

12

Passed

Description

57%

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 clear and domain-specific but stops short of a top-tier description: it uses one generic verb over a list of nouns, omits common trigger-term variations, and lacks any explicit 'Use when' guidance. It is, however, highly distinct and unlikely to conflict with other skills.

Suggestions

Add distinct action verbs for each object, e.g. 'create and review pull requests, manage branches, triage issues, and administer workspaces'.

Include an explicit 'Use when...' clause with natural trigger phrasing, e.g. 'Use when the user asks to automate Bitbucket PRs, repos, branches, issues, or workspace admin'.

Add common shorthand variations users say, such as 'PRs', 'repos', and 'code review'.

DimensionReasoningScore

Specificity

It names the Bitbucket domain and several concrete objects ('repositories, pull requests, branches, issues, and workspace management'), but relies on a single verb ('Automate ... management') rather than listing multiple distinct concrete actions like create, review, or delete.

2 / 3

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.

2 / 3

Trigger Term Quality

Natural terms are present ('Bitbucket', 'pull requests', 'branches', 'issues', 'workspace') but common variations a user would actually say are missing, such as 'PRs', 'repos', 'code review', or 'commits'.

2 / 3

Distinctiveness Conflict Risk

The Bitbucket-specific scope tied to Rube MCP (Composio) carves a clear niche with distinct triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
davepoon/buildwithclaude
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.