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/variable.md

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

# bkt variable

Create and manage pipeline variables in Bitbucket Cloud repositories.

Pipeline variables are available during pipeline execution. Variables can be
defined at three scopes:
  - Repository: Available to all pipelines in the repository
  - Workspace: Available to all pipelines in the workspace
  - Deployment: Available only during deployment to a specific environment

Note: Pipeline variables are only available for Bitbucket Cloud.

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

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [delete](#bkt-variable-delete) | Delete a pipeline variable *(Cloud)* | `--deployment`, `--repo`, `--scope`, `--workspace` |
| [get](#bkt-variable-get) | Get a pipeline variable *(Cloud)* | `--deployment`, `--repo`, `--scope`, `--workspace` |
| [list](#bkt-variable-list) | List pipeline variables *(Cloud)* | `--deployment`, `--limit`, `--repo`, `--scope` |
| [set](#bkt-variable-set) | Create or update a pipeline variable *(Cloud)* | `--body`, `--deployment`, `--env-file`, `--repo` |

## bkt variable delete

Delete a pipeline variable by name from a Bitbucket Cloud repository,
workspace, or deployment environment. By default, the command prompts for
confirmation before deleting. Use --yes to skip the prompt in scripts or
CI pipelines.

This command is only available for Bitbucket Cloud contexts.

**Alias:** `rm`

### Usage

```
bkt variable delete <variable-name> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--deployment` | `-e` | Deployment environment name (implies --scope deployment) |
| `--repo` | `-R` | Repository slug |
| `--scope` |  | Variable scope: repository, workspace, or deployment |
| `--workspace` |  | Bitbucket workspace |
| `--yes` | `-y` | Skip confirmation prompt |

### 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
# Delete a repository variable (will prompt for confirmation)
  bkt variable delete MY_VAR

  # Delete a workspace variable
  bkt variable delete MY_VAR --scope workspace

  # Delete a deployment environment variable
  bkt variable delete MY_VAR --deployment production

  # Delete without confirmation
  bkt variable delete MY_VAR --yes
```

## bkt variable get

Retrieve a single pipeline variable by name from a Bitbucket Cloud repository,
workspace, or deployment environment. The variable key is matched exactly
(case-sensitive). Secured variables are flagged in the output and their values
cannot be retrieved from the API.

This command is only available for Bitbucket Cloud contexts.

### Usage

```
bkt variable get <variable-name> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--deployment` | `-e` | Deployment environment name (implies --scope deployment) |
| `--repo` | `-R` | Repository slug |
| `--scope` |  | Variable scope: repository, workspace, or deployment |
| `--workspace` |  | Bitbucket workspace |

### 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
# Get a repository variable by name
  bkt variable get MY_VAR

  # Get a workspace variable
  bkt variable get MY_VAR --scope workspace

  # Get a deployment environment variable
  bkt variable get MY_VAR --deployment production

  # Get a variable in JSON format
  bkt variable get MY_VAR --json
```

## bkt variable list

List pipeline variables for a Bitbucket Cloud repository, workspace, or
deployment environment. By default, repository-scoped variables are shown.
Use --scope to switch to workspace variables, or --deployment to list
variables tied to a specific deployment environment.

Secured variable values are masked in the output. This command is only
available for Bitbucket Cloud contexts.

**Alias:** `ls`

### Usage

```
bkt variable list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--deployment` | `-e` | Deployment environment name (implies --scope deployment) |
| `--limit` | `-L` | Maximum variables to display |
| `--repo` | `-R` | Repository slug |
| `--scope` |  | Variable scope: repository, workspace, or deployment |
| `--workspace` |  | Bitbucket workspace |

### 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 repository variables (default)
  bkt variable list

  # List workspace variables
  bkt variable list --scope workspace

  # List deployment environment variables
  bkt variable list --deployment production

  # List variables in JSON format
  bkt variable list --json

  # List variables for a specific repository
  bkt variable list --repo my-repo
```

## bkt variable set

Create or update a pipeline variable.

If the variable already exists, it will be updated. Otherwise, a new variable
will be created.

The value can be provided via:
  - The --body flag
  - Standard input (if --body is not specified)
  - Interactive prompt (if running in a TTY)

You can also import multiple variables at once from an env file using the
--env-file flag. The file should contain KEY=VALUE pairs, one per line.
Lines starting with # are treated as comments.

### Usage

```
bkt variable set [<variable-name>] [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--body` | `-b` | Variable value |
| `--deployment` | `-e` | Deployment environment name (implies --scope deployment) |
| `--env-file` | `-f` | Path to env file containing KEY=VALUE pairs |
| `--repo` | `-R` | Repository slug |
| `--scope` |  | Variable scope: repository, workspace, or deployment |
| `--secured` | `-s` | Mark variable as secured (secret) |
| `--workspace` |  | Bitbucket workspace |

### 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
# Set a repository variable with a value
  bkt variable set MY_VAR --body "my-value"

  # Set a workspace variable
  bkt variable set MY_VAR --body "my-value" --scope workspace

  # Set a deployment environment variable
  bkt variable set MY_VAR --body "my-value" --deployment production

  # Set a secured/secret variable
  bkt variable set MY_SECRET --body "secret-value" --secured

  # Set a variable from stdin
  echo "my-value" | bkt variable set MY_VAR

  # Import variables from an env file
  bkt variable set --env-file .env
```

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated 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: 196kUpdated 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: 118kUpdated 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