get_asset

Loads an asset’s full content into the agent’s working context. Works for any asset type (context, skill, persona, prompt, system prompt). Unlike pull_asset, this does not write anything to disk. The content lives only in the agent’s conversation.

Input

Parameter	Type	Required	Description
`id`	string	Yes	The asset ID. Get it from list_assets or search_assets.

Example

Prompt:

“Load the ‘code review checklist’ skill from Versuno.”

Tool call chain:

Agent calls search_assets with "code review checklist" and gets back the id def456.
Agent calls get_asset with { "id": "def456" }.

Response:

Asset: Code review checklist (skill, v12)

## Before the review
- Check the PR description has a clear reason
- Skim the diff size. Over 500 lines? Split it.

## During the review
- Focus on logic, not style
- Ask questions before suggesting rewrites
...

The agent now has the skill loaded and can follow its instructions for the rest of the session.

When to use it

You want the agent to follow a specific skill, persona, or system prompt.
You need a context document available for the current task but don’t want to save it to disk.
You’re using an asset as a one-time reference.

When to use `pull_asset` instead

If you want to edit the asset, version-control it, or sync changes back to Versuno, use pull_asset instead. It writes to .versuno/ with frontmatter metadata so you can push_asset later.

Getting Started

Clients

Tools

Reference

Input

Example

When to use it

When to use `pull_asset` instead

See also

​Input

​Example

​When to use it

​When to use pull_asset instead

​See also

Input

Example

When to use it

When to use `pull_asset` instead

See also