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

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

# bkt perms

Manage user permissions at the project and repository level on Bitbucket Data Center.

Grant, revoke, and list permissions for individual users. Project-level
permissions apply to all repositories within that project, while repository-level
permissions override the project defaults for a specific repository.

This command group is available for Data Center contexts only.

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

### Examples

```bash
# List who has access to a project
  bkt perms project list --project MYPROJ

  # Grant a user write access to a specific repository
  bkt perms repo grant --project MYPROJ --repo my-service --user jdoe --perm REPO_WRITE

  # Revoke a user's project-level permission
  bkt perms project revoke --project MYPROJ --user jdoe
```

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [project](#bkt-perms-project) | Manage project-level permissions *(DC)* | — |
| [repo](#bkt-perms-repo) | Manage repository-level permissions *(DC)* | — |

## bkt perms project

Manage project-level permissions on Bitbucket Data Center.

Project permissions control default access for all repositories within a project.
You can list current permission entries, grant a permission level to a user, or
revoke a user's project permission entirely. Valid permission levels are
PROJECT_READ, PROJECT_WRITE, and PROJECT_ADMIN.

```
bkt perms project <command> [flags]
```

### Examples

```bash
# List all users with permissions on a project
  bkt perms project list --project MYPROJ

  # Grant admin access to a user
  bkt perms project grant --project MYPROJ --user jdoe --perm PROJECT_ADMIN

  # Revoke a user's project permission
  bkt perms project revoke --project MYPROJ --user jdoe
```

| Subcommand | Description |
|---|---|
| grant | Grant project permissions (DC only) |
| list | List project permissions (DC only) |
| revoke | Revoke project permissions (DC only) |

## bkt perms project grant

Grant a permission level to a user on a Bitbucket Data Center project.

The user receives the specified permission for the project and inherits it
across all repositories within that project unless overridden at the repository
level. Valid values for --perm are PROJECT_READ, PROJECT_WRITE, and
PROJECT_ADMIN. If --perm is omitted it defaults to PROJECT_READ.

### Usage

```
bkt perms project grant [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--perm` |  | Permission (PROJECT_READ, PROJECT_WRITE, PROJECT_ADMIN) |
| `--project` |  | Bitbucket project key (required) |
| `--user` |  | Username to grant (required) |

### 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
# Grant read access (default)
  bkt perms project grant --project MYPROJ --user jdoe

  # Grant write access
  bkt perms project grant --project MYPROJ --user jdoe --perm PROJECT_WRITE

  # Grant admin access
  bkt perms project grant --project MYPROJ --user jdoe --perm PROJECT_ADMIN
```

## bkt perms project list

List the permission entries for a Bitbucket Data Center project.

Displays each user who has been granted explicit access to the project along
with their permission level (PROJECT_READ, PROJECT_WRITE, or PROJECT_ADMIN).
Use --limit to control how many entries are returned; set it to 0 to fetch all.

### Usage

```
bkt perms project list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--limit` |  | Maximum entries to display (0 for all) |
| `--project` |  | Bitbucket project key (required) |

### 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 permissions for a project
  bkt perms project list --project MYPROJ

  # List all permissions without a cap
  bkt perms project list --project MYPROJ --limit 0

  # Output as JSON
  bkt perms project list --project MYPROJ --json
```

## bkt perms project revoke

Revoke a user's permission on a Bitbucket Data Center project.

Removes the explicit project-level permission entry for the specified user.
After revocation the user loses access granted at the project level, though
they may still have access through repository-level or global permissions.

### Usage

```
bkt perms project revoke [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--project` |  | Bitbucket project key (required) |
| `--user` |  | Username to revoke (required) |

### 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
# Revoke a user's project permission
  bkt perms project revoke --project MYPROJ --user jdoe

  # Revoke using a different context
  bkt perms project revoke --project MYPROJ --user jdoe --context my-dc
```

## bkt perms repo

Manage repository-level permissions on Bitbucket Data Center.

Repository permissions override the project defaults for a specific repository.
You can list current permission entries, grant a permission level to a user, or
revoke a user's repository permission entirely. Valid permission levels are
REPO_READ, REPO_WRITE, and REPO_ADMIN.

```
bkt perms repo <command> [flags]
```

### Examples

```bash
# List permissions on a repository
  bkt perms repo list --project MYPROJ --repo my-service

  # Grant write access to a user
  bkt perms repo grant --project MYPROJ --repo my-service --user jdoe --perm REPO_WRITE

  # Revoke a user's repository permission
  bkt perms repo revoke --project MYPROJ --repo my-service --user jdoe
```

| Subcommand | Description |
|---|---|
| grant | Grant repository permissions (DC only) |
| list | List repository permissions (DC only) |
| revoke | Revoke repository permissions (DC only) |

## bkt perms repo grant

Grant a permission level to a user on a Bitbucket Data Center repository.

The user receives the specified permission for the repository, overriding any
project-level permission they may already have. Valid values for --perm are
REPO_READ, REPO_WRITE, and REPO_ADMIN. If --perm is omitted it defaults to
REPO_READ.

### Usage

```
bkt perms repo grant [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--perm` |  | Permission (REPO_READ, REPO_WRITE, REPO_ADMIN) |
| `--project` |  | Bitbucket project key (required) |
| `--repo` |  | Repository slug (required) |
| `--user` |  | Username to grant (required) |

### 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
# Grant read access (default)
  bkt perms repo grant --project MYPROJ --repo my-service --user jdoe

  # Grant write access
  bkt perms repo grant --project MYPROJ --repo my-service --user jdoe --perm REPO_WRITE

  # Grant admin access
  bkt perms repo grant --project MYPROJ --repo my-service --user jdoe --perm REPO_ADMIN
```

## bkt perms repo list

List the permission entries for a Bitbucket Data Center repository.

Displays each user who has been granted explicit access to the repository along
with their permission level (REPO_READ, REPO_WRITE, or REPO_ADMIN). Use --limit
to control how many entries are returned; set it to 0 to fetch all.

### Usage

```
bkt perms repo list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--limit` |  | Maximum entries to display (0 for all) |
| `--project` |  | Bitbucket project key (required) |
| `--repo` |  | Repository slug (required) |

### 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 permissions for a repository
  bkt perms repo list --project MYPROJ --repo my-service

  # Fetch all permission entries
  bkt perms repo list --project MYPROJ --repo my-service --limit 0

  # Output as JSON
  bkt perms repo list --project MYPROJ --repo my-service --json
```

## bkt perms repo revoke

Revoke a user's permission on a Bitbucket Data Center repository.

Removes the explicit repository-level permission entry for the specified user.
After revocation the user may still have access through project-level or global
permissions.

### Usage

```
bkt perms repo revoke [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--project` |  | Bitbucket project key (required) |
| `--repo` |  | Repository slug (required) |
| `--user` |  | Username to revoke (required) |

### 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
# Revoke a user's repository permission
  bkt perms repo revoke --project MYPROJ --repo my-service --user jdoe

  # Revoke using a different context
  bkt perms repo revoke --project MYPROJ --repo my-service --user jdoe --context my-dc
```

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