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

View on GitHub
# Headless / CI authentication

Use `BKT_TOKEN` + `BKT_HOST` to run `bkt` in containers and CI pipelines without a prior `bkt auth login` or `bkt context create` step.

## Quick start

```bash
# Data Center — token-only bearer auth (default when no username is set)
export BKT_HOST=https://bitbucket.example.com
export BKT_TOKEN=my-personal-access-token
export BKT_PROJECT=MYPROJ   # optional default project
export BKT_REPO=my-service  # optional default repo
bkt pr list

# Bitbucket Cloud user API token — basic auth; username is required
export BKT_HOST=https://bitbucket.org
export BKT_TOKEN=my-api-token
export BKT_USERNAME=me@example.com
export BKT_WORKSPACE=my-workspace
export BKT_REPO=my-repo
bkt pr list

# Bitbucket Cloud repository/project/workspace access token — bearer auth
export BKT_TOKEN=my-resource-access-token
export BKT_AUTH_METHOD=bearer
unset BKT_USERNAME
bkt pr list
```

## Auth method rules

| Scenario | Resolved auth method |
|---|---|
| DC, no `BKT_USERNAME`, no `BKT_AUTH_METHOD` | `bearer` (default) |
| DC, `BKT_USERNAME` set, no `BKT_AUTH_METHOD` | `basic` |
| DC, `BKT_AUTH_METHOD=bearer` | `bearer` |
| DC, `BKT_AUTH_METHOD=basic` + no `BKT_USERNAME` | **error** — set `BKT_USERNAME` |
| Cloud, no `BKT_AUTH_METHOD` | `basic` (default); `BKT_USERNAME` is required |
| Cloud, `BKT_AUTH_METHOD=basic` | `BKT_USERNAME` is required |
| Cloud, `BKT_AUTH_METHOD=bearer` | bearer; `BKT_USERNAME` is not required |

## Environment variables

| Variable | Description |
|---|---|
| `BKT_TOKEN` | Authentication token. Bypasses keyring. |
| `BKT_HOST` | Bitbucket server URL. Required with `BKT_TOKEN` for config-free use. |
| `BKT_USERNAME` | Username for basic auth. Required for Cloud basic auth; optional for DC and Cloud bearer auth. |
| `BKT_AUTH_METHOD` | Auth method: `basic` or `bearer`. DC defaults to `bearer` when no username is set; Cloud defaults to `basic`. Use `bearer` for Cloud repository, project, or workspace access tokens. |
| `BKT_PROJECT` | Default Data Center project key. |
| `BKT_WORKSPACE` | Default Bitbucket Cloud workspace. |
| `BKT_REPO` | Default repository slug. |
| `BKT_CONFIG_DIR` | Config directory override. |
| `BKT_ALLOW_INSECURE_STORE` | Allow file-based credential storage. |
| `BKT_KEYRING_TIMEOUT` | Keyring operation timeout (e.g. `2m`). |
| `BKT_KEYRING_COLLECTION` | Secret Service collection name override (Linux). Set to the provider's default collection to reuse an already-unlocked wallet. |
| `BKT_OAUTH_CLIENT_ID` | Your own Bitbucket Cloud OAuth consumer key for `--web` login, instead of bkt's built-in consumer. Set together with `BKT_OAUTH_CLIENT_SECRET`. |
| `BKT_OAUTH_CLIENT_SECRET` | Secret of the consumer in `BKT_OAUTH_CLIENT_ID`. |

## Saved-host behaviour

When `BKT_HOST` matches a host already in `config.yml` in the bkt config directory, the saved entry is used as the base (preserving fields like `username` and `auth_method`). `BKT_TOKEN` always overrides the stored token. `BKT_USERNAME` and `BKT_AUTH_METHOD`, when set, override the saved values.

When `BKT_HOST` is set, `BKT_TOKEN` is used for that host only: the pair wins over an active context that points at another host, and `bkt` refuses to send the token to a different host named with `--context` or `--host`.

Cloud resource access tokens are not associated with a user. Commands that
require authenticated-user identity, such as cross-repository
`bkt pr list --mine`, still require user API-token or OAuth credentials.

## Bitbucket Pipelines example

```yaml
# bitbucket-pipelines.yml
pipelines:
  default:
    - step:
        script:
          - bkt pr list --mine
        variables:
          BKT_HOST: https://bitbucket.example.com
          BKT_TOKEN: $MY_PAT_SECRET
```
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