create-agent-adapter

Create a Paperclip agent adapter package with server, UI, and CLI modules.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Mothership-Foundry/foundry-dashboard --skill create-agent-adapter-mothership-foundry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-agent-adapter
Source: https://github.com/Mothership-Foundry/foundry-dashboard/tree/main/.agents/skills/create-agent-adapter
Command: npx skills add https://github.com/Mothership-Foundry/foundry-dashboard --skill create-agent-adapter-mothership-foundry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill explains how to create a new Paperclip agent adapter, enabling teams to standardize the interface, registration points, and runtime integration across server, UI, and CLI.

Core Features & Use Cases

  • Provides a canonical package structure (packages/adapters/<name>/) with shared metadata, server, UI, and CLI modules.
  • Documents how to implement required exports (type, label, models, agentConfigurationDoc) and how to register adapters in server/ui/CLI registries.
  • Outlines security, session management, and skill-injection conventions to keep adapters production-ready.

Quick Start

Create a new adapter package under packages/adapters/<name>/, implement the required exports in index.ts, implement server/ui/cli modules, and register the adapter in all three registries.

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 Paperclip adapter for an AI agent?

To build a Paperclip adapter, create a package under packages/adapters/<name>/ that implements standard exports for server, UI, and CLI modules. You must register the adapter across all three registries to ensure predictable runtime behavior.

What required exports do I need to implement for a Paperclip agent adapter?

A Paperclip agent adapter requires standard exports including type, label, models, and agentConfigurationDoc in its index.ts file. These shared metadata fields allow the adapter to integrate properly with the server, UI, and CLI modules.

How do I manage sessions and security when creating an agent adapter?

Agent adapter security and session management require documenting specific registration points and environment handling conventions within your adapter package. Following these security considerations ensures safe and predictable runtime behavior across server, UI, and CLI integrations.

Can I use this adapter architecture to integrate AI agents across server, UI, and CLI simultaneously?

Yes, the canonical adapter package structure supports simultaneous integration across server, UI, and CLI. You implement specific modules for each environment and register the adapter in all three registries to achieve full runtime integration.

What's the best way to structure an AI agent adapter package for production readiness?

The best way to structure a production-ready adapter package is to follow the canonical packages/adapters/<name>/ directory layout. This structure separates shared metadata, server execute and parse functions, session codecs, and UI parse and build utilities.

Why does my Paperclip adapter not show up in the server or CLI registries?

A Paperclip adapter will not appear if it is not explicitly registered in all three server, UI, and CLI registries. You must document the registration points and ensure the standard module structure is correctly implemented.