skills/sher-deploy/SKILL.md
Deploy frontend projects to instant preview URLs using sher. After building a project, run sher link to get a live, shareable URL in seconds.
npx skillsauth add sherdotsh/sher sher-deployInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
sher is a CLI that builds your frontend project, uploads it, and returns a live preview URL. One command. No accounts. No config.
Use it after you've built or scaffolded a frontend project and the user wants to see it live.
Global (recommended for agents):
npm i -g shersh
Or one-off with npx:
npx shersh link
From the project root:
sher link
That's it. sher auto-detects the framework, runs the build, uploads the output, and returns a URL.
| Flag | Description |
|------|-------------|
| --dir <path> | Upload a specific directory (skips framework detection) |
| --ttl <hours> | Set link expiry in hours (default: 24) |
| --no-build | Skip the build step (use if already built) |
| --pass [password] | Password-protect the preview (Pro only) |
# Standard deploy
sher link
# Deploy a pre-built project
sher link --no-build
# Deploy a specific output directory
sher link --dir ./dist
# Short-lived link (2 hours)
sher link --ttl 2
The CLI prints the live URL to stdout in this format:
https://a8xk2m1p.sher.sh (copied)
expires 2/19/2026, 11:00 AM
The URL always matches the pattern https://[a-z0-9]{8}.sher.sh. Extract it with:
https://[a-z0-9]{8}\.sher\.sh
The URL is also automatically copied to the clipboard.
Present the URL to the user:
Your preview is live at https://a8xk2m1p.sher.sh
If you set a --ttl, mention when it expires. If using --pass, share the password too.
sher auto-detects and builds:
dist/out/dist/build/dist/, build/, or out/--dir . to upload directlyIf sher link fails:
build script in package.json, or use --dir to point to pre-built outputdist/, build/, or out/, or specify --dirdevelopment
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.