Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Creek

v2.1.0

Deploy and manage applications on Creek via the Creek CLI. Covers init, deploy, status, projects, deployments, rollback, env vars, custom domains, and dev se...

0· 104· 2 versions· 0 current· 0 all-time· Updated 4w ago· MIT-0
byLawrence Lin@linyiru

Creek CLI — Agent Skill

Creek deploys web apps to Cloudflare Workers with a single command. Auto-detects framework, determines render mode (SPA/SSR/Worker), provisions infrastructure.

Agent Rules

  1. Always use --json for structured output. Auto-enabled in non-TTY / CI.
  2. Follow breadcrumbs in JSON responses — they suggest the next command.
  3. Use --yes to skip confirmation prompts (auto-enabled in non-TTY).
  4. Check ok fieldtrue = success, false = error with error and message fields.

Command Reference

TaskCommand
Authenticatecreek login
Authenticate (CI)creek login --token <KEY>
Check authcreek whoami --json
Init projectcreek init --json
Deploycreek deploy --json
Deploy directorycreek deploy ./dist --json
Deploy from GitHubcreek deploy https://github.com/user/repo --json
Deploy monorepo subdircreek deploy https://github.com/user/repo --path packages/app --json
Deploy democreek deploy --demo --json
Deploy templatecreek deploy --template vite-react
Skip buildcreek deploy --skip-build --json
Check statuscreek status --json
Check sandboxcreek status <SANDBOX_ID> --json
Claim sandboxcreek claim <SANDBOX_ID> --json
List projectscreek projects --json
List deploymentscreek deployments --json
List deployments (other)creek deployments --project <SLUG> --json
Rollbackcreek rollback --json
Rollback to specificcreek rollback <DEPLOYMENT_ID> --json
Set env varcreek env set <KEY> <VALUE> --json
List env varscreek env ls --json
Show env valuescreek env ls --show --json
Remove env varcreek env rm <KEY> --json
Add domaincreek domains add <HOSTNAME> --json
List domainscreek domains ls --json
Activate domaincreek domains activate <HOSTNAME> --json
Remove domaincreek domains rm <HOSTNAME> --json
Dev servercreek dev

Deployment Modes

Authenticated (permanent)

Requires creek login. Deploys persist under the user's account.

creek deploy --json

Sandbox (60-min preview)

No auth required. Temporary preview with claimable URL.

creek deploy --json          # auto-sandbox when not logged in
creek claim <SANDBOX_ID>     # convert to permanent project

CI/CD

CREEK_TOKEN=ck_... creek deploy --yes --json

JSON Output Format

Every command returns structured JSON with breadcrumbs:

{
  "ok": true,
  "url": "https://my-app-team.bycreek.com",
  "project": "my-app",
  "breadcrumbs": [
    { "command": "creek status", "description": "Check deployment status" },
    { "command": "creek deployments --project my-app", "description": "View deployment history" }
  ]
}

On error:

{
  "ok": false,
  "error": "not_authenticated",
  "message": "Not authenticated. Run `creek login` first.",
  "breadcrumbs": [
    { "command": "creek login", "description": "Authenticate interactively" }
  ]
}

Workflow: First Deploy

creek login --json                # 1. Authenticate
creek init --json                 # 2. Create creek.toml (optional)
creek deploy --json               # 3. Deploy

Workflow: Update & Rollback

creek deploy --json               # Deploy new version
creek deployments --json          # View history
creek rollback --json             # Rollback to previous
creek rollback <ID> --json        # Rollback to specific deployment

Workflow: Custom Domain

creek domains add app.example.com --json     # Add domain
# User sets DNS: CNAME app.example.com → cname.creek.dev
creek domains activate app.example.com --json # Activate after DNS
creek domains ls --json                       # Verify status

creek.toml Reference

[project]
name = "my-app"              # Required. Lowercase alphanumeric + hyphens.
framework = "nextjs"         # Optional. Auto-detected from package.json.

[build]
command = "npm run build"    # Build command (default: npm run build)
output = "dist"              # Build output directory
worker = "worker/index.ts"   # Optional: custom Worker entry point

[resources]
d1 = true                   # Cloudflare D1 database   → env.DB
kv = true                   # Cloudflare KV namespace   → env.KV
r2 = true                   # Cloudflare R2 storage     → env.BUCKET
ai = true                   # Cloudflare Workers AI     → env.AI

Supported Frameworks

SPA: vite-react, vite-vue, vite-svelte, vite-solid, static HTML SSR: nextjs, react-router, sveltekit, nuxt, solidstart, tanstack-start

Config Detection Order

  1. creek.toml — explicit Creek config
  2. wrangler.jsonc / wrangler.json / wrangler.toml — existing CF config
  3. package.json — framework auto-detection
  4. index.html — static site

Troubleshooting

ErrorFix
"Not authenticated"creek login or set CREEK_TOKEN
"Invalid API key"creek login to re-authenticate
"No creek.toml found"creek init or cd to project root
"No project found"Deploy from a dir with package.json or index.html
"No supported project found in repo"Use --path for monorepos
Sandbox expiredRedeploy — sandboxes last 60 minutes
Domain stuck "pending"Set CNAME to cname.creek.dev, then creek domains activate
Build failsCheck [build] command in creek.toml

Version tags

latestvk970k3d64hqjqz69498z5nv8c183webq