unikraft
Kraft CLI commands for building and deploying Unikraft unikernels. Use when working with Kraftfiles, deploying to Unikraft Cloud, or managing unikernel instances.
What this skill does
# Kraft CLI Reference Build and deploy unikernels with the `kraft` CLI. - Documentation: <https://unikraft.org/docs/cli> - Issues & support: <https://github.com/unikraft/kraftkit/issues> - Platform: <https://unikraft.cloud> **Targets `kraft` / KraftKit `v0.12.x`** (verified against `0.12.9`) and the Unikraft Cloud REST API `v1`. If `kraft version` reports a different major or minor, flag the mismatch and re-check flags/endpoints before following this skill — older versions may miss commands (e.g. rolling updates, volume templates) and breaking changes may appear in later majors. ## Important: Running Kraft Commands When working with kraft CLI commands: 1. **Always show the commands first** - Tell the developer what commands to run before executing them 1. **Format for copy-paste** - Display commands in a code block ready to copy-paste into the terminal 1. **Ask before running** - Ask if the developer wants you to run the commands, as there can be authentication issues when `UKC_TOKEN` is not set in the AI's terminal session 1. **Let developer run if needed** - If commands fail due to missing tokens, provide the commands for the developer to run manually ## Environment Setup Cloud commands need `UKC_TOKEN` (and usually `UKC_METRO`). **Export them once per terminal session, not once per command** — every shell in the same session inherits them, so there is no reason to re-export before each `kraft cloud`, `curl`, or deploy call. ```bash # Run once when you open the terminal: export UKC_TOKEN="your-token" # Unikraft Cloud API token (Bearer for the REST API too) export UKC_METRO=fra # Metro/region (e.g., fra, dal, sin, was, sfo) ``` If the token lives in a dotenv file, source it once: ```bash # Once per session: set -a; source .env.github; set +a export UKC_TOKEN="$KRAFTCLOUD_TOKEN" ``` Don't repeat the `export` in follow-up commands or copy-paste snippets — if a later command can't see the token, re-check the session, don't re-export blindly. Persist the token in a shell profile or secret manager only if you understand the blast radius; otherwise keep it session-scoped. ### Metro Names: Never Use `fra0` Unikraft Cloud migrated to suffix-less metro codes. Use the current names only: | Use | Never use | | ----- | --------- | | `fra` | `fra0` | | `dal` | `dal0` | | `sin` | `sin0` | This applies everywhere a metro appears: `--metro` / `UKC_METRO`, the API host (`api.fra.unikraft.cloud`, not `api.fra0.unikraft.cloud`), and instance FQDNs (`*.fra.unikraft.app`, not `*.fra0.unikraft.app`). Older docs, cached examples, and legacy deployments may still show `fra0` — treat any `fra0` string as a bug and replace it with `fra`. ## Build Commands ```bash kraft build # Configure and build Unikraft unikernels kraft clean # Remove build object files kraft menu # Open configuration editor TUI ``` ## Project Library Commands ```bash kraft lib add <lib> # Add unikraft library to the project kraft lib create # Initialize a library from a template kraft lib remove <lib> # Remove a library dependency ``` ## Packaging Commands ```bash kraft pkg list # List installed Unikraft component packages kraft pkg pull <pkg> # Pull a unikernel and/or its dependencies kraft pkg push # Push a unikernel package to registry kraft pkg update # Retrieve new component/library/package lists kraft pkg info <pkg> # Show information about a package kraft pkg export # Export a package kraft pkg remove # Remove selected local packages ``` ## Local Runtime Commands ```bash kraft run # Run a unikernel kraft ps # List running unikernels kraft stop <name> # Stop one or more running unikernels kraft start <name> # Start one or more machines kraft pause <name> # Pause one or more running unikernels kraft logs <name> # Fetch the logs of a unikernel kraft remove <name> # Remove one or more running unikernels ``` ## Local Networking Commands ```bash kraft net create # Create a new machine network kraft net list # List machine networks kraft net inspect <name> # Inspect a machine network kraft net up <name> # Bring a network online kraft net down <name> # Bring a network offline kraft net remove <name> # Remove a network ``` ## Local Volume Commands ```bash kraft vol create # Create a machine volume kraft vol ls # List machine volumes kraft vol inspect <name> # Inspect a machine volume kraft vol remove <name> # Remove a volume ``` ## Compose Commands (Local) ```bash kraft compose up # Run a compose project kraft compose down # Stop and remove a compose project kraft compose ps # List running services of current project kraft compose logs # Print the logs of services kraft compose build # Build or rebuild services kraft compose create # Create a compose project kraft compose start # Start a compose project kraft compose stop # Stop a compose project kraft compose pause # Pause a compose project kraft compose unpause # Unpause a compose project kraft compose pull # Pull images of services kraft compose push # Push images of services ``` ## Cloud Deployment Commands ```bash kraft cloud deploy # Deploy your application to Unikraft Cloud kraft cloud quota # View your resource quota kraft cloud tunnel # Forward a local port to an unexposed instance ``` ## Cloud Instance Commands ```bash kraft cloud instance create # Create an instance kraft cloud instance list # List instances kraft cloud instance get # Retrieve the state of instances kraft cloud instance logs # Get console output of instances kraft cloud instance start # Start instances kraft cloud instance stop # Stop instances kraft cloud instance restart # Restart instance(s) kraft cloud instance remove # Remove instances ``` ## Cloud Service Commands ```bash kraft cloud service create # Create a service kraft cloud service list # List services kraft cloud service get # Retrieve the state of services kraft cloud service logs # Get console output for services kraft cloud service drain # Drain instances in a service kraft cloud service remove # Delete services ``` ## Cloud Image Commands ```bash kraft cloud image list # List all images at a metro for your account kraft cloud image remove # Remove an image ``` ## Cloud Volume Commands ```bash kraft cloud volume create # Create a persistent volume kraft cloud volume list # List persistent volumes kraft cloud volume get # Retrieve the state of persistent volumes kraft cloud volume import # Import local data to a persistent volume kraft cloud volume attach # Attach a persistent volume to an instance kraft cloud volume detach # Detach a persistent volume from an instance kraft cloud volume remove # Permanently delete persistent volume(s) ``` ## Cloud Volume Template Commands ```bash kraft cloud volume template create # Create volume template(s) kraft cloud volume template list # List volume templates kraft cloud volume template get # Retrieve the state of volume templates kraft cloud volume template remove # Permanently delete volume template(s) ``` ## Cloud Autoscale Commands ```bash kraft cloud scale init # Initialize autoscale configuration for a service kraft cloud scale add # Add an autoscale configuration policy kraft cloud scale get # Get an autoscale configuration or policy kraft cloud scale remove # Delete an autoscale configuration policy kraft cloud scale reset # Reset autoscale configuration of a service ``` ## Cloud Certificate Commands ```bash kraft cloud cert create # Create a certificate kraft cloud
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.