New VDF AI Enterprise is now available on AWS Marketplace
VDF AI Agents

Skill versions, imports, and exports

Preserve Skill snapshots, export portable bundles, and understand what VDF imports from Skills and Agent Plugin packages.

Updated Sep 4, 2026 3 min read
On this page

Why version a procedure?

A Skill can change model behaviour without changing the agent’s name or tools. Version snapshots let reviewers connect an observed result to the instructions and resources that were active at that time.

Create a new version when you change:

  • Activation conditions or the description.
  • Decision criteria or workflow order.
  • Required tools or compatibility notes.
  • Supporting references, templates, or eval cases.
  • Output requirements or safety boundaries.

View version history

Open the Skill detail page and select Versions. Each saved snapshot preserves the bundle state available to the runtime.

API and network configurations can request a specific version where supported. The portal’s standard agent binding follows the selected Skill by name unless the interface explicitly exposes a version choice.

Export a Skill ZIP

Use Export from the Skill detail page to download the bundle. The archive preserves SKILL.md and supported files beneath the Skill directory.

Before sharing an export:

  1. Remove credentials and environment-specific secrets.
  2. Review references and assets for customer or personal data.
  3. Confirm licences for included templates or examples.
  4. Validate the archive again in the destination client.

Import a Skill ZIP

Upload the archive from Add Skill. VDF validates paths and metadata before creating the private Skill. Resolve every reported problem before assigning it to an agent.

Export as an Agent Plugin

The Skills page can package selected supported content as an Agent Plugin 1.0.0 archive. Optional MCP configuration can travel with the package when present.

Import from an Agent Plugin

Plugin import extracts supported Agent Skills. Other plugin components can be ignored by this flow, so do not treat a successful Skill import as proof that an entire external plugin has been installed.

Portability checklist

  • Confirm the destination supports the same metadata fields.
  • Map tool names rather than assuming identifiers match.
  • Test automatic activation with the destination model.
  • Check how references, assets, and scripts are handled.
  • Re-run positive, negative, and safety evals.

The directory format is a shared baseline. Runtime compatibility still needs evidence.