Skip to content

hashgraph-online/awesome-codex-plugins / plugins/avivsinai/bitbucket-cli/skills/bkt

Operate Bitbucket Cloud or Data Center repositories, pull requests, branches, pipelines, permissions, and webhooks with bkt. Use when a request names Bitbucket or bkt; confirm the platform before platform-specific commands.

FileKindSize
SKILL.mdskill md3.9 KB
rules/admin.mdmarkdown5.3 KB
rules/auth.mdmarkdown8.4 KB
rules/branch.mdmarkdown12.6 KB
rules/commit.mdmarkdown2.2 KB
rules/context.mdmarkdown5.0 KB
rules/extension.mdmarkdown5.3 KB
rules/guide.mdmarkdown5.8 KB
rules/headless.mdmarkdown3.7 KB
rules/mcp.mdmarkdown29.1 KB
rules/other.mdmarkdown1.2 KB
rules/perms.mdmarkdown10.6 KB
rules/pipeline.mdmarkdown7.7 KB
rules/pr.mdmarkdown47.9 KB
rules/project.mdmarkdown4.2 KB
rules/repo.mdmarkdown14.0 KB
rules/skill.mdmarkdown17.1 KB
rules/status.mdmarkdown5.9 KB
rules/variable.mdmarkdown7.6 KB
rules/webhook.mdmarkdown6.7 KB

rules/extension.md

View on GitHub
<!-- auto-generated by cmd/docgen — do not edit -->

# bkt extension

Install, list, remove, and execute external bkt CLI extensions.

Extensions are Git repositories that contain an executable following the
bkt-<name> naming convention. Once installed, an extension can be invoked
directly through "bkt extension exec" or discovered with "bkt extension list".
Extensions work identically for both Bitbucket Cloud and Data Center contexts.

```
bkt extension <command> [flags]
```

### Examples

```bash
# Install an extension from a Git repository
  bkt extension install https://bitbucket.org/myteam/bkt-lint

  # List all installed extensions
  bkt extension list

  # Run an installed extension with arguments
  bkt extension exec lint --fix
```

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [exec](#bkt-extension-exec) | Execute an installed extension | — |
| [install](#bkt-extension-install) | Install an extension from a repository | — |
| [list](#bkt-extension-list) | List installed extensions | — |
| [remove](#bkt-extension-remove) | Remove an installed extension | — |

## bkt extension exec

Run an installed extension by name, forwarding any additional arguments to the
extension executable. The extension runs in its own directory with
BKT_EXTENSION_DIR and BKT_EXTENSION_NAME environment variables set.
Sensitive bkt configuration variables (tokens, keyring passphrase) are
stripped from the environment before the extension process starts.

### Usage

```
bkt extension exec <name> [args...] [flags]
```

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# Run an extension with no arguments
  bkt extension exec lint

  # Pass arguments to the extension
  bkt extension exec lint --fix --verbose

  # Run an extension that accepts a file path
  bkt extension exec formatter src/main.go
```

## bkt extension install

Clone a Git repository into the bkt extensions directory and register it as
a CLI extension. The repository must contain an executable named bkt-<name>
at the top level or inside a bin/ subdirectory. The extension name is inferred
from the repository URL by stripping the optional "bkt-" prefix.

If the extension is already installed, the command returns an error. Remove it
first with "bkt extension remove" before reinstalling.

### Usage

```
bkt extension install <repository> [flags]
```

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# Install from a full HTTPS URL
  bkt extension install https://bitbucket.org/myteam/bkt-lint

  # Install from an SSH URL
  bkt extension install git@bitbucket.org:myteam/bkt-deploy.git

  # Install from a GitHub repository
  bkt extension install https://github.com/user/bkt-formatter
```

## bkt extension list

Display all extensions currently installed in the bkt extensions directory.
Each entry shows the extension name and, when available, the relative path
to its executable. If no extensions are installed, a hint is printed
suggesting the install command.

**Alias:** `ls`

### Usage

```
bkt extension list [flags]
```

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# List all installed extensions
  bkt extension list

  # List using the short alias
  bkt extension ls

  # List in JSON format
  bkt extension list --json
```

## bkt extension remove

Remove a previously installed extension by deleting its directory from the
bkt extensions folder. The name argument is the extension name (not the full
repository URL). Use "bkt extension list" to see installed extension names.

**Alias:** `rm`

### Usage

```
bkt extension remove <name> [flags]
```

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# Remove an extension by name
  bkt extension remove lint

  # Remove using the short alias
  bkt extension rm deploy
```

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall