Name: bitbucket
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bitbucket

Bitbucket integration. Manage Repositories, Users, Teams. Use when the user wants to interact with Bitbucket data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bitbucket/SKILL.md

Quality

Content

68%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 highly actionable with copy-paste CLI commands and a useful actions table, but it opens with unnecessary background on Bitbucket, leaves a dangling "Step 2" reference, and lacks verification steps around the Create/Update actions it exposes.

Suggestions

Remove or trim the introductory paragraph explaining what Bitbucket is; Claude already knows this and it costs tokens.

Label the workflow steps explicitly (Step 1 install/auth, Step 2 connect, Step 3 search/run) so the dangling "skip to Step 2" reference resolves.

Add a verification checkpoint before/after Create/Update actions (e.g., confirm parameters and inspect the returned object) so destructive operations include a feedback loop.

Dimension	Reasoning	Score
Conciseness	The operational CLI content is mostly efficient, but the opening paragraph explaining what Bitbucket is ("Bitbucket is a web-based version control repository management service...") restates a concept Claude already knows and "Use action names and parameters as needed" is filler, placing it at mostly-efficient with some unnecessary explanation.	3 / 5
Actionability	Provides copy-paste ready commands for every common case (install, login, connection ensure/get, action list/run, request) with real flags, plus a concrete popular-actions table mapping names to keys and descriptions — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The connection setup has real validation checkpoints (state polling, CLIENT_ACTION_REQUIRED handling), but "Step 2" is referenced without being labeled, and the action-running workflow for Create/Update operations has no verification step — the destructive/batch-operations cap at 3 applies.	3 / 5
Progressive Disclosure	A single self-contained file with clear, well-ordered section headers and no nested references; structure is good, though the large popular-actions table is reference-like content kept inline rather than split out.	4 / 5
	Total	15 / 20 Passed

Description

62%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 answers both what and when with an explicit trigger clause and a clear product niche, but relies on the generic verb "Manage" and omits high-frequency natural terms like pull requests, commits, and branches.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List, create, and update repositories, pull requests, issues, branches, and commits."

Expand trigger keywords to include the natural phrases users say, e.g. "Use when the user mentions Bitbucket repos, pull requests, commits, branches, or workspaces."

Tighten the "when" clause from "interact with Bitbucket data" to concrete triggers to lift completeness toward 5.

Dimension	Reasoning	Score
Specificity	Names the Bitbucket domain plus entities ("Manage Repositories, Users, Teams") but the single verb "Manage" is generic rather than multiple concrete actions, fitting the anchor for domain + 1-2 actions rather than several specific ones.	3 / 5
Completeness	Both "what" ("Manage Repositories, Users, Teams") and an explicit "when" ("Use when the user wants to interact with Bitbucket data") are present; the trigger clause is explicit but generic rather than listing concrete trigger phrases, so it sits at 4 not 5.	4 / 5
Trigger Term Quality	"Bitbucket" plus Repositories/Users/Teams gives some relevant keywords, but it omits common natural terms users say (pull requests, commits, branches, Git), so coverage is partial rather than good.	3 / 5
Distinctiveness Conflict Risk	The "Bitbucket integration" niche and Bitbucket-specific trigger are clearly distinct from unrelated skills, with only minor overlap risk against closely related Git/VCS skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/bitbucket/SKILL.md
Commit: f484c82

Reviewed: 8 minutes ago

Table of Contents

Discovery Implementation Validation

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.