> ## Documentation Index
> Fetch the complete documentation index at: https://docs.versuno.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# get_asset

> Fetch a Versuno asset's full content and load it into the agent's context.

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](/mcp/tools/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](/mcp/tools/list-assets) or [search\_assets](/mcp/tools/search-assets). |

## Example

**Prompt:**

> *"Load the 'code review checklist' skill from Versuno."*

**Tool call chain:**

1. Agent calls `search_assets` with `"code review checklist"` and gets back the id `def456`.
2. 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](/mcp/tools/pull-asset) instead. It writes to `.versuno/` with frontmatter metadata so you can [push\_asset](/mcp/tools/push-asset) later.

## See also

* [pull\_asset](/mcp/tools/pull-asset) — save the asset to disk for editing.
* [CLI: versuno prompts assets get](/cli/assets-get) — equivalent in the CLI.