Start a Flisk stack with `flisk up`, preview it first with `flisk up <stack> --dry-run`, and confirm the healthy URLs. Use when the user asks to run, start, or bring up their local services, or after changing service.json files. To check a stack that is already running, use flisk-status; when it fails, use flisk-troubleshoot.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Flisk Up?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/flisk-sh-flisk-up-flisk)
---
name: flisk-up
description: Start a Flisk stack with `flisk up`, preview it first with `flisk up <stack> --dry-run`, and confirm the healthy URLs. Use when the user asks to run, start, or bring up their local services, or after changing service.json files. To check a stack that is already running, use flisk-status; when it fails, use flisk-troubleshoot.
license: MIT
compatibility: Requires the flisk CLI. Services that declare a `command` need only their own runtime; other services need Docker and Tilt. Does not deploy.
metadata:
author: flisk-sh
version: "1.0"
---
# Flisk up
Start local services from `service.json` manifests. Flisk writes the Docker and Tilt configuration; do not write Dockerfiles, Tiltfiles, or routes by hand.
## Workflow
1. Run `flisk doctor` if the machine has not been checked yet. Stop on unresolved errors.
2. Preview the stack: `flisk up <stack> --dry-run`. Show the user which services and URLs will start.
3. Start it: `flisk up <stack>`. Omit `<stack>` to start every stack.
4. Confirm health with `flisk status --json`. Report each service's URL only after it reports healthy.
5. If `flisk up` refuses to start because generated files differ from `service.json`, regenerate from the source manifest. Use `--ignore-drift` only when the user asks to start anyway.
## Services that run without Docker
A service whose `service.json` declares `command` (for example `"command": "node server.js"`, with `appName`, `appType`, `port`, `dependsOn` and an optional `healthCheckPath`) runs as a local process. When every selected service has one, `flisk up` needs no Docker and no Tilt: it starts them in `dependsOn` order, prints `http://localhost:<port>` for each, prefixes their output, and restarts a service that exits. It stays in the foreground; `flisk down` stops it from another terminal.
- Prefer `command` services for a simple app (an API, a website, a worker). Use Docker services when the app needs a database, one gateway URL, or the container it deploys.
- A database or cache can run in Docker next to `command` services: give it an `image` (no `command`, no `dockerfile`) and `flisk up` starts it with `docker run` (a mixed run, docs/run-without-docker.md). Any other mix, such as a service built from a Dockerfile next to a `command` service, is refused with `MIXED_RUNTIME`.
- `flisk up --json` reports `"runtime": "native"` and each service's URL. Read output with `flisk logs --service <name>`.
- Guide: docs/run-without-docker.md.
## Guardrails
- Ask before starting a large stack or one likely to build many images; cold builds can take several minutes.
- Use `flisk up -f` only when the user agrees to kill the existing Tilt process.
- Do not edit `.autogenerated/` or other generated output. Change `service.json` instead.
- Flisk runs locally. Do not use it to deploy to a cluster.
## MCP tools
If a `mcp__flisk__*` tool is missing, run `flisk connect claude` in the project folder and restart Claude Code. The CLI commands in this skill work without MCP as well.