Resources & versions
Resources are the individual items inside a repository — for example skills, agent definitions, commands, rules, or packaged assets, depending on how your team uses the hub.
What is a resource?
- Has a type and name (and often a path or logical location).
- Can include metadata and structured content the dashboard and API understand.
- May be associated with files or blobs stored for download or sync.
Versioning
Repositories support version history so you can:
- See what changed over time.
- Restore or compare earlier states (where the UI exposes it).
- Align releases with tags or labels if your workflow uses them.
Exact version features depend on your plan and whether Git integration is enabled for the repository.
Git-backed repositories
When Git is connected (e.g. remote URL or internal Git hosting):
- Pushes and commits may drive or mirror resource state.
- Use branch and default branch settings as documented in the app for that repository.
If Git setup fails during creation, the repository may still exist in the database — check the repository settings or retry Git configuration from the dashboard.
Best practices
- Name consistently — Use clear types and paths so teammates can search and reuse assets.
- Document intent — Add descriptions so marketplace or internal discovery stays understandable.
- Review before publish — For public repos or marketplace listings, review licensing and secrets.
Limits
Storage, number of resources, and API rate limits may apply per subscription. See Billing & limits.