Static.app Deployment Skill

Deploy static websites and applications to Static.app hosting directly from OpenClaw.

Workspace Structure

All Static.app operations in your workspace use a dedicated folder structure:

CODEBLOCK0

• - New sites: Created in staticapp/ subfolders before deployment
• Downloaded sites: Extracted to staticapp/{pid}/ for editing

How Static.app Handles Files

Static.app automatically creates clean URLs from your filenames:

No subdirectories needed! Just create .html files in the root folder.

Project Structure

Simple Multi-Page Site

CODEBLOCK1

JavaScript App (React, Vue, etc.)

For JS apps, build first, then deploy the dist (or build) folder:

CODEBLOCK2

Prerequisites

1. 1. Get API Key: Go to https://static.app/account/api and create an API key (starts with sk_)
2. Set Environment Variable: Store the API key in STATIC_APP_API_KEY env var

Usage

Deploy Multi-Page Site

CODEBLOCK3

Deploy Specific Directory

CODEBLOCK4

Update Existing Site

CODEBLOCK5

List All Sites

CODEBLOCK6

List Site Files

CODEBLOCK7

Options:

• - --raw — Output raw JSON
• INLINECODE16 — Specify API key

Delete Site

CODEBLOCK8

Options:

• - -f, --force — Skip confirmation prompt
• INLINECODE18 — Specify API key

Download Site

Download an existing site to your workspace for editing:

CODEBLOCK9

This will:

1. 1. Fetch the download URL from Static.app API
2. Download the site archive
3. Extract it to INLINECODE19

Options:

• - -p, --pid — Site PID to download
• INLINECODE21 — Custom output directory (default: ./staticapp/{pid})
• INLINECODE23 — Specify API key
• INLINECODE24 — Output raw JSON response

Example:
CODEBLOCK10

Script Options

CODEBLOCK11

Default Exclusions

The following are automatically excluded from deployment:

• - INLINECODE25
• INLINECODE26, INLINECODE27
• INLINECODE28
• INLINECODE29
• INLINECODE30
• INLINECODE31

Important Notes

✅ What Works

• - Static HTML sites — Any number of .html pages
• CSS & JavaScript — Frontend frameworks, vanilla JS
• Images & Assets — Place in images/ folder or root
• JavaScript files — Place in js/ folder or root
• Built JS Apps — Deploy dist/ or build/ folder after INLINECODE37

❌ What Doesn't Work

• - Node.js Server Apps — No server-side rendering, no Express.js, no API routes
• PHP, Python, Ruby — Static.app only serves static files
• Databases — Use client-side storage or external APIs

JavaScript Apps Workflow

CODEBLOCK12

API Reference

Deploy Site

• - Endpoint: INLINECODE38
• Auth: Bearer token (API key)
• Body: Multipart form with archive (zip file) and optional INLINECODE40

List Sites

• - Endpoint: INLINECODE41
• Auth: Bearer token (API key)
• Headers: INLINECODE42

List Site Files

• - Endpoint: INLINECODE43
• Auth: Bearer token (API key)
• Headers: INLINECODE44

Delete Site

• - Endpoint: INLINECODE45
• Auth: Bearer token (API key)
• Headers: INLINECODE46

Download Site

• - Endpoint: INLINECODE47
• Auth: Bearer token (API key)
• Headers: INLINECODE48
• Response: Returns download URL for the site archive

Dependencies

• - archiver — Zip archive creation
• INLINECODE50 — Multipart form encoding
• INLINECODE51 — HTTP requests
• INLINECODE52 — Zip extraction

Install with: INLINECODE53

Response

On success, the script outputs:
CODEBLOCK13

Workflow

1. 1. Check for STATIC_APP_API_KEY env var or INLINECODE55
2. Create zip archive from source directory (with exclusions)
3. Upload to Static.app API
4. Parse response and output URLs
5. Clean up temporary zip file

Error Handling

• - Missing API key → Clear error with instructions
• Network issues → HTTP error details
• Invalid PID → API error message