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.

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/bitbucket-automation/SKILL.md

The canonical home for this skill is bitbucket-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 skill body is well-organized and packed with concrete, actionable tool guidance, but it suffers from duplicated pitfalls, a filler closing line, and no progressive disclosure to reference files. Destructive workflows also lack inline validation checkpoints.

Suggestions

Move the consolidated "Known Pitfalls" and detailed parameter reference into a references/ file (e.g. PITFALLS.md, REFERENCE.md) and link from the body to reduce duplication and enable progressive disclosure.

Add an explicit "Confirm with the user before running" checkpoint inline in the delete-repository and delete-issue tool sequences.

Remove or replace the empty "When to Use" section with concrete trigger guidance.

DimensionReasoningScore

Conciseness

The body is mostly dense and operational, but pitfalls are duplicated between each workflow's "Pitfalls" subsection and the consolidated "Known Pitfalls" section, and the closing "When to Use" line ("applicable to execute the workflow or actions described in the overview") is filler that could be trimmed.

3 / 5

Actionability

Concrete tool slugs, exact parameter values (e.g. state OPEN/MERGED/DECLINED, kind bug/enhancement/...), and a Quick Reference table give mostly executable guidance, though no fully-assembled example tool calls are shown.

4 / 5

Workflow Clarity

Numbered tool sequences with [Prerequisite]/[Required]/[Optional] tags and an ACTIVE-connection check are clear, but destructive operations (DELETE_REPOSITORY, DELETE_ISSUE) lack an inline validation/confirm checkpoint in their sequences, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Content is well-sectioned with headers and a Quick Reference table, but it is a single ~220-line monolith with no external reference files, and detailed parameter/pitfall material that could be split out is inlined.

3 / 5

Total

13

/

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 clearly conveys what the skill does and names a distinct, specific niche, but it lacks an explicit "Use when..." trigger clause, which caps its completeness. Trigger terms are strong but could add common synonyms.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to automate Bitbucket repos, PRs, branches, issues, or workspace admin."

Include natural synonyms such as "PRs" and "merge requests" alongside "pull requests".

Swap generic verbs ("Automate", "management") for discrete operations (create, review, merge, delete) to raise specificity.

DimensionReasoningScore

Specificity

Lists several concrete Bitbucket objects ("repositories, pull requests, branches, issues, and workspace management") but the verbs are generic ("Automate", "management") rather than discrete operations, leaving minor coverage gaps versus the comprehensive anchor.

4 / 5

Completeness

The "what" is clear ("Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP"), but there is no "Use when..." clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Strong natural keywords ("Bitbucket", "pull requests", "branches", "issues", "workspace") that users would say, but misses common synonyms such as "PRs"; "Rube MCP (Composio)" is technical jargon users rarely voice.

4 / 5

Distinctiveness Conflict Risk

"Bitbucket" scoped to "Rube MCP (Composio)" is a clear niche with distinct triggers and minimal conflict risk against 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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.