run-package
Skill558 starsChanged 3 years agoApache-2.0View on GitHub
Run Starlark scripts and packages with kurtosis run. Covers all flags including dry-run, args-file, parallel execution, image download modes, verbosity levels, and production mode. Use when executing Kurtosis packages locally or from GitHub.
In this repository21 other files it gives its agents.
- cleanSkill
- cli-local-buildSkill
- cluster-manageSkill
- context-manageSkill
- docker-debugSkill
- docker-local-buildSkill
- dumpSkill
- enclave-inspectSkill
- engine-manageSkill
- files-inspectSkill
- gatewaySkill
- graflokiSkill
- import-composeSkill
- k8s-clean-clusterSkill
- k8s-debug-podsSkill
- k8s-dev-deploySkill
- lintSkill
- portalSkill
- port-forwardSkill
- service-manageSkill
- starlark-devSkill
The file
Files
Run Package
Execute Starlark scripts and packages with kurtosis run.
Basic usage
# Run a local package
kurtosis run ./my-package
# Run a local .star script
kurtosis run ./script.star
# Run a remote package from GitHub
kurtosis run github.com/ethpandaops/ethereum-package
# Run with inline args
kurtosis run github.com/ethpandaops/ethereum-package '{"participants": [{"el_type": "geth", "cl_type": "lighthouse"}]}'
# Run with args from a file (JSON or YAML)
kurtosis run github.com/ethpandaops/ethereum-package --args-file config.yamlNamed enclaves
# Run in a specific enclave (created if it doesn't exist)
kurtosis run --enclave my-testnet github.com/ethpandaops/ethereum-package
# Re-run in an existing enclave (adds to it)
kurtosis run --enclave my-testnet ./additional-services.starDry run
Preview what will execute without making changes:
kurtosis run --dry-run github.com/ethpandaops/ethereum-package --args-file config.yamlVerbosity levels
# Default — concise description of what happens
kurtosis run ./my-package
# Brief — concise but explicit
kurtosis run -v brief ./my-package
# Detailed — all arguments for each instruction
kurtosis run -v detailed ./my-package
# Executable — generates copy-pasteable Starlark
kurtosis run -v executable ./my-package
# Output only — just the return value
kurtosis run -v output_only ./my-packageImage handling
# Default: only pull if image doesn't exist locally
kurtosis run ./my-package
# Always pull latest image tags
kurtosis run --image-download always ./my-packageParallel execution
# Run instructions in parallel (as soon as dependencies resolve)
kurtosis run --parallel ./my-package
# Set parallelism level
kurtosis run --parallel --parallelism 8 ./my-packageAdvanced options
# Production mode — services auto-restart on failure
kurtosis run -p ./my-package
# Custom entry point file
kurtosis run --main-file deploy.star ./my-package
# Custom main function
kurtosis run --main-function-name setup ./my-package
# Don't forward ports locally
kurtosis run --no-connect ./my-package
# Show dependency graph
kurtosis run --output-graph ./my-package
# List image and package dependencies
kurtosis run --dependencies ./my-package
# Pull all dependencies locally
kurtosis run --pull --dependencies ./my-package
# Skip enclave inspect output
kurtosis run --show-enclave-inspect=false ./my-packageSafe deployment workflow
Preview, execute, then verify:
# 1. Dry run — validate the plan without making changes
kurtosis run --dry-run --enclave my-testnet github.com/ethpandaops/ethereum-package --args-file config.yaml
# 2. Execute — run the package for real
kurtosis run --enclave my-testnet github.com/ethpandaops/ethereum-package --args-file config.yaml
# 3. Verify — confirm services are running correctly
kurtosis enclave inspect my-testnetDebug mode
# Run with debug engine images
kurtosis --debug-mode run ./my-package
# Increase CLI log verbosity
kurtosis --cli-log-level debug run ./my-packageDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

