From zeabur
Backs up Zeabur templates from URLs like zeabur.com/templates/XXXXXX to local git repos using curl, standardized naming, and commit messages.
npx claudepluginhub zeabur/agent-skills --plugin zeaburThis skill uses the workspace's default tool permissions.
> **Always use `npx zeabur@latest` to invoke Zeabur CLI.** Never use `zeabur` directly or any other installation method. If `npx` is not available, install Node.js first.
Publishes new Zeabur templates or updates existing ones to the marketplace using `npx zeabur@latest` CLI commands for create, update, delete, and verification.
Deploys apps to Render by analyzing codebases, generating render.yaml blueprints, and providing dashboard deeplinks. For Git-backed services, Docker images, databases, and cron jobs.
Deploys built projects to platforms like Vercel, Cloudflare Workers, Supabase. Detects CLI tools, reads stack YAML for config, sets up DB/env, pushes code, verifies live status.
Share bugs, ideas, or general feedback.
Always use
npx zeabur@latestto invoke Zeabur CLI. Never usezeaburdirectly or any other installation method. Ifnpxis not available, install Node.js first.
Backup an online Zeabur template to the local git repository with standardized naming.
https://zeabur.com/templates/85IQXQ)The backup repository path depends on your setup. Look for a zeabur-template directory in the user's workspace, or ask the user where to save templates. A common default:
~/Documents/zeabur/zeabur-template/
{service-name}/zeabur-template-{service-name}-{TEMPLATE_CODE}.yaml
Examples:
elasticsearch-kibana/zeabur-template-elasticsearch-kibana-85IQXQ.yamldify/zeabur-template-dify-1D4DOW.yamlpostiz/zeabur-template-postiz-v2.12-X2L3BE.yamlZeabur templates can be directly downloaded by appending .yaml to the template URL:
https://zeabur.com/templates/{TEMPLATE_CODE}.yaml
Example:
https://zeabur.com/templates/1D4DOWhttps://zeabur.com/templates/1D4DOW.yamlUse curl to download:
curl -sL https://zeabur.com/templates/{TEMPLATE_CODE}.yaml -o output.yaml
For template YAML reference and editing, use the zeabur-template skill.
URL format: https://zeabur.com/templates/{TEMPLATE_CODE}
Example: https://zeabur.com/templates/85IQXQ → Code is 85IQXQ
# Download YAML
curl -sL https://zeabur.com/templates/{TEMPLATE_CODE}.yaml -o /tmp/template.yaml
# Extract template name from YAML metadata.name field
grep -A1 'metadata:' /tmp/template.yaml | grep 'name:' | head -1
elasticsearch-kibanaREPO=~/Documents/zeabur/zeabur-template # adjust to your actual path
# Create directory
mkdir -p $REPO/{service-name}
# Move YAML with naming pattern
mv /tmp/template.yaml $REPO/{service-name}/zeabur-template-{service-name}-{TEMPLATE_CODE}.yaml
cd $REPO
git add {service-name}/
git commit -m "feat({service-name}): add {Template Name} template"
git push
| Step | Action |
|---|---|
| 1 | Extract template code from URL |
| 2 | Download YAML via curl -sL .../{CODE}.yaml |
| 3 | Read template name from YAML metadata.name |
| 4 | Derive kebab-case service name |
| 5 | Save to {service-name}/zeabur-template-{service-name}-{CODE}.yaml |
| 6 | Git commit with conventional format |
| 7 | Push if user requests |
| Issue | Solution |
|---|---|
| curl returns HTML instead of YAML | Verify the template code is correct |
| Template name has special chars | Use simple kebab-case for directory |
| Already exists | Compare with existing file, update if needed |