- Home
- Skills
- Ridemountainpig
- Zeabur Template Skill
- Zeabur Template
zeabur-template_skill
1
GitHub Stars
1
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill ridemountainpig/zeabur-template-skill --skill zeabur-template- SKILL.md2.1 KB
Overview
This skill provides expert guidance for creating, configuring, and optimizing Zeabur service templates. It focuses on standardization, security, observability, and required internationalization for public templates. Use it to validate templates against Zeabur schema and best practices before publishing.
How this skill works
The skill inspects template structure, environment variable usage, resource declarations, and service relationships. It checks for required schema header, secret handling (use of ${PASSWORD}), expose/read-only flags, domain bindings, and valid icon/cover URLs. It also validates that public templates include localization keys for en-US, zh-TW, and zh-CN.
When to use it
- When creating a new Zeabur template from scratch or migrating from Docker Compose.
- When configuring environment variables, secrets, and inter-service exposes.
- Before publishing a public template to ensure internationalization and security.
- When validating service icons, domain bindings, and resource constraints.
- While troubleshooting runtime issues related to template configuration or dependencies.
Best practices
- Start the file with the Zeabur schema header: # yaml-language-server: $schema=https://schema.zeabur.app/template.json.
- Never hardcode credentials; use ${PASSWORD} for passwords and mark system vars readonly when appropriate.
- Set expose: true for variables other services need and readonly: true for system-generated values.
- Provide clear icons, coverImage URLs, and valid public links to improve observability and UX.
- Ensure all public templates include en-US, zh-TW, and zh-CN localization entries.
- Follow strict naming conventions and documented file structure to keep templates consistent.
Example use cases
- Converting a multi-service Docker Compose app to a Zeabur template with proper volumes and service dependencies.
- Auditing a template to ensure no secrets are exposed or hardcoded in environment variables.
- Adding domain binding to a web service by declaring type: DOMAIN variables and corresponding domainKey in services.
- Preparing a public template by adding localized descriptions and verifying icon URLs.
- Optimizing a template for production by setting resource limits and validating service health checks.
FAQ
Always use ${PASSWORD} placeholders for passwords and avoid embedding credentials directly in the template.
Which languages are required for public templates?
Public templates must include localization for en-US, zh-TW, and zh-CN to meet internationalization requirements.