一键在 Manus 中运行任何 Skill

bitbucket-api-env

星标0

分支0

更新时间2026年5月9日 14:10

Use this skill for Bitbucket Cloud work when the user wants REST/API access through injected environment variables and explicitly does not want Bitbucket MCP, mcporter Bitbucket, or connector-backed Bitbucket tools.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

zereight

zereight/skill

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Bitbucket API Env

Use Bitbucket Cloud REST directly. Do not use Bitbucket MCP, mcporter list bitbucket, mcporter call bitbucket.*, or connector-backed Bitbucket tools unless the user explicitly overrides this skill.

Environment

Required repository target:

export BITBUCKET_WORKSPACE=bank-x
export BITBUCKET_REPO_SLUG=mobile-app-workspace

Use one auth mode.

Basic auth with Atlassian email and API token:

export BITBUCKET_USERNAME="$ATLASSIAN_USER_EMAIL"
export BITBUCKET_API_TOKEN="$ATLASSIAN_API_TOKEN"

Bearer auth with a Bitbucket access token:

export BITBUCKET_ACCESS_TOKEN="<token>"

Never paste token values into the conversation or hard-code them into files. Prefer already-exported environment variables. If variables are missing, say exactly which names are missing.

Workflow

Parse Bitbucket URLs into workspace, repo_slug, and pull request id when possible. Otherwise use the environment target.
Use the bundled helper for common read paths:

node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs pr 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs comments 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs activity 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs diffstat 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs diff 123 > /private/tmp/bitbucket-pr-123.diff

For custom endpoints, use request:

node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs request GET "/repositories/$BITBUCKET_WORKSPACE/$BITBUCKET_REPO_SLUG/pullrequests?state=OPEN&pagelen=50"

Keep raw large outputs in /private/tmp; summarize with exact ids, statuses, branch names, file paths, or line references.
For Korean internal engineering requests, answer in Korean.

Guardrails

Default to read-only. Mutating methods require both an explicit user request and BITBUCKET_API_ALLOW_WRITE=1.
Report the exact HTTP status and response body excerpt when an API call fails.
Do not claim that a PR, comment, or file was checked unless the matching API call was actually run.
Do not fall back to Bitbucket MCP because REST failed. Say the API failure directly, then ask whether to try another route.

Common Endpoints

Pull request: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}
Comments: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/comments
Activity: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/activity
Diff: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/diff
Diffstat: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/diffstat
Commits: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/commits

同仓库更多 Skills

同仓库

autocontext

zereight/skill

Run iterative agent evaluation and improvement loops (judge, improve, scenarios, playbooks) via pi-autocontext or autoctx CLI. Use when improving repeatable agent workflows (review rubrics, skill quality, scenario-based feedback), checking run status, or accumulating knowledge—not for one-off code edits or repo pattern drift (use continuity) or single PR review (use zereight-review).

2026-05-260

harness

zereight/skill

Pi-native evaluate→improve→persist harness. Provides a systematic loop for generating candidates, judging them against rubrics, and accumulating knowledge as playbooks. Use for iterative output improvement, not for one-off edits (use continuity) or single PR review (use zereight-review).

2026-05-260

skill-cleaner

zereight/skill

Audit agent skills — token cost, duplicates, outdated plugin versions, unused skills, and overly long descriptions. Use when trimming skill prompt budget, finding duplicate or unused skills, auditing plugin versions, or deciding which skills to remove.

2026-05-260

skill-not-showing

zereight/skill

Diagnose why a skill is missing from Pi /skill or Cursor lists. Use when a skill exists on disk but does not appear, Pi shows only project or extension skills, or after adding a repo skill under .agents/skills/.

2026-05-260

zereight-review

zereight/skill

Comprehensive code review skill for practical PR feedback. Use for feature, bugfix, and refactor reviews. Prioritizes correctness, edge cases, logic invariants, fallback-chain safety, async state transitions, architecture analysis, OWASP security, and clear actionable feedback.

2026-05-260

ljg-skill-map

zereight/skill

Skill map and inventory workflow. Use for scanning installed skills, skill overview, 스킬 목록, skill map.

2026-05-260

name	bitbucket-api-env
description	Use this skill for Bitbucket Cloud work when the user wants REST/API access through injected environment variables and explicitly does not want Bitbucket MCP, mcporter Bitbucket, or connector-backed Bitbucket tools.

Bitbucket API Env

Environment

Required repository target:

export BITBUCKET_WORKSPACE=bank-x
export BITBUCKET_REPO_SLUG=mobile-app-workspace

Use one auth mode.

Basic auth with Atlassian email and API token:

export BITBUCKET_USERNAME="$ATLASSIAN_USER_EMAIL"
export BITBUCKET_API_TOKEN="$ATLASSIAN_API_TOKEN"

Bearer auth with a Bitbucket access token:

export BITBUCKET_ACCESS_TOKEN="<token>"

Never paste token values into the conversation or hard-code them into files. Prefer already-exported environment variables. If variables are missing, say exactly which names are missing.

Workflow

Parse Bitbucket URLs into workspace, repo_slug, and pull request id when possible. Otherwise use the environment target.
Use the bundled helper for common read paths:

node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs pr 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs comments 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs activity 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs diffstat 123
node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs diff 123 > /private/tmp/bitbucket-pr-123.diff

For custom endpoints, use request:

node /Users/tao.exe/Documents/skill/skills/bitbucket-api-env/scripts/bitbucket-api.mjs request GET "/repositories/$BITBUCKET_WORKSPACE/$BITBUCKET_REPO_SLUG/pullrequests?state=OPEN&pagelen=50"

Keep raw large outputs in /private/tmp; summarize with exact ids, statuses, branch names, file paths, or line references.
For Korean internal engineering requests, answer in Korean.

Guardrails

Default to read-only. Mutating methods require both an explicit user request and BITBUCKET_API_ALLOW_WRITE=1.
Report the exact HTTP status and response body excerpt when an API call fails.
Do not claim that a PR, comment, or file was checked unless the matching API call was actually run.
Do not fall back to Bitbucket MCP because REST failed. Say the API failure directly, then ask whether to try another route.

Common Endpoints

Pull request: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}
Comments: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/comments
Activity: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/activity
Diff: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/diff
Diffstat: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/diffstat
Commits: GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/commits