create-agent-adapter

Create Paperclip adapter scaffolding with server, UI, and CLI modules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standard blueprint for creating Paperclip adapter packages, ensuring consistency across server, UI, and CLI when adding new adapters or modifying the adapter system.

Core Features & Use Cases

  • End-to-end scaffolding for a new adapter package (server, UI, CLI) with required exports and module structure.
  • Guidance on registration, session handling, env integration, and adapter lifecycle.
  • Real-world use: rapidly bootstrap an adapter for a new AI tool or integrate a custom process.

Quick Start

Follow this guide to scaffold a new adapter package and implement the required modules across server, UI, and CLI.

Frequently Asked Questions about create-agent-adapter

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

FAQPage Schema
How do I create a new Paperclip adapter package?

To create a Paperclip adapter package, you need to scaffold required server, UI, and CLI modules following a four-export package structure, ensuring session handling and environment integration are properly implemented.

What is the required module structure for a Paperclip adapter?

The required module structure for a Paperclip adapter includes standardized server, UI, and CLI modules, a four-export package interface, registration points, and session handling conventions derived from existing adapters.

How do I add registration and session handling when building a Paperclip adapter?

Adding registration and session handling when building a Paperclip adapter involves applying standard scaffolding conventions that define registration points and integrate environment variables across the server and UI modules.

Can I use existing adapter conventions to scaffold a custom Paperclip adapter for a new AI tool?

Yes, you can use existing adapter conventions derived from claude-local and codex-local adapters to rapidly bootstrap a custom Paperclip adapter for a new AI tool or process.

What's the best way to modify the Paperclip adapter system without breaking consistency?

The best way to modify the Paperclip adapter system without breaking consistency is to follow the standard blueprint covering required interfaces, module structure, and adapter lifecycle conventions across server, UI, and CLI.

Do I need to implement a four-export package when scaffolding a Paperclip adapter?

Yes, you need to implement a four-export package when scaffolding a Paperclip adapter to ensure consistency and proper integration across server, UI, and CLI modules.