hashgraph-online/awesome-codex-plugins / plugins/avivsinai/bitbucket-cli/skills/bkt
bkt
VerifiedOperate 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
| rules/admin.md | markdown | 5.3 KB |
| rules/auth.md | markdown | 8.4 KB |
| rules/branch.md | markdown | 12.6 KB |
| rules/commit.md | markdown | 2.2 KB |
| rules/context.md | markdown | 5.0 KB |
| rules/extension.md | markdown | 5.3 KB |
| rules/guide.md | markdown | 5.8 KB |
| rules/headless.md | markdown | 3.7 KB |
| rules/mcp.md | markdown | 29.1 KB |
| rules/other.md | markdown | 1.2 KB |
| rules/perms.md | markdown | 10.6 KB |
| rules/pipeline.md | markdown | 7.7 KB |
| rules/pr.md | markdown | 47.9 KB |
| rules/project.md | markdown | 4.2 KB |
| rules/repo.md | markdown | 14.0 KB |
| rules/skill.md | markdown | 17.1 KB |
| rules/status.md | markdown | 5.9 KB |
| rules/variable.md | markdown | 7.6 KB |
| rules/webhook.md | markdown | 6.7 KB |
rules/admin.md
View on GitHub<!-- auto-generated by cmd/docgen — do not edit -->
# bkt admin
Perform administrative operations on a Bitbucket Data Center instance.
This command group provides access to server-level management tasks such as
secrets rotation and logging configuration. All subcommands require a Data
Center context; they are not available for Bitbucket Cloud.
```
bkt admin <command> [flags]
```
### Examples
```bash
# Rotate encryption keys on the configured DC instance
bkt admin secrets rotate
# Show the current logging configuration
bkt admin logging get
# Set the logging level to DEBUG
bkt admin logging set --level DEBUG
```
## Subcommands
| Subcommand | Description | Key Flags |
|---|---|---|
| [logging](#bkt-admin-logging) | Inspect or update logging settings *(DC)* | — |
| [secrets](#bkt-admin-secrets) | Manage secrets manager operations *(DC)* | — |
## bkt admin logging
Inspect or update the logging configuration of a Bitbucket Data Center
instance. You can view the current log level and async setting, or change
them at runtime without restarting the server. This command group is only
available for Data Center contexts.
```
bkt admin logging <command> [flags]
```
### Examples
```bash
# Show the current logging configuration
bkt admin logging get
# Set the log level to WARN
bkt admin logging set --level WARN
# Enable async logging at DEBUG level
bkt admin logging set --level DEBUG --async
```
| Subcommand | Description |
|---|---|
| get | Show current logging configuration (DC only) |
| set | Update logging configuration (DC only) |
## bkt admin logging get
Display the current logging configuration of a Bitbucket Data Center
instance, including the active log level and whether asynchronous logging
is enabled. Output defaults to human-readable text but supports JSON via
the --json flag. Requires a Data Center context.
### Usage
```
bkt admin logging get [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 logging config in human-readable format
bkt admin logging get
# Show logging config as JSON
bkt admin logging get --json
# Query a specific DC context
bkt admin logging get --context prod-dc
```
## bkt admin logging set
Update the logging configuration of a Bitbucket Data Center instance at
runtime. You can change the log level (TRACE, DEBUG, INFO, WARN, ERROR)
and toggle asynchronous logging without restarting the server. This
command requires a Data Center context and will fail against Cloud
instances.
### Usage
```
bkt admin logging set [flags]
```
### Flags
| Flag | Short | Description |
|---|---|---|
| `--async` | | Enable asynchronous logging |
| `--level` | | Logging level: TRACE, DEBUG, INFO, WARN, ERROR |
### 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 the log level to INFO
bkt admin logging set --level INFO
# Enable async logging
bkt admin logging set --async
# Set DEBUG level with async on a named context
bkt admin logging set --level DEBUG --async --context staging-dc
```
## bkt admin secrets
Manage encryption keys and secrets through the Bitbucket Data Center
Secrets Manager plugin. Use the subcommands to rotate keys and perform
other secrets-related maintenance tasks on your DC instance.
```
bkt admin secrets <command> [flags]
```
### Examples
```bash
# Rotate the encryption keys
bkt admin secrets rotate
# Rotate keys using a specific DC context
bkt admin secrets rotate --context my-dc
```
| Subcommand | Description |
|---|---|
| rotate | Rotate encryption keys via the Secrets Manager plugin (DC only) |
## bkt admin secrets rotate
Trigger an encryption key rotation on a Bitbucket Data Center instance
through the Secrets Manager plugin. This is a server-side operation that
generates a new encryption key and re-encrypts stored secrets. The command
requires a Data Center context and will fail against Cloud instances.
### Usage
```
bkt admin secrets rotate [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
# Rotate encryption keys on the default DC context
bkt admin secrets rotate
# Rotate keys on a named DC context
bkt admin secrets rotate --context prod-dc
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| 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: 197k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |