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

65%

Does it follow best practices?

Impact

88%

1.33x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/bitbucket-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

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

The body is a well-structured, actionable reference for Bitbucket automation with concrete tool sequences and parameter formats. Its main weaknesses are duplicated pitfalls across sections and the absence of validation feedback loops for destructive operations.

Suggestions

Remove or deduplicate the 'Known Pitfalls' section so each pitfall appears once (in its workflow) to reduce token redundancy.

Add explicit validation/feedback steps for destructive operations, e.g., list forks and confirm scope before DELETE_REPOSITORY, and define error-recovery behavior when a delete fails.

Consider moving the Quick Reference table and exhaustive parameter detail into a reference file to tighten SKILL.md.

DimensionReasoningScore

Conciseness

Content is reference-style with Bitbucket/Composio-specific details Claude doesn't already know, but the standalone 'Known Pitfalls' section and Quick Reference table substantially duplicate the per-workflow 'Pitfalls' and parameter lists, adding padding that could be tightened.

3 / 5

Actionability

Concrete tool slugs, exact parameter names, and format examples (e.g., '[{"uuid": "{...}"}]', 'name~"api"') provide mostly executable guidance; it lacks a full end-to-end example call with all arguments filled.

4 / 5

Workflow Clarity

Numbered tool sequences with [Prerequisite]/[Required]/[Optional] tags and a connection-ACTIVE checkpoint give clear sequencing, but destructive operations (DELETE_REPOSITORY, DELETE_ISSUE) lack a validate->fix->retry feedback loop beyond 'confirm with user', capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Self-contained body (no bundle files) is well-sectioned across Prerequisites, Setup, Core Workflows, Common Patterns, Known Pitfalls, and Quick Reference; minor organization gaps exist since the reference table and detailed pitfalls could live in a separate file.

4 / 5

Total

14

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 specific and well-scoped to a clear Bitbucket-automation niche, with concrete capability terms and third-person voice. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit usage trigger, e.g., 'Use when the user wants to automate Bitbucket repos, PRs, branches, issues, or workspace management.'

Include common synonyms like 'PRs' alongside 'pull requests' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ('repositories, pull requests, branches, issues, and workspace management') plus the mechanism (Rube MCP/Composio) and an operational directive, but stops short of comprehensive per-action coverage.

4 / 5

Completeness

The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the trailing 'Always search tools first' is operational instruction rather than a usage trigger, capping completeness at 3.

3 / 5

Trigger Term Quality

Natural user-facing terms like 'Bitbucket repositories, pull requests, branches, issues' are present, but common synonyms/variants (e.g., 'PRs') are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped specifically to Bitbucket via Rube MCP (Composio), giving it a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

20

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.