jk
Jenkins CLI for controllers. Use when users need to manage jobs, pipelines, config.xml, runs, logs, artifacts, credentials, nodes, or queues in Jenkins. Triggers include "jenkins", "jk", "pipeline", "build", "job create", "job config", "config.xml", "run logs", "jenkins credentials", "jenkins node".
What this skill does
# Jenkins CLI (jk) `jk` is a GitHub CLI–style interface for **Jenkins controllers**. It provides modern, scriptable workflows for developers and operators. ## Dependency Check **Before executing any `jk` command**, verify the CLI is installed: ```bash jk --version ``` For `jk job create`, `jk job config`, `jk job configure`, and `jk job scan`, use `jk` `0.0.29` or newer. If the command fails or `jk` is not found, install it using one of these methods: | Platform | Command | |----------|---------| | macOS/Linux | `brew install avivsinai/tap/jk` | | Windows | `scoop bucket add avivsinai https://github.com/avivsinai/scoop-bucket && scoop install jk` | | Go | `go install github.com/avivsinai/jenkins-cli/cmd/jk@latest` | | Binary | Download from [GitHub Releases](https://github.com/avivsinai/jenkins-cli/releases) | **Only proceed with `jk` commands after confirming installation succeeds.** ## Authentication ```bash # Login with credentials jk auth login https://jenkins.example.com --username alice --token <API_TOKEN> # Login to a Jenkins controller that uses Google/OIDC/SSO in the browser jk auth login https://jenkins.example.com --username [email protected] --token <JENKINS_API_TOKEN> # Login with custom context name jk auth login https://jenkins.example.com --name prod --username alice --token <TOKEN> # Login with TLS options jk auth login https://jenkins.example.com --username alice --token <TOKEN> --insecure jk auth login https://jenkins.example.com --username alice --token <TOKEN> --ca-file /path/to/ca.pem # Check auth status (active context) jk auth status # Logout from a context jk auth logout # Logout from active context jk auth logout prod # Logout from specific context ``` Options for `auth login`: - `--name` — Context name (defaults to hostname) - `--username` — Jenkins user ID (Google/SSO users: usually your email) - `--token` — Jenkins API token - `--insecure` — Skip TLS verification - `--proxy` — Proxy URL - `--ca-file` — Custom CA bundle - `--set-active` — Set as active context (default: true) - `--allow-insecure-store` — Allow encrypted file fallback For Google OAuth, OpenID Connect, Okta, Azure AD, or other browser SSO security realms, first sign in to Jenkins in the browser and create a Jenkins API token from `/me/configure`. Use that Jenkins API token with `--token`; do not use a Google/OIDC access token. ## Contexts Contexts store controller URLs and credentials for easy switching: ```bash # List contexts (* = active) jk context ls # Switch active context jk context use prod-jenkins # Remove a context jk context rm staging ``` Environment: `JK_CONTEXT` overrides active context. ## Quick Command Reference | Task | Command | |------|---------| | Search jobs | `jk search --job-glob '*deploy*'` | | List jobs | `jk job ls` | | View job | `jk job view team/app` | | Create multibranch job | `jk job create auth-relay --folder platform/services --repo-owner playg --repository repo` | | Fetch job config | `jk job config platform/services/auth-relay` | | Patch Jenkinsfile path | `jk job configure platform/services/auth-relay --script-path services/auth-relay/Jenkinsfile` | | Rescan multibranch job | `jk job scan platform/services/auth-relay` | | List runs | `jk run ls team/app` | | Start run | `jk run start team/app -p KEY=value` | | View run | `jk run view team/app 128` | | Follow logs | `jk run start team/app --follow` | | Stream logs | `jk log team/app 128 --follow` | | Download artifacts | `jk artifact download team/app 128` | | Test report | `jk test report team/app 128` | | List credentials | `jk cred ls` | | List nodes | `jk node ls` | | View queue | `jk queue ls` | | List plugins | `jk plugin ls` | ## Job Discovery ```bash # Search across folders jk search --job-glob '*deploy*' --limit 10 # Search in specific folder jk search --folder team/services --job-glob '*api*' # Filter by run results jk search --job-glob '*' --filter result=FAILURE --since 7d # With parameter filters jk search --job-glob '*/deploy-*' --filter param.ENV=production ``` ## Job Operations ```bash # List jobs in root jk job ls # List jobs in folder (positional or flag) jk job ls team/app jk job ls --folder team/app # View job details jk job view team/app/pipeline # Create a Bitbucket-backed Multibranch Pipeline job jk job create auth-relay \ --folder platform/services \ --repo-owner playg \ --repository taboola-sales-skills \ --script-path services/auth-relay/Jenkinsfile \ --credentials bitbucket-ro \ --branch-strategy all # Fetch raw config.xml for a job jk job config platform/services/auth-relay # Replace config.xml from a file or stdin jk job configure platform/services/auth-relay --file auth-relay.config.xml cat auth-relay.config.xml | jk job configure platform/services/auth-relay --stdin # Patch only the Jenkinsfile path in a multibranch config jk job configure platform/services/auth-relay --script-path services/auth-relay/Jenkinsfile # Trigger a multibranch rescan jk job scan platform/services/auth-relay ``` ## Run Management ### Listing Runs ```bash # List recent runs jk run ls team/app/pipeline # Limit results jk run ls team/app/pipeline --limit 50 # Filter runs jk run ls team/app/pipeline --filter result=SUCCESS jk run ls team/app/pipeline --filter result=FAILURE --since 7d # Filter by parameters jk run ls team/app/pipeline --filter param.ENV=staging # Include queued builds jk run ls team/app/pipeline --include-queued # Group by parameter jk run ls team/app/pipeline --group-by param.ENV --agg last # With metadata for agents jk run ls team/app/pipeline --json --with-meta # Pagination jk run ls team/app/pipeline --cursor <cursor-from-previous> ``` ### Starting Runs ```bash # Start a run jk run start team/app/pipeline # Start with parameters jk run start team/app/pipeline -p BRANCH=main -p ENV=staging # Start and follow logs jk run start team/app/pipeline --follow # Start, wait for completion (no log streaming) jk run start team/app/pipeline --wait --timeout 10m # Get only the result jk run start team/app/pipeline --follow --result # Fuzzy job matching jk run start deploy --fuzzy ``` ### Viewing Runs ```bash # View run details jk run view team/app/pipeline 128 # Get only result status jk run view team/app/pipeline 128 --result # Exit with build result code jk run view team/app/pipeline 128 --exit-status # Wait for completion jk run view team/app/pipeline 128 --wait --timeout 5m # Show summary jk run view team/app/pipeline 128 --summary ``` ### Other Run Commands ```bash # View run parameters jk run params team/app/pipeline # Cancel a run jk run cancel team/app/pipeline 128 jk run cancel team/app/pipeline 128 --mode term jk run cancel team/app/pipeline 128 --mode kill # Rerun a build (with same parameters) jk run rerun team/app/pipeline 128 jk run rerun team/app/pipeline 128 --follow ``` ## Logs ```bash # View console log (snapshot) jk log team/app/pipeline 128 # Stream live logs jk log team/app/pipeline 128 --follow # Custom poll interval jk log team/app/pipeline 128 --follow --interval 2s # Plain output (no decorations) jk log team/app/pipeline 128 --plain ``` ## Artifacts ```bash # List artifacts jk artifact ls team/app/pipeline 128 # Download all artifacts jk artifact download team/app/pipeline 128 # Download with pattern filter jk artifact download team/app/pipeline 128 --pattern "**/*.jar" jk artifact download team/app/pipeline 128 -p "reports/**/*.xml" # Output directory jk artifact download team/app/pipeline 128 -o ./artifacts/ # Allow empty result (no error if no matches) jk artifact download team/app/pipeline 128 -p "*.log" --allow-empty ``` ## Test Results ```bash # View test report jk test report team/app/pipeline 128 # JSON output jk test report team/app/pipeline 128 --json ``` ## Credentials ```bash # List credentials (system scope) jk cred ls # List folder-scoped credentials jk cred ls --scope folder --folder team/app # Create secre
Related 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.