Bkt
Run Bitbucket Data Center admin tasks—secrets rotation and runtime logging—from the bkt CLI without clicking through the server UI.
Overview
Bkt is an agent skill for the Operate phase that documents bkt admin CLI operations for Bitbucket Data Center secrets rotation and logging configuration.
Install
npx skills add https://github.com/avivsinai/bitbucket-cli --skill bktWhat is this skill?
- Documents bkt admin for Bitbucket Data Center only—not Bitbucket Cloud
- Secrets subcommand group for encryption key rotation via secrets manager
- Logging get/set for runtime log level and async logging without server restart
- Example invocations: bkt admin secrets rotate and bkt admin logging set --level DEBUG --async
- Structured subcommand tables for logging and secrets with DC context requirement
- Admin command group with logging and secrets subcommands documented for Data Center
Adoption & trust: 857 installs on skills.sh; 137 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You manage Bitbucket Data Center but forget which bkt admin subcommands rotate secrets or change log level without a restart.
Who is it for?
Self-hosted Bitbucket DC admins who already use bkt and need fast, accurate admin subcommand references during ops or incident response.
Skip if: Bitbucket Cloud workspaces, developers who only create PRs from git, or teams without Data Center admin access.
When should I use this skill?
Performing Bitbucket Data Center administrative operations via bkt admin logging or secrets.
What do I get? / Deliverables
You can run documented bkt admin logging and secrets commands from the agent with DC context and flags spelled out correctly.
- Correct bkt admin command invocation for the requested DC task
- Interpretation of logging get output or confirmation of set/rotate actions to run
Recommended Skills
Journey fit
Admin secrets and logging on a self-hosted Bitbucket instance is production operations work, so the canonical shelf is Operate → infra. Subcommands target server-level configuration (encryption key rotation, log level/async), not day-to-day PR review or feature coding.
How it compares
CLI command reference for Bitbucket DC server admin—not a PR reviewer skill or a CI pipeline generator.
Common Questions / FAQ
Who is bkt for?
Solo operators and small teams with Bitbucket Data Center admin responsibility who want the bkt CLI admin surface explained for agent-assisted execution.
When should I use bkt?
In Operate → infra when rotating encryption keys, inspecting logging config, or setting WARN/DEBUG levels and async logging on a running DC instance.
Is bkt safe to install?
Admin commands change server security and observability settings; review the Security Audits panel on this Prism page and restrict who can run secrets rotate in production.
SKILL.md
READMESKILL.md - Bkt
<!-- 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 --output 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 --output 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