vault-pool-setup

Create policy-bound vaults on Operator XLayer and map pool concepts to vault architectures.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/dubzn/operator-xlayer --skill vault-pool-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-pool-setup
Source: https://github.com/dubzn/operator-xlayer/tree/main/.agents/skills/vault-pool-setup
Command: npx skills add https://github.com/dubzn/operator-xlayer --skill vault-pool-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many users refer to a “pool” when they actually need a policy‑bound execution vault on Operator XLayer, and they need clear guidance on vault creation, controller authorization, and whether the existing operator API meets their use case.

Core Features & Use Cases

  • Vault mapping: Distinguishes LP/AMM pools from OperatorVaults and directs requests appropriately.
  • API suitability assessment: Determines if the current single‑vault backend is sufficient or if a multi‑vault architecture is required.
  • Step‑by‑step setup: Provides detailed instructions to create a vault via VaultFactory, configure policies, fund the vault, and configure both backend and agent for single‑ or multi‑vault deployments.

Quick Start

Ask the skill to map “pool” to a vault, evaluate the current API, and receive the full setup workflow for a single‑vault deployment.

Frequently Asked Questions about vault-pool-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a policy-bound vault on Operator XLayer?

To set up a policy-bound vault on Operator XLayer, deploy an on-chain VaultFactory contract, configure execution policies, fund the vault, and then set up your backend and agent for single-vault or multi-vault topology.

What is the difference between an LP pool and an Operator Vault?

An LP pool refers to AMM liquidity pools, whereas an Operator Vault is a policy-bound execution vault on XLayer. The skill maps user-requested pool concepts to the correct vault architecture and directs setup accordingly.

Does the current Operator XLayer API support multi-vault backends?

The current Operator XLayer API uses a single-vault backend. The skill assesses whether this single-vault architecture is sufficient for your use case or if you need to implement a multi-vault backend topology.

How do I authorize a controller for an XLayer vault?

Controller authorization for an XLayer vault is configured during the policy setup phase after deploying the VaultFactory, ensuring the agent or backend has correct execution permissions bound to the vault.

When should I choose a multi-vault architecture over a single-vault setup?

Choose a multi-vault architecture when the single-vault backend cannot meet your isolation or scaling requirements. The skill evaluates your API needs and provides the appropriate topology setup workflow.