How do I install the Stk Deploy skill?

Run npx skillmds@latest add level09/stk-deploy in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Stk Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Stk Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Stk Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Stk Deploy?

level09 (@level09) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Stk Deploy by level09 — Agent Skill

Name: Stk Deploy
Author: level09

File contents

Deploy stk App to Production

One-shot production install via deploy.sh (framework root). Installs Caddy (auto-TLS, security headers, static caching), a systemd service, a non-root app user, generated secrets, and hardens the box (SSH key-only, fail2ban, ufw). SQLite by default, PostgreSQL+Redis optional.

Prerequisites

Fresh Ubuntu/Debian VPS with root SSH access.
DNS A record for the domain pointing at the server (Caddy needs it for TLS).
App repo pushed to GitHub and public, or see the private-repo note below.

Install (non-interactive)

Run from your machine against the server, or on the server as root:

wget -qO /tmp/deploy.sh https://raw.githubusercontent.com/level09/stk/master/deploy.sh
sudo DOMAIN=example.com REPO=<github-user>/<repo> bash /tmp/deploy.sh

Env vars: DOMAIN (required), REPO (default level09/stk), BRANCH (default master), DB=sqlite|postgres, ADMIN_EMAIL, ADMIN_PASSWORD, PYTHON_PORT (default 5000), SKIP_SSL=true (HTTP only, no TLS).

Ends at a live https://<domain> with an admin login. Credentials are saved on the server at /home/<app-user>/.credentials.

Hard warnings

Never re-run deploy.sh on a live app. It is install-only: it deletes and re-clones the app directory. With SQLite the database is instance/stk.db inside that directory, so a re-run destroys production data. Use the update flow below.
Private repos fail silently at the clone step: the script clones over plain HTTPS. Either make the repo public, or pre-seed a read-only GitHub token on the server and clone via git@github.com: manually first.

Update flow (every deploy after the first)

ssh <app-user>@<domain>
cd ~/<domain>
git pull
uv sync --frozen --no-dev
uv run --no-sync stk db upgrade   # only if models changed
sudo systemctl restart <domain>.service

The app user's sudoers allows managing only its own service.

Verify

curl -I https://<domain> returns 200/302 with the security headers.
Log in as admin, create a throwaway record, restart the service, confirm it survives (proves the DB path).

---name: stk-deploydescription: Deploy an stk app to production on a fresh VPS with HTTPS, systemd, and a hardened OS. Use when taking an stk app live, deploying to a server, or setting up production hosting for a domain.---# Deploy stk App to ProductionOne-shot production install via `deploy.sh` (framework root). Installs Caddy(auto-TLS, security headers, static caching), a systemd service, a non-root appuser, generated secrets, and hardens the box (SSH key-only, fail2ban, ufw).SQLite by default, PostgreSQL+Redis optional.## Prerequisites1. Fresh Ubuntu/Debian VPS with root SSH access.2. DNS A record for the domain pointing at the server (Caddy needs it for TLS).3. App repo pushed to GitHub **and public**, or see the private-repo note below.## Install (non-interactive)Run from your machine against the server, or on the server as root:```bashwget -qO /tmp/deploy.sh https://raw.githubusercontent.com/level09/stk/master/deploy.shsudo DOMAIN=example.com REPO=<github-user>/<repo> bash /tmp/deploy.sh```Env vars: `DOMAIN` (required), `REPO` (default `level09/stk`), `BRANCH`(default `master`), `DB=sqlite|postgres`, `ADMIN_EMAIL`, `ADMIN_PASSWORD`,`PYTHON_PORT` (default 5000), `SKIP_SSL=true` (HTTP only, no TLS).Ends at a live `https://<domain>` with an admin login. Credentials are savedon the server at `/home/<app-user>/.credentials`.## Hard warnings- **Never re-run deploy.sh on a live app.** It is install-only: it deletes and re-clones the app directory. With SQLite the database is `instance/stk.db` *inside* that directory, so a re-run destroys production data. Use the update flow below.- **Private repos fail silently at the clone step**: the script clones over plain HTTPS. Either make the repo public, or pre-seed a read-only GitHub token on the server and clone via `git@github.com:` manually first.## Update flow (every deploy after the first)```bashssh <app-user>@<domain>cd ~/<domain>git pulluv sync --frozen --no-devuv run --no-sync stk db upgrade # only if models changedsudo systemctl restart <domain>.service```The app user's sudoers allows managing only its own service.## Verify- `curl -I https://<domain>` returns 200/302 with the security headers.- Log in as admin, create a throwaway record, restart the service, confirm it survives (proves the DB path).

Frequently asked questions

Stk Deploy