create-agent-adapter

Create a standardized blueprint for building VFactory agent adapters.

1|Updated Mar 12, 2026

Search Tags:#testing #ui #architecture #integration #cli #server #adapter

Ready to run

npx skills add https://github.com/XiaoPuOuO/VFactory --skill create-agent-adapter-xiaopuouo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-agent-adapter
Source: https://github.com/XiaoPuOuO/VFactory/tree/main/paperclip-official/AgentSetting/skills/create-agent-adapter
Command: npx skills add https://github.com/XiaoPuOuO/VFactory --skill create-agent-adapter-xiaopuouo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical guide for creating a new VFactory agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

Core Features & Use Cases

This guide explains the architecture, file layout, required exports, server/UI/CLI integration, session handling, and testing patterns to ensure adapters work consistently across runtimes. It covers the registration workflow, and how to structure adapter code to be compatible with the three consumers (server, UI, and CLI).

Quick Start

Create a new adapter package under packages/adapters following the four-exports convention and registries setup.

Frequently Asked Questions about create-agent-adapter

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

FAQPage Schema

How do I build a new VFactory agent adapter for a custom CLI tool?▼

A VFactory agent adapter requires a standardized package under packages/adapters with four core exports, specific module file layouts, metadata exports, session handling, and testing patterns to ensure compatibility across server, UI, and CLI runtimes.

What is the standard module structure for integrating an AI coding agent with server, UI, and CLI?▼

The standard module structure for an agent adapter involves specific file layouts and metadata exports under packages/adapters, establishing registration points and session handling to ensure consistent runtime behavior across server, UI, and CLI environments.

Can I use the VFactory adapter pattern for API-based agents instead of local CLI agents?▼

Yes, the VFactory adapter pattern applies to API-based agents, custom processes, and CLI agents. It standardizes required interfaces and registration workflows derived from existing local agent adapters to ensure broad compatibility.

What testing patterns should I follow when creating a new agent adapter package?▼

When creating an agent adapter package, follow standardized testing patterns that validate compatibility across server, UI, and CLI runtimes, ensuring the module's session handling and registration points function consistently.

Why does my agent adapter need specific registration points and metadata exports?▼

Agent adapters require specific registration points and metadata exports so the three runtime consumers—server, UI, and CLI—can properly discover, load, and interface with the adapter's session handling and functionality.