Agent skill · software engineering · aiskillstore
bitbucket-devops
Comprehensive Bitbucket pipeline automation using direct Node.js API calls. Monitor pipeline status, analyze failures, download logs, and trigger builds. Use this skill when the user asks to check pipeline status, find failing pipelines, download logs, trigger builds, or debug pipeline failures. No MCP approval prompts required - uses Bash tool with node commands.
Why this skill is useful
Adds executable scripts for comprehensive Bitbucket pipeline automation that aren't available in public documentation.
What it needs
Requires bash, node installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Bitbucket DevOps Skill This skill provides comprehensive Bitbucket DevOps automation using direct Node.js API calls via a Bash-equivalent tool. Built on the bitbucket-mcp client library. It's plain Node.js CLI invocation with no Claude-specific dependency, so it runs unchanged under Claude Code, AGY, OpenCode, or any other agent runtime that can shell out to node. Note on paths: Paths below (~/.claude/skills/bitbucket-devops/...) reflect Claude Code's skill-install convention, since install.sh/install.ps1 default to --llm claude. If this skill was installed with --llm agy or --llm opencode, substitute ~/.gemini/antigravity-cli/skills/bitbucket-devops/ or ~/.config/opencode/skills/bitbucket-devops/ respectively (or whatever TARGETDIR was used) - the commands themselves are identical. Key Advantage: Uses direct Node.js calls via a Bash-equivalent tool instead of MCP tools. This works the same way in any agent runtime that can invoke shell commands (Claude Code, AGY, OpenCode, etc.) - there's no Claude-specific API or tool assumption anywhere in this skill's code. In Claude Code specifically, Bash is auto-approved by default, which also eliminates the MCP approval-prompt friction described in GitHub Issue #10801; other runtimes may have their own approval model for shell commands, but the underlying calls are identical either way. ⚠️ MANDATORY: How to Approach User Requests You MUST follow this three-tier fallback strategy for ALL Bitbucket operations. This is REQUIRED, not optional. CRITICAL RULES: DO NOT create new .js files for Bitbucket API calls DO NOT use node -e for inline Bitbucket API operations ONLY use the pre-built CLI tools listed below ALWAYS start with Tier 1, fall back to Tier 2 if needed, use Tier 3 only as last resort Tier 1: High-Level Helper Functions (REQUIRED FIRST STEP) You MUST check these helpers FIRST before attempting any other approach. These solve common workflows in a single command. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/bitbucket-devops