Agent assets overview
When Prompts and Skills are embedded in application code, every change requires a full redeployment. Agent assets let you manage Prompts and Skills independently from code, with built-in version control and multi-role collaboration, so you can iterate faster and track the impact of each change.
Features
Decouple from code: Publish new Prompt and Skill versions directly on AgentLoop without redeploying your application.
Data-driven evaluation: Run regression tests against versioned Prompts and Skills and compare results across iterations.
Multi-role collaboration: Designers, operations staff, product managers, and engineers contribute to the same assets. Every change is tracked and attributable.
Version-level metrics: Compare latency, token cost, and evaluation scores across Prompt and Skill versions.
Core concepts
Asset properties
Each agent asset (Prompt or Skill) has the following properties:
| Property | Description |
|---|---|
| Name | A unique identifier within the namespace. |
| Description | A summary of what the asset does and when to use it. |
| Created time | The timestamp when the asset was created. |
| Versions | Each asset contains one or more versions. For details, see VersionInfo. |
VersionInfo
Each version of an asset includes the following metadata:
| Property | Description |
|---|---|
| Version number | The version identifier. We recommend x.y.z (semantic versioning), but custom formats are also supported. |
| Status | The current stage of the version. Valid values: Draft (editable, still in progress) and Published (read-only, released for use). |
| Updated time | The timestamp of the last modification. |
| Changelog | A record of what was modified and why. |
Version pointers
Version pointers let you reference a specific version by a logical name rather than a version number. AgentLoop provides two types:
latest: Automatically tracks the most recently published version. When you publish a new version, the latest pointer updates to point to it.
Labels: Custom tags that you assign to a specific version, such as
Daily,Stable,Beta, orProduction. Use labels for canary releases and environment isolation. Each label points to exactly one version at a time.