buildkite-helper
BuildKite CI/CD pipeline configuration, YAML syntax, dynamic pipelines, and agent management When user works with BuildKite, mentions CI pipelines, .buildkite/ directory, buildkite-agent commands, pipeline YAML, build steps, BuildKite API, or asks about CI configuration, pipeline generation, step dependencies, retry configuration, agent queues, or Kubernetes CI agents
What this skill does
# BuildKite Helper
## Overview
BuildKite is a CI/CD platform where builds run on your own infrastructure via agents. Pipelines are defined in YAML (static or dynamically generated). This monorepo uses BuildKite as its sole CI platform with dynamic TypeScript pipeline generation and Dagger for all build steps.
## Pipeline YAML Quick Reference
### Command Step
```yaml
steps:
- label: ":test_tube: Tests"
command: "npm test"
key: "tests"
agents: { queue: "default" }
artifact_paths: "coverage/**/*"
timeout_in_minutes: 10
retry:
automatic:
- exit_status: -1
limit: 2
- exit_status: 255
limit: 2
soft_fail:
- exit_status: 1
env:
NODE_ENV: test
```
### Wait Step
```yaml
- wait: ~ # Waits for all previous steps
- wait: ~
continue_on_failure: true # Proceed even if prior steps failed
```
### Block Step (creates implicit dependencies)
```yaml
- block: ":rocket: Deploy?"
prompt: "Ready to deploy?"
blocked_state: passed # passed | failed | running
fields:
- select: "Region"
key: "region"
options:
- { label: "US", value: "us" }
- { label: "EU", value: "eu" }
```
### Input Step (no implicit dependencies)
```yaml
- input: "Release info"
fields:
- text: "Version"
key: "version"
format: "[0-9]+\\.[0-9]+\\.[0-9]+"
```
### Trigger Step
```yaml
- trigger: "deploy-pipeline"
label: ":rocket: Deploy"
async: true # Don't wait for triggered build
build:
branch: "${BUILDKITE_BRANCH}"
commit: "${BUILDKITE_COMMIT}"
env:
DEPLOY_ENV: production
```
### Group Step
```yaml
- group: ":lock: Security"
key: "security"
steps:
- command: "audit.sh"
- command: "scan.sh"
# Consecutive groups run in parallel. No nested groups allowed.
```
## Dynamic Pipeline Generation
```bash
# Generate and upload pipeline (steps inserted after upload step)
./generate.sh | buildkite-agent pipeline upload
# Upload from file
buildkite-agent pipeline upload .buildkite/deploy.yml
# Upload JSON
echo '{"steps": [{"command": "test.sh"}]}' | buildkite-agent pipeline upload
```
**This monorepo**: TypeScript generator at `scripts/ci/src/main.ts` → change detection → JSON → `buildkite-agent pipeline upload`.
## Step Configuration
### Dependencies
```yaml
- command: "build.sh"
key: "build"
- command: "test.sh"
depends_on: "build" # Single dependency
- command: "deploy.sh"
depends_on: ["build", "test"] # Multiple dependencies
allow_dependency_failure: true # Run even if deps fail
```
### Conditionals (`if`)
C-like expressions evaluated at **upload time** (not runtime):
```yaml
- command: "deploy.sh"
if: build.branch == pipeline.default_branch
- command: "pr-check.sh"
if: build.pull_request.id != null
- command: "tagged.sh"
if: build.tag =~ /^v[0-9]/
- command: "skip-wip.sh"
if: build.message !~ /\[skip ci\]/i
```
Operators: `==`, `!=`, `=~`, `!~`, `||`, `&&`, `includes`, `!`. Variables: `build.*` (branch, commit, message, source, tag, pull_request, env()), `pipeline.*`, `organization.*`.
### Retry
```yaml
retry:
automatic:
- exit_status: -1 # Agent lost/timeout
limit: 2
- exit_status: "*" # Any non-zero (1-255)
limit: 1
manual:
permit_on_passed: true
```
Auto retry: `exit_status` (int/array/"\*"), `signal`, `signal_reason`, `limit` (max 10).
### Concurrency
```yaml
- command: "deploy.sh"
concurrency: 1
concurrency_group: "app/deploy" # Org-wide scope
concurrency_method: ordered # ordered (FIFO) | eager
```
### Other
```yaml
skip: "Temporarily disabled" # Skip with reason (max 70 chars)
soft_fail: true # All non-zero exits are soft failures
priority: 1 # Higher = dispatched first
timeout_in_minutes: 30
parallelism: 5 # Run N parallel copies
matrix: ["linux", "darwin"] # Expand step per value
```
## buildkite-agent CLI
```bash
# Pipeline
buildkite-agent pipeline upload [file] # Upload steps (stdin or file)
# Meta-data (build-level key-value, max 100KB/value)
buildkite-agent meta-data set "key" "value"
buildkite-agent meta-data get "key"
buildkite-agent meta-data get "key" --default "fallback"
# Annotations (markdown on build page, max 1MiB)
buildkite-agent annotate "message" --style info --context "ctx"
buildkite-agent annotate --style error --context "ctx" < report.md
buildkite-agent annotate --scope job "Per-job note" # v3.112+
buildkite-agent annotate --context "ctx" --remove
# Styles: default, info, warning, error, success
# Artifacts
buildkite-agent artifact upload "dist/**/*"
buildkite-agent artifact upload "report.html" --job "other-job-id"
buildkite-agent artifact download "dist/*" ./local/
buildkite-agent artifact shasum "file.tar.gz"
# Step
buildkite-agent step update "label" "New Label"
```
## Environment Variables (Key Subset)
| Variable | Description |
| ------------------------------------ | ------------------------------------------------- |
| `BUILDKITE_BRANCH` | Branch being built |
| `BUILDKITE_COMMIT` | Git commit SHA |
| `BUILDKITE_MESSAGE` | Build message (commit msg) |
| `BUILDKITE_BUILD_NUMBER` | Build number (monotonic) |
| `BUILDKITE_BUILD_URL` | URL to build on Buildkite |
| `BUILDKITE_BUILD_ID` | Build UUID |
| `BUILDKITE_JOB_ID` | Job UUID |
| `BUILDKITE_PIPELINE_SLUG` | Pipeline slug |
| `BUILDKITE_ORGANIZATION_SLUG` | Organization slug |
| `BUILDKITE_PULL_REQUEST` | PR number or `false` |
| `BUILDKITE_PULL_REQUEST_BASE_BRANCH` | PR target branch or `""` |
| `BUILDKITE_TAG` | Tag name (if tag build) |
| `BUILDKITE_SOURCE` | `webhook`, `api`, `ui`, `trigger_job`, `schedule` |
| `BUILDKITE_PARALLEL_JOB` | Parallel job index (0-based) |
| `BUILDKITE_PARALLEL_JOB_COUNT` | Total parallel jobs |
| `BUILDKITE_RETRY_COUNT` | Times job has been retried |
| `BUILDKITE_STEP_KEY` | User-defined step key |
| `BUILDKITE_AGENT_ACCESS_TOKEN` | Agent session token |
| `BUILDKITE_TRIGGERED_FROM_BUILD_ID` | Parent build UUID |
| `BUILDKITE_REPO` | Repository URL |
Variable precedence (lowest→highest): pipeline env → build env → step env → standard vars → agent env → hook exports. Use `$$VAR` to escape upload-time interpolation.
## Kubernetes Plugin (agent-stack-k8s)
```yaml
plugins:
- kubernetes:
checkout:
cloneFlags: "--depth=100"
fetchFlags: "--depth=100"
podSpecPatch:
serviceAccountName: buildkite-controller
containers:
- name: container-0
image: "ghcr.io/org/ci-base:latest"
resources:
requests: { cpu: "250m", memory: "512Mi" }
envFrom:
- secretRef: { name: ci-secrets }
volumeMounts:
- name: git-mirrors
mountPath: /buildkite/git-mirrors
readOnly: true
```
## This Monorepo's CI Patterns
**Key files:**
- `.buildkite/pipeline.yml` — Bootstrap: single step runs TypeScript generator
- `scripts/ci/src/main.ts` — Pipeline generator entry (change detection → build → JSON)
- `scripts/ci/src/change-detection.ts` — Queries BuildKite API for last green build, git diff
- `scripts/ci/src/lib/bRelated in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.