> ## 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.

# list_assets

> List Versuno assets filtered by type. Returns metadata only.

Returns a list of your Versuno assets with metadata only. No content is loaded into the agent's context. Use this to discover what's available before loading specific assets with [get\_asset](/mcp/tools/get-asset) or [pull\_asset](/mcp/tools/pull-asset).

## Input

| Parameter | Type   | Required | Description                                                                                                |
| --------- | ------ | -------- | ---------------------------------------------------------------------------------------------------------- |
| `type`    | enum   | No       | Filter by asset type: `context`, `skill`, `persona`, `prompt`, or `system_prompt`. Omit to list all types. |
| `limit`   | number | No       | Max results to return. Default 20, max 50.                                                                 |

## Example

**Prompt:**

> *"List my Versuno skill assets."*

**Tool call:**

```json theme={null}
{
  "type": "skill",
  "limit": 20
}
```

**Response:**

```
Found 3 skill assets:

- abc123  "Bug triage" (v4, updated 2 days ago)
- def456  "Code review checklist" (v12, updated yesterday)
- ghi789  "Changelog generator" (v2, updated last week)
```

## When to use it

* The agent needs to see what assets exist before deciding which to load.
* You want the agent to summarize your library without reading every asset.
* You're debugging a sync issue and want to confirm an asset exists in the cloud.

## See also

* [search\_assets](/mcp/tools/search-assets) — full-text search when you know what you're looking for.
* [get\_asset](/mcp/tools/get-asset) — load a specific asset's content.
* [CLI: versuno prompts assets list](/cli/assets-list) — equivalent in the CLI.