create-agent-adapter

Scaffold Paperclip agent adapter packages with four exports and registry wiring.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/santhank8/paperclone --skill create-agent-adapter-santhank8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-agent-adapter
Source: https://github.com/santhank8/paperclone/tree/main/.agents/skills/create-agent-adapter
Command: npx skills add https://github.com/santhank8/paperclone --skill create-agent-adapter-santhank8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a blueprint and tooling scaffolding to implement a new Paperclip adapter across server, UI, and CLI, enabling integration with a new AI runtime or tool.

Core Features & Use Cases

  • Scaffold the adapter package under packages/adapters/<name>/ with the four exports and registry wiring.
  • Provide a consistent server, UI, and CLI module structure, including frontmatter metadata and tests.
  • Support end-to-end integration for different runtimes, including session handling, environment injection, and testing patterns.

Quick Start

Scaffold a new adapter by creating the packages/adapters/<name> package, implement the four exports, and wire up server, UI, and CLI modules.

Frequently Asked Questions about create-agent-adapter

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

FAQPage Schema
How do I scaffold a Paperclip adapter to integrate a new AI runtime?

To scaffold a Paperclip adapter, create the package under packages/adapters/<name>/, implement the four required exports, and wire up the server, UI, and CLI modules to enable runtime integration.

What is the four-export convention for building a Paperclip agent adapter?

The four-export convention is a required structural pattern for Paperclip agent adapters that enforces specific module exports, ensuring reliable session codec integration, environment handling, and test patterns across server, UI, and CLI.

How do I wire up server, UI, and CLI modules when creating an adapter package?

Wiring up server, UI, and CLI modules involves creating a consistent package structure with registration points and frontmatter metadata, ensuring the new AI runtime operates reliably across all interfaces.

Does creating a Paperclip adapter require manual session codec and environment handling setup?

Creating a Paperclip adapter involves session codec integration and environment handling, but the scaffold enforces these patterns automatically to ensure reliable operation and reuse across different runtimes.

What's the best way to structure tests for a new Paperclip agent adapter?

The best way to structure tests for a Paperclip agent adapter is to follow the scaffold's enforced test patterns, which are designed to validate the four-export convention and ensure reliable end-to-end runtime integration.

When do I need to add frontmatter metadata to a Paperclip adapter package?

Frontmatter metadata is required when scaffolding a Paperclip adapter package to provide consistent module structure across server, UI, and CLI, ensuring proper registration and integration of the new AI runtime.