Sharing Templates
Once you have customized your workspace — tuned the personality, installed the right skills, configured integrations, and dialed in the heartbeat cycle — you can share it as a template for others to deploy with one click. Templates are Hubify’s viral mechanism. A great template spreads because it solves a real workflow problem and saves others hours of configuration.How Template Sharing Works
You can publish templates today at hubify.com/templates/publish using a 4-step wizard that guides you through packaging, metadata, and submission.Fork and customize
Start from any existing template (built-in or community). Deploy it to your workspace and make it yours — edit the SOUL.md, add skills, configure integrations, write a heartbeat checklist that actually works for your use case.
Prepare for publishing
Clean up your workspace for public consumption:
- Write a clear, descriptive SOUL.md that others can understand and adapt
- Document which skills are included and why
- Write a template description and pick relevant tags
- Remove any personal data, API keys, or private references from shared files
Submit for review
Submit your template via CLI or dashboard:This packages your template manifest (HUB.yaml structure, SOUL.md, skills list, integration types) and sends it to the Hubify review queue.
Review process
The Hubify team reviews submitted templates for:
- Quality: Is the SOUL.md well-written? Are skills relevant to the stated use case?
- Safety: No leaked credentials, API keys, or personal data in shared files
- Completeness: Does the template include a description, tags, and working integrations?
- Originality: Does it solve a workflow problem that existing templates don’t cover?
What Gets Shared
When you publish a template, the following components are included:| Component | Shared | Details |
|---|---|---|
| HUB.yaml structure | Yes | Workspace configuration, model routing, mode settings — without your personal hub ID or credentials |
| SOUL.md personality | Yes | The agent personality you wrote |
| Skills list | Yes | References to skills from the registry (the skill IDs and versions, not the skill files themselves) |
| Dashboard configuration | Yes | Which pages and sections the dashboard includes |
| Integration list | Yes | Which integration types are configured (e.g., “telegram”, “github”) — not your credentials |
| Heartbeat checklist | Yes | Your HEARTBEAT.md template |
| Description and tags | Yes | What you write to describe the template |
| AGENTS.md instructions | Yes | Operational rules for agents |
What Does NOT Get Shared
Your private data is never included in a published template.| Component | Shared | Why |
|---|---|---|
| Personal data | No | Memory files, daily logs, personal notes are stripped |
| API keys or credentials | No | Vault entries are never included in template exports |
| Private files | No | Anything in projects/ or user-created directories outside the reserved structure |
| Chat history | No | Conversation logs stay in your workspace |
| Memory directory | No | Your memory/ files are personal and never exported |
| Learnings | No | Your learnings/ files stay private unless you opt them into the global intelligence layer separately |
| Vault entries | No | Encrypted credentials never leave your workspace |
The template export process automatically strips personal data and validates that no secrets are included before submission. If it detects anything that looks like an API key, token, or credential in your SOUL.md or AGENTS.md, the submission will be blocked until you remove it.
Template Quality Guidelines
Published templates should meet these quality standards:SOUL.md
- Clear description of who the agent is and what it does
- Specific tone and priority instructions (not generic “be helpful” filler)
- Written so someone unfamiliar with your workflow can understand the agent’s role
Skills
- Every included skill should serve a clear purpose for the template’s use case
- Document why each skill is included (in the template description, not in the skill itself)
- Avoid including skills that are tangential to the core workflow
Integrations
- At least the primary integrations should be functional (even if in draft-only mode)
- Document which integrations are required versus optional
- Indicate which integrations default to draft-only mode and why
Description and Tags
- Write a 2-3 sentence description that explains the template’s purpose and target audience
- Pick accurate category tags (productivity, development, research, agency, fitness, etc.)
- Include a “best for” line describing the ideal user
General
- No offensive, harmful, or misleading content
- No instructions that violate platform terms of service
- No skills or automations that could be used for spam or abuse
Metrics and Reputation
Template authors get attribution and metrics for their published templates.| Metric | Description |
|---|---|
| Install count | How many users have deployed your template |
| Fork count | How many users have forked your template to create their own variant |
| Author attribution | Your username appears on the template page as the author |
Future Metrics
The following metrics are planned but not yet available:- Ratings and reviews from users who deployed the template
- Active workspace count showing how many workspaces are currently running the template
- Revenue share for Pro-tier installs of community templates
Template Publishing Checklist
Before submitting your template, verify:- SOUL.md is well-written and specific to the use case
- AGENTS.md contains clear operational rules
- All included skills are relevant and documented
- No API keys, tokens, or personal credentials in any shared file
- No personal data in SOUL.md, AGENTS.md, or HEARTBEAT.md
- Template description is clear and accurate
- Tags and categories are relevant
- At least one integration is configured (even in draft-only mode)
- HEARTBEAT.md contains a useful proactive checklist
Next Steps
Customizing Templates
Edit personality, skills, and guardrails before publishing
Templates Overview
Browse built-in templates and see what each includes
Multiple Workspaces
Run different templates for different use cases
Guardrails & Safety
Configure safety settings before sharing