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

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

# bkt auth

Manage authentication credentials for Bitbucket Data Center and Cloud hosts.

Tokens are stored in the OS keychain by default. For Data Center hosts, bkt
uses Personal Access Tokens (PATs). For Bitbucket Cloud, bkt uses browser
OAuth (--web) or Atlassian API tokens with scopes.

Use "bkt auth login" to add a host, "bkt auth status" to inspect stored
credentials, and "bkt auth logout" to remove them.

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

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [doctor](#bkt-auth-doctor) | Diagnose authentication and keychain issues | — |
| [login](#bkt-auth-login) | Authenticate against a Bitbucket Data Center or Cloud host | `--alias`, `--allow-http`, `--allow-insecure-store`, `--auth-method` |
| [logout](#bkt-auth-logout) | Remove stored credentials for a host | `--host` |
| [status](#bkt-auth-status) | Show authentication status for configured hosts | — |

## bkt auth doctor

Inspect the keychain/secret store wiring and explain why prompts or
timeouts may be happening.

On macOS this reports the current bkt binary's code signature, Designated
Requirement, and whether a stored token item is present for the host. If the
stored item was created by a bkt binary with a different Designated
Requirement — which is common after `brew upgrade bitbucket-cli` — macOS will
keep prompting for the Keychain password on every read. The fix in that case
is to re-run `bkt auth login` so the item is recreated with the
current binary's DR.

The command never reads the stored secret itself.

### Usage

```
bkt auth doctor [host] [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
# Inspect the default host
  bkt auth doctor

  # Inspect a specific host
  bkt auth doctor bitbucket.example.com
```

## bkt auth login

Authenticate against a Bitbucket Data Center or Cloud host and store
credentials in the OS keychain.

For Data Center (--kind dc, the default), you authenticate with a Personal
Access Token (PAT). The token needs Repository Read/Write and Project Read
permissions. Use --web-token to open the PAT management page in your browser.

For Bitbucket Cloud (--kind cloud), the simplest method is --web, which
logs in through Bitbucket in your browser with OAuth. The CLI receives a
short-lived access token that it refreshes automatically. To use your own
OAuth consumer instead of bkt's, set BKT_OAUTH_CLIENT_ID and
BKT_OAUTH_CLIENT_SECRET. Alternatively, --web-token opens the Atlassian API
token page and prompts for a scoped API token locally.

Credentials are verified against the remote host before being stored. If no
OS keychain is available, pass --allow-insecure-store to use encrypted file
fallback. In non-interactive environments, provide --username and pipe the
token on stdin with --with-token (--token also works, but the process list
shows it).

Credentials are stored per host, keyed by the server's host name. To use
several accounts on one server, for example two Bitbucket Cloud accounts,
log in again with --alias: the second account gets a host entry and keychain
item of its own under that name, and a context selects it with
`bkt context create <name> --host <alias>`.
Alias names share the OS keychain namespace across config directories;
use distinct aliases even when BKT_CONFIG_DIR differs.

### Usage

```
bkt auth login [host] [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--alias` |  | Store the credentials under this host name instead of the server's, to log in to one server with several accounts |
| `--allow-http` |  | Allow http:// URLs for login even though credentials will be sent in plaintext |
| `--allow-insecure-store` |  | Allow encrypted fallback secret storage when no OS keychain is available |
| `--auth-method` |  | Authentication method: bearer (token-only; Data Center default) or basic (username+token; Cloud default) |
| `--kind` |  | Bitbucket deployment kind (dc or cloud) |
| `--token` |  | Authentication token (DC: PAT, Cloud: API token). WARNING: visible in process list and shell history; prefer the interactive prompt |
| `--username` |  | Username (DC: PAT owner, Cloud: Atlassian email for API tokens) |
| `--web` | `-w` | Authenticate via OAuth in the browser (Cloud only) |
| `--web-token` |  | Open browser to create an API token, then prompt for credentials |
| `--with-token` |  | Read the token from standard input |

### 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
# Login to Bitbucket Cloud via OAuth
  bkt auth login https://bitbucket.org --kind cloud --web

  # Login to Bitbucket Cloud with an API token
  bkt auth login https://bitbucket.org --kind cloud --web-token

  # Interactive login to a Data Center instance
  bkt auth login https://bitbucket.example.com

  # Open browser to create a PAT, then prompt for credentials
  bkt auth login https://bitbucket.example.com --web-token

  # Non-interactive login with flags (CI pipelines)
  bkt auth login https://bitbucket.example.com --username admin --with-token < pat.txt

  # A second Bitbucket Cloud account, used by its own context
  bkt auth login https://bitbucket.org --kind cloud --web --alias team-b
  bkt context create team-b --host team-b --workspace team-b-workspace
```

## bkt auth logout

Remove stored credentials for a Bitbucket host and delete the host entry
from the configuration file.

The host can be specified as a positional argument or with the --host flag,
using either the host key (e.g. "bitbucket.example.com") or the full base
URL. Any contexts associated with the removed host are also deleted.

This command does not work when the BKT_TOKEN environment variable is set,
because the token is externally managed in that case.

### Usage

```
bkt auth logout [host] [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--host` |  | Host key or base URL to remove |

### 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 credentials by host key
  bkt auth logout bitbucket.example.com

  # Remove credentials by base URL
  bkt auth logout https://bitbucket.example.com

  # Remove Bitbucket Cloud credentials
  bkt auth logout api.bitbucket.org
```

## bkt auth status

Display the authentication status for all configured Bitbucket hosts and
contexts.

For each host, the output includes the base URL, deployment kind (dc or
cloud), the stored username, and the token source (OS keychain or the
BKT_TOKEN environment variable). Configured contexts are listed with their
associated host, project/workspace, and default repository.

Use --json to get machine-readable output suitable for scripting.

### Usage

```
bkt auth status [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
# Show all configured hosts and contexts
  bkt auth status

  # Get status as JSON
  bkt auth status --json
```
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated 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