Install the "nova-app-builder" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/nova-app-builder into .claude/skills/nova-app-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nova-app-builder", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "nova-app-builder" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/nova-app-builder into .agents/skills/nova-app-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nova-app-builder", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "nova-app-builder" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/nova-app-builder into .cursor/skills/nova-app-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nova-app-builder", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "nova-app-builder" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/nova-app-builder into .gemini/skills/nova-app-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nova-app-builder", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "nova-app-builder" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/nova-app-builder into .github/skills/nova-app-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nova-app-builder", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "nova-app-builder" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/nova-app-builder into .opencode/skills/nova-app-builder/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nova-app-builder", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
nova-app-builder
GitHub stars
2.2k
Token cost
~7k tokens
SKILL.md length
2,156 words
Files
13 (incl. scripts, references, assets)
Skills in repo
1,235
Repo updated
First seen
Licence
MIT
At a glance
Build and deploy Nova Platform apps (TEE apps on Sparsity Nova / sparsity.cloud).
Works in 6 steps: Scaffold the project → Write the app logic → Commit & push to Git → …
A user wants to create a Nova app
SKILL.md covers Architecture Overview, Two Development Paths, Prerequisites (collect from… and Full Workflow, plus 6 more sections
Runs Python scripts from its folder; calls curl, python3 and git; reaches github.com and sparsity.cloud; needs GH_TOKEN
What it does
Nova App Builder is an agent skill from LeoYeAI/openclaw-master-skills. Build and deploy Nova Platform apps (TEE apps on Sparsity Nova / sparsity.cloud). Use when a user wants to create a Nova app, write enclave application code, build it into a Docker image, and deploy it to the Nova Platform to get a live running URL. Handles the full lifecycle: scaffold, code, build, push, deploy, verify running. Triggers on requests like 'build me a Nova app', 'deploy to Nova Platform', 'create a TEE app on sparsity.cloud', 'I want to run an enclave app on Nova'.
Its SKILL.md is about 7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 17 other files, including scripts, reference files and assets (for example `_meta.json`, `assets/app-template/enclave/main.py` and `assets/app-template/enclave/odyn.py`).
It sits in DevOps & Cloud, covering Containers. It works with Docker and Python. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
When your agent uses it
A user wants to create a Nova app
Write enclave application code
Build it into a Docker image
Deploy it to the Nova Platform to get a live running URL
Example prompts
“build me a Nova app”
“deploy to Nova Platform”
“create a TEE app on sparsity.cloud”
“/nova-app-builder”
Requirements
Python 3
Docker
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
curl
python3
git
uvicorn
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
sparsity.cloud
odyn.sparsity.cloud
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
GH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nova App Builder loads about 7k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 125 tokens; SKILL.md has 2,156 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~125
When it runs· the whole SKILL.md, loaded when a task matches
~7k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~16k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/nova-app-builder/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
nova-app-builder
description
Build and deploy Nova Platform apps (TEE apps on Sparsity Nova / sparsity.cloud). Use when a user wants to create a Nova app, write enclave application code, build it into a Docker image, and deploy it to the Nova Platform to get a live running URL. Handles the full lifecycle: scaffold, code, build, push, deploy, verify running. Triggers on requests like 'build me a Nova app', 'deploy to Nova Platform', 'create a TEE app on sparsity.cloud', 'I want to run an enclave app on Nova'.
Nova apps run inside AWS Nitro Enclaves, managed by Enclaver (Sparsity edition) and supervised by Odyn (PID 1 inside the enclave). Key concepts:
Enclaver: packages your Docker image into an EIF (Enclave Image File) and manages the enclave lifecycle.
Odyn: supervisor inside the enclave; provides Internal API for signing, attestation, encryption, KMS, S3, and manages networking.
Nova Platform: cloud platform at sparsity.cloud — builds EIFs from Git, runs enclaves, exposes app URLs.
Nova KMS: distributed key management; enclave apps derive keys via /v1/kms/derive.
Nova Python SDK: canonical SDK in enclave/nova_python_sdk/ — import as from nova_python_sdk.odyn import Odyn. Ships in nova-app-template and all examples.
⚠️ enclaver.yaml and nova-build.yaml are generated by Nova Platform — developers never need to write or provide these files. The control plane generates both from app settings before triggering the build workflow. S3 storage and AWS credentials are fully managed by the platform; developers never touch them.
Prerequisites (collect from user before starting)
Ensure skill is up to date before starting:
bash
clawhub update nova-app-builder
Older versions are missing Dockerfile.txt in the template, causing scaffold to fail.
App idea: What does the app do?
Nova account + API key: Sign up at sparsity.cloud → Account → API Keys.
GitHub repo + GitHub PAT: Used only to push your app code to GitHub. Nova Platform then builds from the repo URL. The PAT is not passed to Nova Platform.
git remote set-url origin https://oauth2:${GH_TOKEN}@github.com/<user>/<repo>.git
git push origin main
⚠️ Do NOT ask for Docker registry credentials, AWS S3 credentials, or enclaver.yaml.
Nova Platform handles the Docker build, image registry, and S3/storage provisioning internally.
Developers never touch AWS credentials or write enclaver.yaml — the platform generates it from the advanced field.
The app only calls Internal API endpoints (/v1/s3/*) for storage; Odyn handles the rest.
Port choice: Any port works. Set it via advanced.app_listening_port when creating the app. Must also match EXPOSE in your Dockerfile. No requirement to use 8080.
This generates <output-dir>/<app-name>/ with the following structure:
Note: The template ships as Dockerfile.txt (clawhub cannot distribute extensionless files). scaffold.py automatically renames it to Dockerfile and substitutes the port. No manual action needed.
Alternatively, fork nova-app-template for the full production-ready structure:
nova-app-template/
├── Makefile
├── Dockerfile
├── enclaver.yaml ← reference template only; portal parses listening port from it;
│ platform generates the real enclaver.yaml from app settings
├── enclave/
│ ├── app.py ← entry point (not main.py)
│ ├── routes.py ← FastAPI route handlers
│ ├── config.py ← app business logic config (chain RPCs, contract address, etc.)
│ ├── chain.py ← chain interaction helpers (app-specific ABI, contract reads)
│ ├── tasks.py ← background scheduler (oracle, periodic jobs)
│ ├── nova_python_sdk/ ← canonical Nova SDK (do not modify)
│ │ ├── odyn.py ← identity, attestation, encryption, S3, KMS/app-wallet wrappers
│ │ ├── kms_client.py ← thin client for KMS and app-wallet request handlers
│ │ ├── rpc.py ← shared RPC transport + environment switching
│ │ └── env.py ← IN_ENCLAVE + endpoint resolution helpers
│ └── requirements.txt
├── frontend/ ← React/Next.js UI (served at /frontend)
└── contracts/ ← example on-chain contracts
Edit enclave/main.py (scaffold) or enclave/routes.py (full template). Key patterns:
Minimal FastAPI app:
python
import os, httpx
from fastapi import FastAPI
app = FastAPI()
IN_ENCLAVE = os.getenv("IN_ENCLAVE", "false").lower() == "true"
ODYN_BASE = "http://localhost:18000" if IN_ENCLAVE else "http://odyn.sparsity.cloud:18000"
@app.get("/api/hello")
def hello():
r = httpx.get(f"{ODYN_BASE}/v1/eth/address", timeout=10)
return {"message": "Hello from TEE!", "enclave": r.json()["address"]}
⚠️ IN_ENCLAVE is NOT injected automatically by Enclaver — it's an app-level convention. Set it in your Dockerfile as ENV IN_ENCLAVE=false for local dev; the platform sets it true in production.
Using the Nova Python SDK (recommended for full template; copy from nova-app-template):
Business chain: Ethereum Mainnet (1) — your business logic
Helios light-client RPC runs locally at http://127.0.0.1:18545 (Base Sepolia) and http://127.0.0.1:18546 (Mainnet).
⚠️ Helios RPC ports must be decided before creating the app — they are set in advanced.helios_chains[].local_rpc_port and locked at creation time. Choose values carefully up front.
Rules for enclave code:
Odyn calls (localhost): requests or httpx both work — Odyn is local.
External outbound HTTP: must use httpx (proxy-aware). Never use requests or urllib for external calls — they may bypass the egress proxy.
Persistent state → use /v1/s3/* endpoints (or odyn.s3_put()); the enclave filesystem is ephemeral.
Secrets → derive via KMS (/v1/kms/derive); never from env vars or hardcoded.
Test locally: IN_ENCLAVE=false python3 app.py (scaffold: uvicorn main:app --port <port>). Odyn calls hit the public mock.
/.well-known/attestation routing note: In production Nova deployments, this endpoint is handled by Caddy routing to the Aux API (port 18001) — not your app code. Some examples implement it in app code as a local dev shim. Don't ship that in production.
Step 3 — Commit & push to Git
Your repo only needs Dockerfile + app code. No local Docker build needed — Nova Platform builds from your Git repo directly.
KMS integration is fully handled by the platform — just set enable_decentralized_kms: true (and optionally enable_app_wallet: true) in advanced when creating the app. No contract addresses, app IDs, or manual KMS config needed in your code.
bash
git add .
git commit -m "Initial Nova app"
git push origin main
Step 4 — Deploy to Nova Platform
The deployment is a 3-step process: Create App → Trigger Build → Create Deployment.
Via Portal (recommended for first-time)
Portal flow (works for both scaffold and full template):
The repo URL is stored on the app record and used for all subsequent builds — you don't provide it again at build time.
In the App page → Versions → + New Version:
Git Ref: main (or tag / commit SHA)
Version: e.g. 1.0.0
Submit
Wait for build status → success (platform builds Docker image → EIF → generates PCRs and build-attestation.json signed with Sigstore/cosign)
In Versions, find the successful version → Deploy this version:
Select Region
Select Tier: standard or performance
Submit
Poll until deployment state → running → copy the App URL (hostname from app detail)
The deploy modal has no environment-variable input — no env vars or credentials needed.
Via API (scripted)
The script will ask interactively whether to run on-chain registration after the app is live. Use --onchain to always run it, --no-onchain to always skip.
BASE="https://sparsity.cloud/api"
TOKEN="<your-api-key>"
REPO="https://github.com/you/my-app"
# 1. Create app — 'advanced' is the only config field needed
SQID=$(curl -sX POST "$BASE/apps" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{
"name":"my-app",
"repo_url":"'"$REPO"'",
"description":"optional description",
"metadata_uri":"",
"app_contract_addr":"",
"advanced":{
"directory":"/",
"app_listening_port":8080,
"egress_allow":["**"],
"enable_decentralized_kms":false,
"enable_persistent_storage":false,
"enable_s3_storage":false,
"enable_s3_kms_encryption":false,
"enable_ipfs_storage":false,
"enable_walrus_storage":false,
"enable_app_wallet":false,
"enable_helios_rpc":false
}
}' \
| python3 -c "import sys,json; print(json.load(sys.stdin)['sqid'])")
echo "App sqid: $SQID"
# 2. Create new version (build) — repo URL comes from app record, not repeated here
BUILD_ID=$(curl -sX POST "$BASE/apps/$SQID/builds" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"git_ref":"main","version":"1.0.0"}' \
| python3 -c "import sys,json; print(json.load(sys.stdin)['id'])")
echo "Build ID: $BUILD_ID"
# 3. Poll build
while true; do
STATUS=$(curl -s "$BASE/builds/$BUILD_ID/status" \
-H "Authorization: Bearer $TOKEN" \
| python3 -c "import sys,json; print(json.load(sys.stdin).get('status',''))")
echo "Build: $STATUS"
[ "$STATUS" = "success" ] && break
[ "$STATUS" = "failed" ] && echo "Build failed!" && exit 1
sleep 15
done
# 4. Deploy this version — specify region and tier
# region options: ap-south-1 (default), us-east-1, us-west-1, eu-west-1
# tier options: standard (2vCPU/5GiB), performance (6vCPU/13GiB)
DEPLOY_ID=$(curl -sX POST "$BASE/apps/$SQID/deployments" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{\"build_id\":$BUILD_ID,\"region\":\"ap-south-1\",\"tier\":\"standard\"}" \
| python3 -c "import sys,json; print(json.load(sys.stdin)['id'])")
echo "Deployment ID: $DEPLOY_ID"
# 5. Poll deployment
while true; do
RESP=$(curl -s "$BASE/deployments/$DEPLOY_ID/status" -H "Authorization: Bearer $TOKEN")
STATE=$(echo $RESP | python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('deployment_state',''))")
echo "Deployment state: $STATE"
[ "$STATE" = "running" ] && break
[ "$STATE" = "failed" ] && echo "Deploy failed!" && exit 1
sleep 15
done
# 6. Get app URL (hostname from detail, or use unified status)
curl -s "$BASE/apps/$SQID/detail" -H "Authorization: Bearer $TOKEN" \
| python3 -c "import sys,json; d=json.load(sys.stdin); print(d['app'].get('hostname',''))"
# Tip: GET /api/apps/{sqid}/status gives the full lifecycle in one call:
# build_status, deployment_state, proof_status, onchain_instance_id, etc.
Step 5 — Verify the live app
bash
# Health check
curl https://<hostname>/
# Hello endpoint (returns enclave address + signature)
curl https://<hostname>/api/hello
# Attestation (proves it's a real Nitro Enclave) — POST, returns binary CBOR
# In production, /.well-known/attestation is Caddy → Aux API; not app code
curl -sX POST https://<hostname>/.well-known/attestation --output attestation.bin
Note: /api/app-wallet is only available if you forked nova-app-template. The scaffold template includes /api/hello instead.
Step 6 — On-Chain Registration (optional but important for trust)
After the app is running, register it on-chain to establish verifiable trust.
Using the script (recommended):
bash
python3 scripts/nova_deploy.py ... --onchain
The script will automatically execute steps 6a–6d and poll until complete.
Manually via API — 4-step sequence:
bash
# 6a. Create app on-chain
curl -sX POST "$BASE/apps/$SQID/create-onchain" \
-H "Authorization: Bearer $TOKEN"
# Poll: GET /api/apps/{sqid}/status → onchain_app_id is set when done
# 6b. Enroll build version on-chain (PCR measurements → trusted code fingerprint)
curl -sX POST "$BASE/apps/$SQID/builds/$BUILD_ID/enroll" \
-H "Authorization: Bearer $TOKEN"
# Poll enrollment via build status endpoint
while true; do
ENROLLED=$(curl -s "$BASE/builds/$BUILD_ID/status" \
-H "Authorization: Bearer $TOKEN" \
| python3 -c "import sys,json; d=json.load(sys.stdin); print(d.get('is_enrolled',''))")
echo "Enrolled: $ENROLLED"
[ "$ENROLLED" = "True" ] && break
sleep 10
done
# 6c. Generate ZK proof (SP1-based)
curl -sX POST "$BASE/zkproof/generate" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d "{\"deployment_id\": $DEPLOY_ID}"
# Poll proof via deployment status endpoint (or /zkproof/status/{deployment_id})
while true; do
PROOF=$(curl -s "$BASE/deployments/$DEPLOY_ID/status" \
-H "Authorization: Bearer $TOKEN" \
| python3 -c "import sys,json; print(json.load(sys.stdin).get('proof_status',''))")
echo "Proof status: $PROOF"
[ "$PROOF" = "proved" ] && break
[ "$PROOF" = "failed" ] && echo "Proof failed!" && exit 1
sleep 30
done
# 6d. Register instance on-chain (manual — auto-registration has been removed)
curl -sX POST "$BASE/apps/$SQID/instance/register" \
-H "Authorization: Bearer $TOKEN"
# Poll: GET /api/deployments/{id}/status → onchain_instance_id is set when done
# Or use unified: GET /api/apps/{sqid}/status → latest_onchain_instance_id
What each step does:
Create app on-chain: Registers your app in the Nova App Registry contract (Base Sepolia)
Enroll version: Records the EIF's PCR measurements on-chain — the trusted code fingerprint
Generate ZK proof: Platform generates an SP1 zero-knowledge proof from the enclave's Nitro attestation
Register instance: Verifies the ZK proof on-chain and links the live instance to its enrolled version
After registration, anyone can verify on-chain that this running instance matches the audited build.
Show full SKILL.md (933 more words)Show less
Odyn Internal API Reference
All endpoints are on http://127.0.0.1:18000 (Primary API — inside enclave only, NOT publicly exposed in production).
Always-available endpoints:
Endpoint
Method
Description
/v1/eth/address
GET
Enclave Ethereum address + public key
/v1/eth/sign
POST
EIP-191 personal-sign (optionally with attestation)
/v1/eth/sign-tx
POST
Sign EIP-1559 transactions
/v1/random
GET
32 bytes from NSM-backed randomness
/v1/attestation
POST
Raw CBOR attestation bytes (not JSON)
/v1/encryption/public_key
GET
Enclave P-384 public key
/v1/encryption/encrypt
POST
Encrypt response to a client
/v1/encryption/decrypt
POST
Decrypt client payloads
Feature-gated endpoints (set in advanced at app creation):
Endpoint Group
Gate
Description
/v1/s3/*
enable_s3_storage: true
Base64 object storage backed by S3
/v1/kms/derive
enable_decentralized_kms: true
Deterministic key derivation
/v1/kms/kv/put|get|delete
enable_decentralized_kms: true
KMS-backed KV store with optional TTL
/v1/app-wallet/address
enable_app_wallet: true
App-specific wallet address
/v1/app-wallet/sign
enable_app_wallet: true
EIP-191 message signing via app wallet
/v1/app-wallet/sign-tx
enable_app_wallet: true
EIP-1559 transaction signing via app wallet
Port exposure in production:
Runtime publishes exactly two ports: host app port → enclave app port and host attestation port → enclave Aux API port 18001
/.well-known/attestation* is routed by Caddy to the host attestation port → Aux API (18001)
Primary API (18000) is NOT exposed publicly for normal production apps
Odyn mock service (local development):
Primary API: http://odyn.sparsity.cloud:18000
Aux API: http://odyn.sparsity.cloud:18001
Helios RPC presets: http://odyn.sparsity.cloud:18545 through :18553
Key Notes
advanced is REQUIRED at app creation. Omitting it will cause the build to fail. Only advanced exists — the old enclaver field has been removed from the API.
Your repo only needs Dockerfile + app code. The platform handles everything else at build time.
App ID format: sqid (string like abc123) — use in all URL paths, not the integer id.
Port: Set via advanced.app_listening_port. Must also match EXPOSE in Dockerfile. The enclaver.yaml in the template repo is a reference; portal reads the listening port from it.
Repo URL is set once at app creation — not repeated at build time. Build only needs git_ref + version.
Deploy requires region + tier: regions are ap-south-1 (default), us-east-1, us-west-1, eu-west-1. tier is "standard" (2 vCPU/5 GiB) or "performance" (6 vCPU/13 GiB). No env var injection in deploy.
Helios RPC: Use the canonical port mapping in references/nova-api.md — ports are fixed and locked at app creation.
KMS/S3 fully managed by platform — no AWS credentials, no enclaver.yaml authoring needed.
No Docker push: Platform builds from Git.
On-chain steps (create-onchain → enroll → ZK proof → register) are required for public verifiability, but optional for a functional running app.
Instance registration is now manual — auto-registration has been removed. Use POST /api/apps/{app_sqid}/instance/register after proof is proved.
Portal helper APIs (clone-repo, get-enclaver-config) are used by the portal UI to auto-fill the listening port from enclaver.yaml when you enter a repo URL. Not needed for direct API usage.
Build provenance: Builds produce a build-attestation.json with PCR0/PCR1/PCR2, source repo, commit, GitHub run metadata — signed with Sigstore/cosign and stored off-chain.
IN_ENCLAVE is not injected by Enclaver — set ENV IN_ENCLAVE=false in Dockerfile for local dev; production sets it true.
Common Issues
Symptom
Fix
Dockerfile missing after scaffold
Run clawhub update nova-app-builder then re-scaffold. The template ships as Dockerfile.txt and scaffold renames it to Dockerfile automatically.
App expects enclaver.yaml or old config
enclaver.yaml is always generated by Nova Platform — developers never provide it. The advanced field at app creation drives all platform-level config. Only enclave/config.py (app business logic) needs developer attention when using the full template.
API endpoint console.sparsity.cloud not resolving
Old version of nova_deploy.py. Run clawhub update nova-app-builder. Correct endpoint is https://sparsity.cloud/api.
from odyn import Odyn fails
Old import path. New SDK is at nova_python_sdk/. Use from nova_python_sdk.odyn import Odyn.
Build stuck in pending
Check GitHub Actions in nova build repo; may be queued
Build failed
Check error_message in build response; usually Dockerfile issue
Deploy API returns 401
Regenerate API key at sparsity.cloud
App stuck in provisioning >10 min
Check app logs via GET /api/apps/{sqid}/detail
httpx request fails inside enclave
Add domain to advanced.egress_allow. Note: "**" matches domains only — add "0.0.0.0/0" for direct IP connections
Direct IP connection blocked
"**" does NOT cover IPs. Add "0.0.0.0/0" (IPv4) and/or "::/0" (IPv6) to egress_allow
S3 fails
Ensure 169.254.169.254 and S3 endpoint are in egress allow list
/v1/kms/* returns 400
Ensure enable_decentralized_kms: true and enable_helios_rpc: true in advanced at app creation
App Wallet unavailable
Ensure enable_app_wallet: true in advanced at app creation
Proxy not respected for external calls
Use httpx for external HTTP calls (proxy-aware). requests/urllib may bypass the egress proxy. Note: requests is fine for internal Odyn calls (localhost).
Health check returns 502
App is starting; wait for enclave to fully boot
ZK proof stuck
Check GET /api/zkproof/status/{deployment_id} for details
/.well-known/attestation returning wrong format in prod
In production, this is Caddy → Aux API routing — not app code. Remove app-side shim for production builds.
Reference Files
references/odyn-api.md — Full Odyn Internal API (signing, encryption, S3, KMS, App Wallet, attestation)
references/nova-api.md — Nova Platform REST API (full endpoint reference)
Nova Python SDK: The canonical SDK lives in enclave/nova_python_sdk/ in both nova-app-template and all examples. Do not modify SDK files — copy the whole directory into your project.
Nova App Builder next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Nova App Builder compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Nova App Builder this skillLeoYeAI/openclaw-master-skills
This skill should be used when the user asks how to configure, run, automate, integrate, or troubleshoot minimega (VMs, namespaces, VLANs, clusters, miniccc, miniweb, command socket or Python API…
This skill should be used when the user mentions Unraid, asks to check server health, monitor array or disk status, list or restart Docker containers, start or stop VMs, read system logs, check…
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Build and deploy Nova Platform apps (TEE apps on Sparsity Nova / sparsity.cloud). Nova App Builder is an agent skill from LeoYeAI/openclaw-master-skills.cloud).
When should I use Nova App Builder?
Nova App Builder fits situations like: A user wants to create a Nova app; write enclave application code; build it into a Docker image; deploy it to the Nova Platform to get a live running URL.
How do I install Nova App Builder in Claude Code?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a claude-code`. Or copy the skill folder (skills/nova-app-builder in LeoYeAI/openclaw-master-skills) into .claude/skills/nova-app-builder in your project. Claude Code loads it when a task matches its description.
How do I install Nova App Builder in Codex?
Run `npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a codex`. Or copy the skill folder (skills/nova-app-builder in LeoYeAI/openclaw-master-skills) into .agents/skills/nova-app-builder in your project. Codex loads it when a task matches its description.
Can I use Nova App Builder in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill nova-app-builder -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nova-app-builder, .gemini/skills/nova-app-builder, .github/skills/nova-app-builder and .opencode/skills/nova-app-builder in your project.
What does Nova App Builder need to run?
Going by SKILL.md and its folder, Nova App Builder needs Python for the scripts in its folder, the command-line tools its instructions call (curl, python3, git and uvicorn) and credentials named GH_TOKEN. Our summary lists: Python 3; Docker.
Does Nova App Builder access the network?
SKILL.md names 3 domains. In commands or code: github.com, sparsity.cloud and odyn.sparsity.cloud; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Is Nova App Builder safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Nova App Builder use?
Nova App Builder is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nova App Builder use?
About 7k tokens (SKILL.md is roughly 28k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.7k tokens, read only when the agent opens those files.
What are the alternatives to Nova App Builder?
Skills that share tags, products or a category with Nova App Builder: Minimega (sandia-minimega/minimega, 160 stars), Unraid (dinglebear-ai/unraid, 135 stars), Generate Nemo Gym Env (adithya-s-k/FineEnvs, 456 stars) and Cosmos3 Env Troubleshoot (NVIDIA/cosmos-framework, 559 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nova App Builder?
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.